Pushbullet enables seamless sharing of notifications and files across devices.
Pushbullet enables seamless sharing of notifications and files across devices. On Nagent, Pushbullet is exposed as a fully-configurable notifications integration that any agent can call — 15 actions, and OAUTH2, API_KEY authentication. No code is required to wire Pushbullet into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Pushbullet to automate the kinds of tasks notifications teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Pushbullet into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Pushbullet, with input parameters and output schema. Drop these into any step of an agent built in Helix.
PUSHBULLET_CREATE_CHATTool to create a new chat with the specified email address. Use when you need to initiate a conversation thread by email.
Input parameters
Email of the person to create the chat with (does not have to be a Pushbullet user).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHBULLET_CREATE_DEVICETool to register a new device under the current user's account. Use when adding a new hardware or app device to Pushbullet.
Input parameters
Icon for this device; e.g., desktop, phone, watch, etc.
Model of the device
True if the device has SMS capability (Android only)
Name to display for the device
Platform-specific push token; leave blank for custom devices
Version of the Pushbullet app installed on the device (non-negative)
Manufacturer of the device
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHBULLET_CREATE_PUSHTool to send a new push (note, link, or file) to a device, user, channel, or client. Use when you need to share content to a specific target. Example: "Send a link to https://example.com to device abc123".
Input parameters
URL to include with a link push. Required when type='link'.
Body text of the note, link message, or file message.
Client-generated unique identifier for idempotency.
Type of push to send: 'note', 'link', or 'file'.
Email address to send the push to (Pushbullet user or fallback email).
Title of the note or link (optional).
URL of the file to push. Required when type='file'.
Filename for file push. Required when type='file'.
MIME type of the file. Required when type='file'.
Tag of channel to broadcast the push to subscribers.
Identifier of OAuth client to send the push to its authorized users.
Identifier of device to send the push to.
Identifier of the source device sending this push.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHBULLET_DELETE_ALL_PUSHESTool to delete all pushes for the current user asynchronously. Use when you need to bulk-clear all existing pushes in one call.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHBULLET_DELETE_CHATTool to delete a chat by its identifier. Use when you need to remove a chat from your Pushbullet account after confirming its identifier.
Input parameters
The unique identifier of the chat to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHBULLET_DELETE_DEVICETool to remove a device by its identifier. Use when you need to delete a device from your Pushbullet account after confirming its identifier.
Input parameters
The unique identifier of the device to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHBULLET_DELETE_PUSHTool to delete a specific push by its identifier. Use when you need to remove a push after confirming its identifier.
Input parameters
Identifier of the push to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHBULLET_GET_USERTool to retrieve the currently authenticated user's profile. Use when you need to verify the access token or display the current user's details.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHBULLET_LIST_CHATSTool to list all chat objects for the current user. Use when you need the full set of chat threads before sending or muting messages.
Input parameters
Maximum number of chats to return (max 500).
Cursor for pagination to fetch the next page of chats.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHBULLET_LIST_DEVICESTool to list all registered devices for the current user. Use after obtaining a valid access token.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHBULLET_LIST_PUSHESTool to list pushes with optional filtering and pagination. Use when retrieving or syncing pushes after a certain time.
Input parameters
Maximum number of pushes to return (max 500, default 500).
If true, only active pushes are returned.
Cursor for pagination to fetch the next set of pushes.
Only return pushes modified after this UNIX timestamp (float).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHBULLET_UPDATE_CHATTool to mute or unmute an existing chat. Use when adjusting notification settings for a specific chat by its identifier.
Input parameters
Unique identifier of the chat to update
True to mute notifications for this chat, false to unmute
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHBULLET_UPDATE_DEVICETool to update metadata for a device by its identifier. Use when changing a device's nickname, model, or other settings.
Input parameters
Icon for the device. Common values: desktop, laptop, tablet, phone, watch, system, ios.
Identifier of the device to update.
Model of the device.
Whether the device supports SMS (Android only).
New display name for the device.
Platform-specific push token. Leave blank for custom or listening devices.
Version of the Pushbullet app installed on the device (non-negative).
Manufacturer of the device.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHBULLET_UPDATE_PUSHTool to update a push (dismiss or modify list items) by its identifier. Use when marking a push as dismissed or updating list push items.
Input parameters
Unique identifier of the push to update
List of items to update for list-style pushes
Set to true to mark the push as dismissed (hides notifications)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHBULLET_UPLOAD_REQUESTTool to obtain a signed upload URL for a file before pushing. Use when you need to upload file content via the signed S3 form data.
Input parameters
Name of the file to upload. Example: 'photo.jpg'
MIME type of the file. Example: 'image/jpeg'
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 92 agents privately built on Nagent that already use Pushbullet.
Build on Nagent
Connect Pushbullet to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Pushbullet, and click "Connect Now." You'll authenticate with OAUTH2, API_KEY — Nagent handles credential storage and refresh automatically. Once connected, Pushbullet is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Pushbullet is connected, you configure its 15 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Pushbullet steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Pushbullet event fires, the agent kicks off automatically.
Every Pushbullet action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Pushbullet ships with 15 pre-built notifications actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Pushbullet together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Pushbullet-based workflows tailored to your business.