Try the outcome check without an account

Before connecting n8n, open the free Keptick tool and try its fictional Daily invoice sync example. Under Try the outcome check, the two buttons show how an output count changes the monitor status. No account or private endpoint is needed for this example.

  1. Choose Reset to restore the example. It starts at Waiting for first outcome, with Minimum successful outputs set to 1 and Monitor enabled checked.
  2. Choose Expected outputs. This simulates a successful outcome with the current minimum count: one output in the example. The status becomes Healthy.
  3. Choose Zero outputs. This still simulates success, but with zero items. With a minimum of one, the status becomes Output below minimum.

Success: true · Items: 0 · Minimum: 1 → Output below minimum.
The workflow can report success while producing fewer verified outputs than you need.

Check what your minimum means

If an empty result is acceptable for this workflow, set Minimum successful outputs to 0 and choose Zero outputs again. The status is now Healthy: zero meets the configured minimum. Use zero only when no completed output is an acceptable result; otherwise keep the minimum that represents useful work.

Unchecking Monitor enabled shows Paused. Choose Reset when you are finished: it clears the simulated outcome and restores the example fields, including the minimum of one and the enabled monitor.

These buttons only change the local example. They do not connect n8n, send a workflow receipt or test email delivery. A healthy example does not establish that a real workflow is monitored. Follow the setup below when you are ready to connect a monitor, then run the three integration checks to verify normal output, empty output and a missing receipt.

Choose a business result that the workflow can verify

A workflow can run without raising an error and still produce too little useful output. A search may return no matching records. A filter may remove everything. A destination may accept fewer writes than expected.

Choose a result close to the completed work: successfully created records, confirmed deliveries or files that were written and checked. Counting input rows is only appropriate if the outcome you care about is receiving those rows. Do not present the input count as proof that downstream work succeeded.

Validate text before counting it as completed output

A nonzero item count and valid JSON do not establish that imported text is intact. A recent HTTP Request discussion separates the bytes received from the text produced by decoding them. Check the content your workflow needs before reporting those records as verified outputs.

Fictional field: value
{"value":"\uFFFD"} and JSON containing the literal character � both parse to the same value. Both can be valid UTF-8. Invalid input bytes decoded with replacement can also produce that character and leave the JSON parseable.

  1. Define an acceptable record. Validate required fields and the destination result against the source's documented contract. Treat missing or changed text as a review case when it violates that contract. A question mark can be ordinary punctuation, and U+FFFD can already be present in valid source text; neither character alone proves a decoding failure.
  2. Keep the evidence from before decoding. If investigating a text mismatch, retain the relevant original bytes locally through your authorised diagnostic process, along with the declared content type, charset and software version. A decoded string alone may no longer distinguish valid source text from replacement introduced during decoding. A strict UTF-8 failure establishes invalid UTF-8, not the correct alternative charset. Do not guess a codec or rewrite stored records from the displayed character alone.
  3. Count validated results. Report the records that passed your content and destination checks. When the required result fails validation, send an explicit failure outcome. Keptick evaluates the receipt you send; it does not inspect HTTP response bytes, detect encodings or repair imported text.

Evidence reviewed 14 November 2026: our three synthetic Node.js cases from 13 November passed 16 checks of strict UTF-8 decoding, JSON parsing and string predicates. This guide reuses that preserved result. Those checks did not run n8n, a real encoding detector, a legacy decoder, an upstream patch or a data-repair process. They establish the distinction above, not a tested fix for the reporter's workflow.

Two successful runs can still lose a stored update

Scope check: n8n 2.45.7, reviewed 3 November 2026. A current report uses regular/main mode, SQLite and N8N_CONCURRENCY_PRODUCTION_LIMIT=1. Two overlapping webhook runs each increment a shared static counter and finish successfully, but the reporter finds a stored counter of 1 instead of 2. Requests spaced far enough apart produce 2. Two per-run success receipts alone would miss that difference.

  1. Define the stored result you expect. Use the business keys that should exist, or a counter change from a known starting value. A count of successful executions does not verify those results.
  2. Read the destination after the completion window. For overlapping work, use a separate verification step that reads the persisted result afresh. Compare it with the expected keys or change for that window; do not reuse the original run's in-memory static data.
  3. Report what the verification found. Send a verified output count or an explicit failure when the stored result is incomplete. Keptick evaluates the outcomes it receives. It does not lock, repair or independently inspect n8n static data. Test the verification with fictional overlapping runs before depending on it.

