Doyouok community node: alerts for missed runs and “green but wrong” results

Hi everyone,

Disclosure first: I’m the developer of Doyouok, a small monitoring service for scheduled jobs, and I built this node. The node is free and MIT licensed, and it passed n8n’s verification, so it installs from the nodes panel on both n8n Cloud and self-hosted.

I built it to cover three common monitoring needs in scheduled workflows.

1. The workflow didn’t run at all

The server was down, the workflow got deactivated, or the trigger stopped firing. Nothing inside the workflow can report this, because nothing ran. If the trigger silently stops without reporting an error, an Error Workflow may have nothing to react to either.

The node covers this from the outside: you set Expected Every (for example 1 Days), and if no run arrives in time you get an overdue alert, even when your whole n8n is offline.

2. Check the result in the same node

Instead of an IF and a notification node,
set Result: Check Conditions, e.g. {{ $json.syncedContacts }} is greater than 0

(where 0 really means something broke).
The alert shows the actual value (“syncedContacts is 0, expected > 0”) and links to the execution.

3. Alerts managed in one place

Channels (email, Telegram, Slack, Discord), reminders and recovery messages are set once in Doyouok, and one dashboard shows all monitored workflows, even across n8n instances.

How you add it

Schedule Trigger (daily 02:00)  →  your workflow steps  →  Doyouok

Leave Check on This Workflow (Automatic). Save the workflow and run it once to create the check and start monitoring; there is no ping URL to copy. Renaming the workflow updates the check on the next run.

For instant alerts when a step errors, set that step’s On Error to “Continue (using error output)” and wire it to a second Doyouok node with Result: Failure.

What leaves your n8n

The workflow’s name and ID, the instance ID, the expected interval, success or failure, and on failure the reason text plus the execution link. Full input and output payloads are not uploaded. Failed-condition values and any custom Failure Message are included in the report, so avoid including sensitive data in those fields.

Honest limits

  • If the workflow crashes before it reaches the node and you haven’t wired the error output, you get the overdue alert, not an instant one. An Error Trigger mode is on my list.
  • The condition example expects an output item such as { "syncedContacts": 0 }. If an upstream node returns no items and the Doyouok node is not reached, detection falls back to the overdue alert.
  • It needs a Doyouok account. It’s free to start, with no credit card required. Paid plans are available if you need more checks.

Install

Open the nodes panel in any workflow, search for “Doyouok”, choose it under “More from the community” and press Install node (instance owner or admin). On self-hosted you can also install n8n-nodes-doyouok from Settings > Community Nodes.

Source and README
Setup guide and FAQ

Feedback welcome

How do you check today that a “successful” run actually did its job?
And which conditions would you want beyond number and text checks?
Happy to answer questions here.