n8n notifications on your iPhone

Quick answer

Add an HTTP Request node that POSTs JSON to https://monish.cc/v1/send with your Monish key. A done says the workflow finished, a failed can still ring during quiet hours, and an ask waits for your Approve before the next node runs. The same request works from cron and any shell script.

Get your key

Install Monish on your iPhone. Your key, an_ followed by 10 characters, is in Setup, inside your line. Treat it like a password: anyone who has it can send to your phone. If it leaks, tap New key in the app.

The HTTP Request node

SettingValue
MethodPOST
URLhttps://monish.cc/v1/send
AuthenticationGeneric credential type, then Header Auth. Name Authorization, value Bearer an_… with your key. The key stays in n8n’s credentials, out of any workflow you share.
Send bodyOn. Body content type JSON, specify body using JSON.
JSONOne of the bodies below. Switch the field to Expression so the {{ }} parts are filled in.

Every body has a type (done, failed, ask, progress or metrics), a title of 60 characters or so, and optionally a body of up to 200, an agent name and an id. The skill lists every field.

Three recipes

1. Ping when a workflow finishes

Put the node last. The count comes from the node before it.

JSON body

{
  "id": "n8n-{{ $execution.id }}",
  "type": "done",
  "agent": {{ JSON.stringify("n8n · " + $workflow.name) }},
  "title": "Invoices synced",
  "body": "{{ $json.count }} invoices sent to accounting"
}

2. Ring when a workflow fails

Create an error workflow: an Error Trigger node followed by this HTTP Request node. Then, in each workflow’s settings, pick it as the error workflow. A failed can still ring during your quiet hours.

JSON body after the Error Trigger

{
  "id": "n8n-error-{{ $json.execution.id }}",
  "type": "failed",
  "agent": {{ JSON.stringify("n8n · " + $json.workflow.name) }},
  "title": {{ JSON.stringify($json.workflow.name + " failed") }},
  "body": {{ JSON.stringify(String($json.execution.error.message).slice(0, 200)) }},
  "fields": { "severity": "error", "message": {{ JSON.stringify("Stopped at " + $json.execution.lastNodeExecuted) }} }
}

JSON.stringify keeps a workflow name or an error message with quotes from breaking the JSON.

3. Approve before an email goes out

  1. Ask. An HTTP Request node sends the question.
  2. Wait for the answer. A second HTTP Request node, method GET, same credential, calls the URL below. Each call holds for up to 25 seconds.
  3. Still pending? An If node checks {{ $json.status }}. If it is pending, connect it back to “Wait for the answer”.
  4. Approved? A second If node sends approved on to your Gmail or Send Email node. denied, expired and text stop there, or send a done saying the email is on hold.

JSON body of the Ask node

{
  "id": "n8n-mail-{{ $execution.id }}",
  "type": "ask",
  "agent": {{ JSON.stringify("n8n · " + $workflow.name) }},
  "title": "Send the October newsletter to 1,240 subscribers?",
  "body": "Subject: What’s new in October",
  "expires_in": 3600,
  "fields": { "risk": "high", "approve_label": "Send", "deny_label": "Hold" }
}

URL of the Wait for the answer node

https://monish.cc/v1/answer/n8n-mail-{{ $execution.id }}

The loop ends on its own: once expires_in has passed, the answer is expired, which counts as a no. More on questions.

Cron and shell scripts

The same endpoint, from any machine that has curl. Export MONISH_KEY, send one failed on a non-zero exit and one done otherwise.

nightly-backup.sh

#!/bin/sh
# nightly-backup.sh: one done when it works, one failed with the exit code when it doesn't.
notify() { curl -s -m 10 https://monish.cc/v1/send -H 'content-type: application/json' \
  -H "authorization: Bearer $MONISH_KEY" -d "$1" >/dev/null; }

if /usr/local/bin/backup.sh >/tmp/backup.log 2>&1; then
  notify '{"type":"done","agent":"cron · nas","title":"Backup done","body":"/srv saved to the NAS"}'
else
  code=$?
  notify "{\"type\":\"failed\",\"agent\":\"cron · nas\",\"title\":\"Backup failed\",
    \"fields\":{\"message\":\"backup.sh stopped, see /tmp/backup.log\",\"severity\":\"error\",\"code\":\"exit $code\"}}"
fi

crontab, with your key in place of the dots

MONISH_KEY=an_••••••••••
0 3 * * * /home/me/bin/nightly-backup.sh

What lands on your iPhone

Questions

Does it work with n8n Cloud and self-hosted n8n?
Yes. It is a plain HTTPS request, so any n8n that can reach the internet can send to your iPhone.
Do I need a community node?
No. The built-in HTTP Request node is all it takes, for sending and for reading answers.
How many messages can a workflow send?
300 per hour per key, and at most 10 in 10 seconds. Past that the server answers 429 with retry_after. Send one item per run, not one per row: a batch of 50 rows is one done with the count.
What does the server keep?
What your workflow sends, for 48 hours, so the app can catch up on a missed notification. Then it is deleted. Answers to questions are kept 24 hours.

More guides

New to Monish? The home page shows what lands on your iPhone, and all guides are listed here.

Get Monish on your iPhone

Free, no account, no SDK. Your key is waiting in the app, inside the line to paste.

Download on the App Store