Know when your n8n workflow fails.

Send the workflow name, failed step and execution link to your iPhone using Error Trigger and HTTP Request.

Get Kweenkl for iPhoneDownload the n8n workflow

Five channels free. An optional one-time purchase unlocks unlimited channels; see the App Store for pricing in your region.

Connect one workflow

1. Install Kweenkl, allow notifications, and create a channel for workflow alerts. Copy its webhook URL.
2. Download the error-alert workflow and import it into n8n.
3. Open Send iPhone alert. Replace the placeholder URL with your channel's webhook URL.
4. Save and publish the alert workflow if your n8n version offers publishing.
5. In a workflow you already use, open Settings → Error workflow and select the Kweenkl alert workflow. Save.

The payload contains the workflow name, failed step and execution link, when available. It leaves out input records and the full error object. Everyone subscribed to the Kweenkl channel can receive the alert. Keep the webhook URL private and replace it before sharing any export.

Test the complete connection

First open your normal HTTPS n8n editor address on the iPhone and sign in. A link containing localhost or 127.0.0.1 will not reach an n8n instance on your computer. For a self-hosted instance, configure its external editor address (N8N_EDITOR_BASE_URL) and keep authentication enabled before testing.

1. Download the disposable test workflow and import it separately.
2. Set its Error workflow to the Kweenkl alert workflow. Keep saving failed executions enabled.
3. Publish the disposable workflow and copy the Webhook node's Production URL.
4. Send an empty POST to that URL from your terminal: curl --fail-with-body -X POST 'YOUR_DISPOSABLE_PRODUCTION_URL'.
5. Confirm the failed execution in n8n, the completed alert workflow, and the actual notification on your iPhone. Open the message's execution link.
6. Unpublish the disposable workflow after the test.

A manual editor run does not trigger Error Trigger. A successful HTTP response is not confirmation that your phone received the alert. For a self-hosted n8n instance, your phone needs its usual network access and login to open an execution link.

If the alert does not arrive

• Check that the monitored workflow has the correct error workflow selected.
• Publish the alert workflow when available. Our n8n 2.37.10 test refused an unpublished error workflow.
• Open the alert workflow's execution and inspect the HTTP Request status. Check its channel URL without sharing the private token.
• Check notification permissions and your phone's Focus settings. Confirm that the channel is present in Kweenkl.

What this covers

This recipe reports execution errors. It does not detect schedules that never fire or incorrect outputs that do not cause an error. Keep your heartbeat and outcome checks for those cases. A trigger failure may have no saved execution URL.

Published by Kweenkl. This recipe uses built-in n8n nodes; it is not an official n8n integration.

References: Error Trigger · HTTP Request