Pushbullet
for LuumenAI
Send push notes to the devices your on-call team already carries
Pushbullet gives Luumen a direct line to the phones and laptops your team already uses. The agent reads your registered devices, chats, and push history for context, then sends a note or link to a specific device when something needs a human. Sending a push is held for your approval before it goes out.
The Pushbullet toolbox
15 tools: 4 read, 11 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet current userRetrieve the currently authenticated user's profile.
- ReadList ChatsList all chat objects for the current user.
- ReadList DevicesList all registered devices for the current user.
- ReadList PushesList pushes with optional filtering and pagination.
- WriteCreate ChatCreate a new chat with the specified email address. Approval by default
- WriteRegister DeviceRegister a new device under the current user's account. Approval by default
- WriteCreate PushSend a new push (note, link, or file) to a device, user, channel, or client. Approval by default
- WriteDelete All PushesDelete all pushes for the current user asynchronously. Approval by default
- WriteDelete ChatDelete a chat by its identifier. Approval by default
- WriteDelete Pushbullet DeviceRemove a device by its identifier. Approval by default
- WriteDelete PushDelete a specific push by its identifier. Approval by default
- WriteMute or Unmute ChatMute or unmute an existing chat. Approval by default
- WriteUpdate DeviceUpdate metadata for a device by its identifier. Approval by default
- WriteUpdate PushUpdate a push (dismiss or modify list items) by its identifier. Approval by default
- WriteUpload RequestObtain a signed upload URL for a file before pushing. Approval by default
One prompt, start to finish
What a governed Pushbullet run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as create chat, register device, create push, delete all pushes, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Pushbullet — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
SlackRead the incident thread; post updates and approvals back.
GmailVendor and alert mail as context; replies drafted for review.
Microsoft TeamsRead Teams channels and chats for context, then make membership changes as approved steps.
DiscordRead Discord command permissions and app context, then change them with approvalPut Pushbullet to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.