ActionPushbulletUpdated September 2026
What Pushbullet devices are connected?
Short answer: You can list pushbullet devices in Pushbullet by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Pushbullet List Pushbullet Devices action to a workflow, map its 0 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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.
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 run history shows the failed step with its input and the error message Pushbullet returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does List Pushbullet Devices support batch operations?
Run List Pushbullet Devices inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Pushbullet's rate limits.
More actions