Pushbullet n8n integrationAutomate Pushbullet with n8n.
Every automation eventually has to reach a phone. The Pushbullet n8n integration wraps 4 operations on a single push resource, so a workflow can send a note, a link or a file to one device, an email address or a channel, then read back or clean up what it sent. The starting signal comes from somewhere else.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Pushbullet n8n integration actually do?
It connects n8n workflows to the Pushbullet API through one node, built around a single resource called Push. A push is the short notification that lands on your phone, in the browser extension, or with anyone subscribed to a channel. n8n can create one, read the ones already sent, hide one, or remove it. That is the whole surface: 4 operations, 1 resource, no starting node.
Scenario one, the overnight job nobody watches. A workflow reads rows from Google Sheets, processes them, and closes with push.create set to Note, so the outcome lands on the phone of whoever is on call. Title carries the summary, body carries the detail. No need to open n8n to find out how the run went.
Scenario two, the link handoff. The workflow produces a URL: a generated report, an invoice, a dashboard filtered on today. Type set to Link sends that address as a notification you open with one tap, instead of one more message competing for attention in Gmail.
Scenario three, the file drop. Type set to File pushes a binary item coming from an earlier node, so a PDF built mid-workflow reaches the device without a storage link in between. Target decides who receives it: one specific device, an email address, a channel tag, or every device on the account.
Reach for the HTTP Request node once the Pushbullet API offers something this one does not. Devices, contacts, chats and channel subscriptions all sit outside the dedicated node's reach. The same Pushbullet credential, the connection saved once inside n8n, authenticates that HTTP call too.
Two limits are worth knowing before building anything. There is no Pushbullet trigger, no node that wakes a workflow up when a push arrives, so the start comes from a Schedule Trigger, from a Webhook node (a URL n8n publishes and another service calls), or from the trigger of another tool such as Slack or Telegram. And Get Many stops at Limit for as long as Return All stays off. If the platform choice is still open, the n8n review goes deeper into the self-hosting question.
How do you connect Pushbullet to n8n?
- 01
Create the OAuth client
Start on the Pushbullet create client page. It turns your account into an OAuth client, meaning an app allowed to act on your behalf. Creating it hands you a Client ID and a Client Secret. Keep the tab open, because n8n needs both values, and the client needs one value coming from n8n before the pairing works at all.
- 02
Register the redirect URL
In n8n, open the Credentials menu and add a new Pushbullet credential. n8n displays an OAuth Redirect URL: copy it and add it as the redirect_uri of the client you created a minute ago. That address is where Pushbullet sends the browser once access is granted, and a value that does not match is behind most connections that never complete.
- 03
Authorize from n8n
Paste the Client ID and the Client Secret into the credential, then click Connect my account. The Pushbullet consent screen opens, you approve, and n8n stores the token. The credential is saved once for good: every Pushbullet node you add afterwards offers it in a dropdown, in any workflow on that instance.
What can the Pushbullet node do?
The Pushbullet node exposes 4 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Push
4 operationsCreate a push
push.createWhat you see in n8n
Notes & use cases
Sends a new push and returns the created object, including its identifier.
Key parameters
- Type: Note, Link or File, and that choice drives the fields that follow.
- Title and Body: the two lines shown in the notification.
- URL: the address opened on tap, for a Link push, often
{{ $json.url }}. - Input Binary Field: the name of the binary field holding the file, for a File push.
- Target and Value: Target picks Default, Device ID, Email or Channel Tag, and Value carries the matching identifier, address or tag.
Delete a push
push.deleteWhat you see in n8n
Notes & use cases
Removes a push from the account, so it disappears from the Pushbullet history and from the devices that synced it.
Key parameters
- Push ID: the identifier of the push, taken from the output of a Create a push or Get many pushes step, never the title.
Get many pushes
push.getAllWhat you see in n8n
Notes & use cases
Reads the pushes already sitting on the account and returns them as items, one per push.
Key parameters
- Return All: on, n8n walks every page of the history; off, Limit sets how many pushes come back.
- Active: in Filters, left on, it leaves out pushes that were already deleted.
- Modified After: in Filters, a timestamp from which pushes are picked up, which spares a scheduled run from reading everything again.
Update a push
push.updateWhat you see in n8n
Notes & use cases
Marks an existing push as dismissed, which hides its notification wherever that is still possible. Nothing else moves.
Key parameters
- Push ID: the push to act on, usually piped in from a Get many pushes step.
- Dismissed: set to true, the notification is hidden where the device allows it, and it is the only attribute this operation edits.
Need help automating Pushbullet with n8n?
A person reads every message.