Pushcut n8n integrationAutomate Pushcut with n8n.
Your phone can start a workflow, and a workflow can reach your phone. The Pushcut n8n integration runs both ways: the node exposes 1 operation, notification.send, and the Pushcut Trigger starts a run the second you tap an action you built in the app.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Pushcut n8n integration actually do?
Pushcut is an iOS app for smart notifications that kick off shortcuts, URLs and online automations. Wired into n8n, it plays two roles. The Pushcut node sends a notification from inside a workflow, with one operation to learn. The Pushcut Trigger works the other way: it starts a workflow when you tap an action you paired in the app, so a person stays in the loop without opening a laptop.
Start with the alert that has to leave the screen. A scheduled workflow reads a sheet in Google Sheets, finds the row that crossed a threshold, and calls notification.send. Title and Text are written from the row itself, so the notification says which client and which number moved, not just that something happened.
Second pattern: the approval you give while standing in a queue. A first workflow pushes a notification carrying an action. Tapping it hits the Pushcut Trigger, and a second workflow picks up from there, posting the decision to Slack or answering the customer in Telegram. The phone becomes the button, n8n does the rest.
Third pattern: the morning briefing. A public template pairs OpenWeatherMap with the Pushcut node to push a weather update every day (workflow 843), and the same shape carries yesterday's sales, a backup status or an error count.
The node covers sending, and nothing else. If you need a Pushcut endpoint it does not expose, the HTTP Request node calls the API directly and reuses the same credential through its predefined authentication, so you keep one API key for the whole instance.
Two limits worth knowing before you build. The notification you pick with Notification Name or ID has to exist in the app first, since the node fires an existing notification rather than inventing one. And the app is iOS, so a mixed-device team usually pairs it with another channel, Pushover for example, for the people who are not on an iPhone. If the whole logic is still fuzzy, the n8n training walks through triggers and credentials from scratch.
How do you connect Pushcut to n8n?
- 01
Create the API key in Pushcut
Download the Pushcut app first, then open Account, go to Integrations and choose Add API Key. That key is the only authentication method the node and the trigger accept, so keep the screen open: you paste it into n8n in the next step. There is no OAuth flow and no scope list to tick here.
- 02
Store the key as a credential
In n8n, open the Credentials menu and create a Pushcut credential, then paste the API Key. A credential is created once and reused everywhere: the Pushcut node and the Pushcut Trigger both pick it from their dropdown, and so does an HTTP Request node set to the predefined Pushcut authentication.
- 03
Pair an action with the trigger
In the app, open a notification from the Notifications screen, select Add Action and give it a label. Switch to the Server tab, then the Integration tab, and choose Integration Trigger. Back in n8n, name the action in the trigger node and hit Execute step. Your action now shows up in the app under Select Integration Trigger, and Done saves it.
What starts a workflow from Pushcut ?
Pushcut Trigger is the node that starts a workflow when Pushcut calls n8n. Activate the workflow: n8n gives you the webhook URL to register in Pushcut, and every call becomes an execution.
What you see in n8n
Configuration notes
01Configure the Pushcut Trigger
The Pushcut Trigger runs on a webhook, an URL that Pushcut calls when the action fires. n8n registers that URL when you activate the workflow, and each call arrives within seconds, with no polling loop checking for news in the background. There is no event list to tick: the action you pair in the app is the event.
Key parameters
- Action Name: any name you like, and it shows up as a server action inside the app. Pick something you will recognize in a list of actions, like the workflow it starts.
02Run a workflow from an iPhone action
Once paired, the action behaves like any other entry point in n8n. Tapping it in the app, or firing it from a shortcut or a URL that Pushcut already handles, starts the run and the rest of the workflow executes as usual. Nothing else in the node changes, which is why one trigger covers every scenario here.
notification.send, or a field team that logs an arrival by tapping an action while n8n writes the line and notifies the office. Version 1 of the trigger is the current one, so a workflow built today keeps the same parameter when you import it elsewhere. Neither case needs a second trigger node sitting in the same workflow.What can the Pushcut node do?
The Pushcut node exposes 1 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
| Resource | Send |
|---|---|
| Notification | ✓ |
Notification
1 operationSend a notification
notification.sendWhat you see in n8n
Notes & use cases
Fires a notification that already exists in the Pushcut app and pushes it to your devices, rewritten for the run in progress when you need it.
Key parameters
- Notification Name or ID: pick it from the list, or pass an ID with an expression like
{{ $json.notification }}. - Device Names or IDs: the devices that receive it. Left empty, every device gets it.
- Title and Text: replace what the app defines, so one notification serves many workflows.
- Input: the value passed as input to the notification action, useful when it expects an order number.
Need help automating Pushcut with n8n?
A person reads every message.
