ActionPushbulletUpdated May 2026

What Pushbullet devices are connected?

Short answer: Drop the "Pushbullet → List Pushbullet Devices" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 Pushbullet actions

Sample request

{}

Returns

{
  "devices": [
    {
      "iden": "dev_abc",
      "model": "iPhone 15",
      "active": true,
      "nickname": "iPhone"
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Pushbullet Devices.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Pushbullet

2 Google Sheets triggers

HubSpot → Pushbullet

18 HubSpot triggers

FAQ

Questions about List Pushbullet Devices.

What does the List Pushbullet Devices action do in Pushbullet?

Returns the devices linked to the account. Useful for "send only to my phone, not my desktop" device-specific routing.

What inputs does List Pushbullet Devices require?

List Pushbullet Devices has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Pushbullet returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Pushbullet Devices support batch operations?

Yes. Run List Pushbullet Devices inside a Loop node to process arrays. Tiny Command handles Pushbullet's rate limits automatically so you don't have to throttle manually.

More actions