Reference · Credentials
Pushcut API credentials
Used by 2 BusyBot nodes.
pushcutApi 1 field The Pushcut credential holds an API key generated in the Pushcut iOS app, used by the Pushcut node and its trigger to fire notifications and run shortcuts from a workflow.
Fields
| Field | Type | Required | Notes |
|---|---|---|---|
API KeyapiKey | password | Yes | Your Pushcut API key. |
Getting your credentials
- Open the Pushcut app on your iOS device.
- Go to the Account area and find the API key. Generate one if none exists.
- Copy the key and paste it into the credential’s API Key field in BusyBot.
Notifications must also be defined in the Pushcut app before a workflow can send them by name.
Permissions and scopes
The key is tied to your Pushcut account and reaches the devices registered to it.
Troubleshooting
- 401 Unauthorized — the key is wrong or was regenerated in the app.
- Notification not found — the notification name must already exist in the Pushcut app; it is not created on the fly.
- Nothing arrives on the device — check that the device is registered and notifications are permitted in iOS settings.
Frequently asked questions
Where does the API key come from?
The Account area of the Pushcut iOS app, rather than a web dashboard.
Why is my notification name rejected?
Notifications have to be defined in the Pushcut app first — a workflow triggers an existing one by name rather than creating it.
Does one key cover the node and the trigger?
Yes, both declare the same credential type.
Nodes that use Pushcut API
One credential works across every node below — create it once and reuse it.
Last updated . Spotted something wrong? Tell us.