Our review of the linked 2.45.7 source confirms that new executions on the v1 regular/main path can load static data before waiting for capacity and do not reload it afterward. The lost-counter reproduction belongs to the reporter; we have not reproduced it or tested a fix. This source review does not establish behavior for other versions or execution engines. Check the current issue before changing your workflow.

Send one receipt for the completed batch

Create a Keptick monitor, choose the expected interval and minimum output count, and copy its private endpoint. After the verification step, send a JSON POST like this:

{
  "eventId": "workflow-run-1042-final",
  "success": true,
  "items": 12,
  "durationMs": 3200
}

Use a unique event ID for each run. A retry of the same receipt should keep the same ID. Keptick deduplicates repeated IDs while its seven-day history is retained. Keep the endpoint private; possession of it allows outcome submission to that monitor.

The downloadable HTTP Request node runs once for its input batch. Replace its endpoint and place it after the node that represents verified completed output. It is a starting node, not an already connected monitoring system.

Handle zero output explicitly

Expected minimum: 1 verified output
Reported success: true
Reported items: 0
Result: Output below minimum

In n8n, a downstream node may not execute when the preceding node produces no items. Attaching the receipt node to that output alone can therefore miss the very zero-result case you wanted to detect.

Create an explicit branch that emits a summary item when no results were produced, then send items: 0 from that branch. Do not enable an empty placeholder and then count that placeholder as one successful business output. If using “Always Output Data,” verify the actual completed-result count separately.

Keptick’s missing-run check can detect that no receipt arrived, but that is a different signal from an explicit zero-output receipt.

Copied [] does not establish zero output

If an AI sub-node shows records in n8n's Logs view but its JSON copy button returns [], verify the selected output before reporting a zero-result run. An empty clipboard export alone is not evidence that the workflow produced nothing. Do not rerun customer work solely because that copy is empty.

Scope check: n8n 3.2.0, reviewed 16 November 2026. In the reported JSON-copy case, our review of the release source found that copying the whole output requests the Main connection, while the displayed data uses the resolved connection type. That copy can be empty when only AI connection data exists, or can copy different, nonempty Main data when both are present.

  1. Check the same execution and output. Record the execution, selected node, run, output branch and connection type through your authorised diagnostic process. Compare the visible records with the actual result at the destination. Keep workflow payloads and credentials private.
  2. Check the complete result. A displayed page may contain only part of the output. Replacing a failed copy with a single page is not a complete export. Confirm that your verification covers the full set of records you intended to check.
  3. Report verified work. Derive the monitor's output count from the result your workflow verified. Neither the clipboard array length nor a visible item count proves that downstream records were saved correctly. If the result cannot be established, retain that uncertainty instead of inventing a success or zero-output claim.

This explanation reuses the preserved 16 November release trace and eight isolated cases with 24 checks. The checks did not mount n8n's components, use the real clipboard, run the n8n suite or test a patch. They cover the whole-output JSON-copy path without a selected value or pinned data. Check your installed version and the current issue before applying a change. Keptick evaluates submitted outcomes; it does not inspect or repair the n8n editor.

Cover execution errors and missing receipts

Import the separate error workflow, replace its endpoint and select it as the monitored workflow’s Error Workflow. Error workflows are intended for failed triggered executions; manual runs may behave differently. Test the actual scheduled or triggered path in a safe workflow.

When the process stops before reporting

If the n8n process stops before the final receipt node runs, that node cannot report the outcome. An error workflow on the stopped instance may not run either. Keep the missing-receipt check outside the workflow process, with an interval and grace period that match when work is actually expected.

A missing receipt tells you that the expected report did not arrive. It does not prove that the work failed or identify a memory problem. Before rerunning the job, check its stored results so already completed work is not repeated.

