- Integrations
- /
- Pushbullet
Pushbullet
Pushbullet cross-device notifications
Pushbullet is the cross-device notification and file-sharing service — used to push notifications and links between your phone, browser, and desktop without separate app installs. Tiny Command exposes three read actions, no triggers (Pushbullet's real-time stream is WebSocket-based; for trigger-shaped workflows, poll List Pushes on a cadence and dedupe by push ID): List Pushes (recent pushes received on the account), List Devices (every device connected to the account — phone, laptop, browser extension), List Items (a generic items list). The connection uses a Pushbullet access token from the account settings. Most Pushbullet workflows are personal automation — push a notification to your phone when a long-running script finishes, mirror Slack notifications between devices. For team automation, Pushbullet isn't the right fit (it's per-user, not multi-tenant); for personal "I want my computer to ping my phone when X happens" workflows, it's a friendly fit.
Do anything Pushbullet can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| List Pushbullet Devices | Returns the devices linked to the account. Useful for "send only to my phone, not my desktop" device-specific routing. |
| List Pushbullet Items | Generic list endpoint for Pushbullet resources. Useful for "what's in my Pushbullet history" inventory workflows. |
| List Pushbullet Pushes | Returns recent push notifications received on the account. Useful for "react to Pushbullet activity" workflows via polling. |
Pre-built Pushbullet workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Pushbullet once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Pushbullet field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Pushbullet integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Pushbullet to Tiny Command?
What Pushbullet triggers does Tiny Command support?
What Pushbullet actions can I run from a workflow?
Is the Pushbullet integration real-time?
Do I need to write code to use Pushbullet with Tiny Command?
How much does the Pushbullet integration cost?
More other apps people connect.
Same category as Pushbullet, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Pushbullet.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.