Pushcut integration

What it does

The Pushcut integration lets your agency drive a client's on-device automation surface from inside a workflow. Connect a client's Pushcut account once and your workflows can send rich iOS notifications (with custom title, body, sound, image, and embedded action buttons), trigger a Pushcut Automation Server to run Siri Shortcuts or HomeKit scenes on a dedicated iPhone or iPad, and list the devices, notification templates, and active subscriptions on the account to populate dynamic dropdowns at design time.

Connect a Pushcut account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Pushcut and click Connect.
3. On the client's iPhone or iPad, open the Pushcut app and tap Account, then Integrations, then API.
4. Tap Create API Key, name it (e.g. TaskJuice), and copy the generated key.
5. Paste the key into TaskJuice. The key is sent on the API-Key header on every request.

To rotate or revoke the key, return to the Pushcut app, delete the existing key, generate a new one, and update the TaskJuice connection.

Triggers

Pushcut does not expose a provider-side webhook for inbound events on the launch catalog, so the integration ships no triggers. Use a polling Schedule node plus the List Notifications or List Subscriptions actions if you need to react to changes in the account configuration.

Actions

• pushcut/send-notification sends a predefined Pushcut notification by name. Overrides the title, body, input string, default action, image, sound, and target device list at send time.
• pushcut/execute-action triggers a Pushcut Automation Server to run a Siri Shortcut or set a HomeKit scene on a named server, with optional delay, timeout, and input string.
• pushcut/list-devices lists the iOS devices registered on the connected account so workflows can target a specific device by name.
• pushcut/list-notifications lists the notification templates defined on the connected account, so workflows can pick a notification by name without hard-coding it.
• pushcut/list-subscriptions lists the active webhook subscriptions on the connected account so workflows can audit which notifications mirror events to external URLs.

Known limitations

• Pushcut is an iOS-only product. The connected account must have at least one iPhone or iPad running the Pushcut app for notifications to deliver and for the Automation Server endpoints to respond.
• Notification templates are defined inside the Pushcut iOS app, not via the API. The Send Notification action targets an existing template by name; create the template on a device before referencing it in a workflow.
• The Pushcut Automation Server requires a dedicated, awake iOS device with the Pushcut Automation Server enabled. Execute Action calls time out when the server device is offline or asleep; surface the resulting error and retry on the next workflow run.
• Rate limits and per-account quotas are governed by the client's Pushcut subscription tier. When Pushcut returns a 429, the action surfaces as a retryable rate-limit error and honors the recommended backoff.
• The API key has full account scope. Treat it as a high-privilege secret, store it only in TaskJuice's credential vault, and rotate it from the Pushcut app when team members change.