Docker incident check, reviewed 9 November 2026. A public PDF-extraction report describes a container restart; its cause remains unresolved after the reporter tried a larger Node heap limit. --max-old-space-size controls V8 old space in MiB, not all memory used by the process or container. A higher value alone is not a verified fix.

For an existing incident, an authorised operator can read retained events on the Docker host. Replace START_UTC and END_UTC with a short RFC3339 window such as YYYY-MM-DDTHH:MM:SSZ; the end must be in the past. Replace CONTAINER_ID with the ID of the container that failed. If it was recreated, use its old ID from the incident record.

docker events \
  --since 'START_UTC' --until 'END_UTC' \
  --filter type=container --filter container=CONTAINER_ID \
  --filter event=oom --filter event=die \
  --filter event=start --filter event=restart \
  --format 'time={{.Time}} event={{.Action}} exitCode={{index .Actor.Attributes "exitCode"}}'

The command reads existing events and prints Unix time in seconds, event type and any exit code. A matching oom followed by die provides different evidence from exit code 137 alone, which does not identify the cause. Match the timestamps to the failed execution and keep configuration, credentials and document contents private.

Docker returns only its last 256 retained events. No matching events can mean the relevant history is gone or the wrong container or daemon was checked; it cannot rule out an older OOM. Record that result as inconclusive. Keptick does not read Docker events or repair the workflow. This documentation-based check has not been run against the reporter's instance and establishes no root cause or fix.

A quiet Gmail inbox and a failed poll can look alike

Scope check: n8n 2.45.5, reviewed 30 October 2026. The reported setup uses the scheduler poller with durable cursors enabled. A polling trigger can fail before it creates a workflow execution. In this release, the scheduled Gmail Trigger initializes its cursor before polling. Its outer catch can log an API error without rethrowing it; when no messages have been collected, it can return null. The scheduler records a clean return as a successful poll and creates no execution for a null result. An execution-error workflow does not receive the swallowed error on that path.

No new Gmail message, no execution and no downstream receipt can therefore describe either a quiet mailbox or a broken poll. A receipt node attached to the Gmail output cannot distinguish those cases.

  1. Review source health. Check the existing n8n logs, the configured poller mode and its back-off state. A zero error counter does not prove that the Gmail request succeeded on this path. Keep logs, credentials and mailbox data private.
  2. Choose a meaningful expectation. Use output-count alerts where completed work is actually expected. A Gmail poll every minute does not mean that a new message should arrive every minute.
  3. Verify a separate health check when needed. Send a heartbeat only after that scheduled check succeeds. A timer that reports healthy without checking the source only measures the timer. Keptick does not inspect Gmail or repair n8n polling. Include normal mailbox inactivity and an intentional failure in a safe integration test.

Verified from the release source linked below. Live Gmail error behavior and a workaround were not tested. Check the open issue and your installed release before changing it. The local outcome example above tests receipt interpretation only.

Keptick evaluates an incoming outcome immediately. Missing-run checks start roughly every five minutes; a busy account queue can require another cycle, and email delivery can take longer. This is not an instant paging SLA.

Test three cases before depending on it

  1. Normal output: the verified result meets the configured minimum and the workspace shows Healthy.
  2. Empty output: a deliberate non-production zero-result run submits zero and shows Output below minimum.
  3. No receipt: pause a test workflow long enough to pass its interval and grace period; confirm the missing-run state and intended alert route.

Also test a reported failure if you use an error workflow. Use fictional records or a separate test workflow so the check does not contact customers or alter production work.

One monitor and up to 500 outcomes per day are free. The paid workspace is $19/month, with up to 50 monitors and 15,000 outcomes per account per day. Existing tools such as Healthchecks.io and Cronitor may already cover your needs; start with the result or failure they are not currently showing you.

Sources and context

Try one example. Then use your own.

Track successful outputs, missed runs, and client-facing evidence from your automations. The free tool works without an account. Saved workspaces have a 14-day trial with no card, then $19/month. Your first monitor can stay free within its allowance.

Try the free Keptick tool

Monitoring depends on your workflow sending a receipt. Scheduled missing-run checks run about every five minutes; email delivery can add delay. This is not an emergency alerting system.