ceven

Pushbullet

Sends instant alerts and files to your devices, syncs notifications across platforms, and automates content delivery to specific hardware targets.

Try Pushbullet in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Pushbullet integration

    • Describe the outcome and Ceven picks the right Pushbullet calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Pushbullet data, across all 15 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Pushbullet access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Pushbullet, when, and on whose behalf.
    • The agent pauses and asks when Pushbullet is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Pushbullet.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Pushbullet action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Pushbullet, and when to use it.

Create Push
Use this when you need to send a note, link, or file to a specific device, user, or channel.
Create Chat
Use this to initiate a new conversation thread with a user by providing their email address.
List Devices
Pull a list of all registered devices for the current user to identify target IDs.
List Pushes
Retrieve a history of pushes with optional filtering to sync state or audit alerts.
List Chats
Pull all existing chat objects to find specific threads before sending messages.
Get Current User
Retrieve the authenticated user profile to verify account details and access status.
Upload Request
Obtain a signed upload url to send a file via S3 form data before pushing it.
Update Device
Modify device metadata such as nicknames or icons to keep the device list organized.
Update Push
Mark a push as dismissed or modify items within a list push by its identifier.
Mute or Unmute Chat
Adjust notification settings for a specific chat thread to silence or enable alerts.
Register Device
Add a new hardware or app device to the user account for future notifications.
Delete Push
Remove a specific push notification from the account using its unique identifier.
Delete Chat
Remove an entire chat thread from the account after confirming the chat ID.
Delete Device
Remove a registered device from the account to stop it from receiving pushes.
Delete All Pushes
Bulk clear every existing push for the current user in one asynchronous call.
Delete Pushbullet Device
Tool to remove a device by its identifier. use when you need to delete a device from your pushbullet account after confirming its identifier.

16 actions · scroll to see them all

Frequently asked questions

Ceven uses OAuth2 for all Pushbullet connections. When you link your account, you are redirected to the Pushbullet authorization page where you grant specific permissions to the Ceven agent. Once you approve, Pushbullet sends us an authorization code that we exchange for an access token and a refresh token. We store these tokens in an encrypted vault. The agent uses the access token to make API requests and uses the refresh token to maintain the connection without requiring you to log in again. You can revoke this access at any time through your Pushbullet account settings, which immediately kills the token on their end.
Yes. The process involves a two step workflow. First, the agent calls the upload request action to get a signed URL from Pushbullet. Then, the agent uploads the file content to that signed S3 location. Once the upload is successful, the agent triggers a push action that references that file. This allows you to automate the delivery of reports, images, or logs from any connected SaaS tool directly to your mobile device. You can set up filters so only files of a certain size or type are pushed to avoid cluttering your device storage.
Yes, Pushbullet imposes API rate limits that the Ceven agent must respect. Specifically, there are limits on the number of pushes you can send per hour and per day. If a workflow attempts to send a massive burst of notifications, Pushbullet will return a 429 too many requests error. Ceven handles this by implementing an exponential backoff strategy, meaning the agent will wait a few seconds before retrying the request. If you consistently hit these limits, you may need to upgrade your Pushbullet account tier to a Pro plan to increase your daily allotment of pushes.
Ceven can do both. By using the list devices action, the agent can identify the unique ID for every piece of hardware linked to your account. You can build a workflow that sends a notification only to your work laptop during business hours and only to your phone during the weekend. Alternatively, you can send a push to the user object, which broadcasts the notification to every single device registered to that account. This is useful for emergency alerts that must be seen regardless of which device you are currently using.
Ceven logs the metadata of the workflow execution for debugging purposes, but it does not maintain a permanent archive of the message content sent via Pushbullet. The content exists in the workflow execution history for a limited time based on your data retention settings. Once the push is successfully delivered to the Pushbullet API, the data resides on Pushbullet servers according to their own privacy policy. If you need a permanent record of alerts, we recommend adding a step to your workflow that logs the message to a database or a spreadsheet before sending the push.
Yes, the agent has full access to the chat management tools. You can use Ceven to create new chats by email, list your existing conversations, and mute or unmute specific threads. This is particularly useful for creating a notification hub where different types of system alerts are routed into different chat threads. For example, you could have one chat for critical errors and another for daily summaries. The agent can automatically mute the summary chat during the night and unmute the critical error chat to ensure you are only woken up by the most urgent issues.
Pushbullet handles the delivery queue on their end. When Ceven sends a push to a specific device ID, the Pushbullet API accepts the request and queues the notification. As soon as the target device connects to the internet and checks in with the Pushbullet servers, the notification is delivered. The Ceven agent receives a success response from the API once the request is accepted, not when it is actually read by the user. If you need to verify that a message was seen, you would need to build a separate confirmation loop using a different tool.
Yes. You can set up a scheduled workflow in Ceven that runs every day or week to clean up your Pushbullet history. The agent can list all pushes, filter them by date or content, and then call the delete push action for each one that meets your criteria. You can also use the delete all pushes action for a complete wipe. This is helpful for users who use Pushbullet as a temporary scratchpad for links and notes and want to prevent the list from becoming an unmanageable archive of old data.

Alternatives to Pushbullet

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Pushover logoPushoverJoin logoJoinAirDroid logoAirDroid

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Pushbullet and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free