Pushbullet, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Pushbullet account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Notifications
- Signs in to your account
- 15 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What Pushbullet is
Pushbullet enables seamless sharing of notifications and files across devices.
You sign in with your own Pushbullet account, the same way you already do. We never see or hold your password.
One message in, the work done in Pushbullet.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in Pushbullet. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own Pushbullet account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in Pushbullet
These are the ready-made tools your AI employee already has in Pushbullet. It is not limited to them, but it never has to be taught these.
- Create ChatTool to create a new chat with the specified email address. use when you need to initiate a conversation thread by email.
- 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://examp
- 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.
- 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.
- Delete PushTool to delete a specific push by its identifier. use when you need to remove a push after confirming its identifier.
- Delete Pushbullet DeviceTool to remove a device by its identifier. use when you need to delete a device from your pushbullet account after confirming its identifier.
- Get current 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.
- 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.
- List DevicesTool to list all registered devices for the current user. use after obtaining a valid access token.
- List PushesTool to list pushes with optional filtering and pagination. use when retrieving or syncing pushes after a certain time.
- Mute or Unmute ChatTool to mute or unmute an existing chat. use when adjusting notification settings for a specific chat by its identifier.
- Register DeviceTool to register a new device under the current user’s account. use when adding a new hardware or app device to the user's pushbullet devices.
- Update DeviceTool to update metadata for a device by its identifier. use when you need to change device settings like nickname, model, or icon.
- 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.
- 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.
You stay the boss of your Pushbullet account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own Pushbullet account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in Pushbullet is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in Pushbullet and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about Pushbullet
- Can an AI employee really work inside Pushbullet?
- Yes. It signs in to your own Pushbullet account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of Pushbullet?
- No. Nothing moves and nothing is replaced. Your records stay in Pushbullet, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my Pushbullet account?
- You sign in with your own Pushbullet account, the same way you already do. We never see or hold your password. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in Pushbullet?
- It has 15 ready-made tools in Pushbullet today, among them Create Chat, Create Push and Delete All Pushes. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use Pushbullet and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in Pushbullet and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in Pushbullet?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Pushbullet is written down with what it did and when.