See llms.txt for all machine-readable content.
A filter or a changed API can make a workflow succeed while processing nothing. One empty run is often normal; three in a row usually is not.
GET /api/v1/executions?includeData=true&status=success for each workflow you list, counts output items on a chosen node (or the last node that ran), and alerts only when the last N consecutive successful runs all output fewer than minItems items (defaults: 3 runs, 0 items). A later run with data, or a run whose execution data is missing, stops the streak, so a single empty success does not page you.zero-items-alert.json.execution:list and execution:read. Add an n8n API credential whose Base URL includes /api/v1, and select it on Get Executions.n8nBaseUrl: your instance origin, without /api/v1 (used to build execution links); workflowIds: comma-separated IDs from each workflow URL; consecutiveEmptyRuns (default 3) and minItems (default 1, i.e. alert on 0 items); countNode: leave blank to use the last executed node, or enter an exact node name; executionsPerWorkflow, alertEmailTo, alertEmailFrom, and optional Slack settingsFor hosted outcome monitoring across all client workflows, try LeadPulse's free Health Check: https://leadpulseops.com/health-check