Get a push when a workflow runs.
Hear from your Make, n8n, or IFTTT workflows the moment they finish, and get a push the second one breaks without warning. No more silent automations you only notice when something downstream goes wrong.
Know when your workflows run
Automations run in the background until one quietly breaks. Put their results on your phone instead.
One final step
One final HTTP step in Make, n8n, or IFTTT turns the whole workflow into a push.
Catch failures
Point error handlers and fallback paths at PocketAlert and a broken scenario reaches your phone.
Data from the run
Carry record names, customers, and totals from earlier steps into the alert so it describes the run.
Any platform
Make, n8n, IFTTT, Zapier, and Pipedream each fire through a standard HTTP request module.
Detect silent stops
Heartbeat on every run. When the pings stop, you learn the automation went quiet on its own.
Result in hand
The result lands on your phone when the run ends, sparing you a trip to the run history.
Three steps to automation alerts
Get an API key
Create an API key on the API Keys page for the Token header.
Add a final step
Add a final HTTP step to your Make, n8n, or IFTTT workflow pointed at the messages API.
Close the loop
Run the workflow and your phone buzzes with the result. Wire up errors for failure alerts.
Notify from your automation
1. Get an API key
Create a key on the API Keys page and send it in the Token header.
2. Add a final HTTP step
In Make, add the HTTP, Make a request module. In n8n, add an HTTP Request node. In IFTTT, use the Webhooks, Make a web request action. Configure it like this:
Method: POST
URL: https://api.pocketalert.app/v1/messages
Headers: Token: YOUR_API_KEY
Content-Type: application/json
Body type: Raw / JSON
Body: {"title":"Sync complete","message":"42 records updated","application_id":"qm47b9pzxzxg"}In Make, put the headers in the Headers field as Token and Content-Type, set Body type to Raw with content type JSON, and pull earlier-step values into the body. In n8n, set Authentication to None, add the two headers, and send JSON body.
3. Handle failures
Route the platform's error handler, such as Make error routes or the n8n Error Trigger, to the same endpoint with a body like {"title":"Workflow failed","message":"Sync stalled at step 3","level":"high","application_id":"qm47b9pzxzxg"}. The getting-started docs cover the rest.
Questions, answered
Add a final HTTP step to your Make, n8n, or IFTTT workflow and POST it to https://api.pocketalert.app/v1/messages with your Token header. Each run sends a push notification, so you no longer dig through the run history.
Use an error or fallback path. Make has error handler routes, n8n has an Error Trigger workflow, and IFTTT can branch on a filter. Point any of them at the messages API and failures land on your phone.
Yes. Pass any field from an earlier step into the message, such as a record name, customer, or total, and the alert tells you what the run actually did.
Make, n8n, IFTTT, Zapier, and Pipedream all work through their HTTP request module pointed at the PocketAlert messages API.
Send a heartbeat from each successful run of a scheduled scenario. If the pings stop, the automation has gone quiet without throwing an error, which is otherwise easy to miss.
Yes. Add a level field to the JSON body, from silent (-2) to critical (2). Give the error path level high so a broken workflow lands as a time-sensitive push that cuts through iPhone Focus, and send routine heartbeats at silent — they skip the sound and vibration but stay in your history.
Stay on top of your automations.
Drop a final HTTP step into any workflow. After that you know whether it ran or stalled.