Detect Empty/Malformed Workflow Outputs with Keptick Receipt
Overview
This workflow provides a reusable pattern for checking that your n8n workflow produces the expected number of valid completed records. It demonstrates how to count distinct IDs from an output, detect empty results, malformed data, duplicates, and optionally send a lightweight receipt to Keptick for monitoring. The demo uses fictional data so you can test all scenarios without any external service — but you can easily adapt it to inspect real outputs from any node.
How It Works
The workflow is intentionally self-contained and driven by a configuration node. By changing a single parameter (demoCase), you can simulate healthy, empty, invalid, or duplicate results and see how the check behaves. The core logic lives in two Code nodes and one IF node; the HTTP request branch is optional and only runs when sendReceipt is enabled.
Node List
- Read first (Sticky Note) — Instructional note explaining the demo and how to adapt the workflow.
- Run the demo (Manual Trigger) — No auth. Starts the workflow on demand so you can test each scenario interactively.
- Configure check (Set Node) — No auth. Sets four configuration values:
demoCase(healthy/empty/invalid/duplicates),minimumItems(minimum distinct IDs required),recordIdField(field name containing the record ID), andsendReceipt(boolean to enable Keptick delivery). Also includestestReceiptandreceiptUrlfor Keptick setup. - Fictional completed outputs (Code Node) — No auth. Based on the
demoCasevalue, returns a set of fictional records (or empty, malformed, or duplicate data). This node replaces the real output node in production. - Check completed outputs (Code Node) — No auth. Extracts the configuration, filters out empty items, validates the
recordIdFieldfor each record, counts distinct IDs, tallies invalid and duplicate items, and compares againstminimumItems. Returns a result object with check status, pass/fail, and areceiptpayload. - Send receipt enabled? (IF Node) — No auth. Evaluates
sendReceiptfrom the configuration. If true, execution passes to the HTTP request branch; if false, execution goes to the local inspection node. - Send count-only receipt (HTTP Request) — No explicit authentication. The
receiptUrlcontains the Keptick ingestion endpoint including a private token. Sends a POST request with the receipt payload (counts, status, execution ID). No retry on failure. - Verify receipt accepted (Code Node) — No auth. Checks that the API response includes
received: true. If not, throws an error. Returns an enriched result object. - Inspect local result (NoOp) — No auth. A terminal node for viewing the check result directly in the editor when no receipt is sent.
- Use with a real workflow (Sticky Note) — Setup instructions for adapting the pattern to production.
- Optional Keptick monitor (Sticky Note) — Information about Keptick and how to obtain and configure the receipt URL.
Setup Instructions
- No account required for demo: Run the workflow with
demoCase: healthy(default) and inspect the output at the Inspect local result node. ChangedemoCasetoempty,invalid, orduplicatesto see how the guard handles each case. - Connect your real output: Replace the Fictional completed outputs node with the node that emits your completed records. Enable Always Output Data on that node so the check runs even when there are zero rows.
- Configure the guard: Set
recordIdFieldto the field name that holds your unique record identifier (e.g.,id,orderId). SetminimumItemsto the minimum number of distinct valid records you expect. - Optional Keptick monitoring: Create a free monitor at Keptick. Copy the private receipt URL and paste it into the
receiptUrlfield in Configure check. SetsendReceipttotrueandtestReceipttotrueduring setup. When ready for production, settestReceipttofalse. Keep the receipt URL confidential — do not share workflow exports that contain it. - Test thoroughly: Run the workflow with healthy, empty, invalid, and duplicate data to verify your guard behaves as expected.
Use Cases & Adaptations
- Data pipeline validation: Ensure an ETL or sync workflow always produces a minimum number of records before triggering downstream steps.
- API batch processing: Check that all API calls returned valid IDs and no batches were empty or malformed.
- Duplicate detection: The guard counts distinct IDs, making it easy to spot duplicate outputs that might indicate replay or processing errors.
- Custom monitoring: Instead of Keptick, you can replace the HTTP request with a Slack message, email, or database write to alert on failures.
- Error handling: The guard only checks outputs after they are produced. Combine with n8n’s error workflow trigger to catch runs that never reach the check.
Workflow JSON
{
"id": "keptickOutputGuard",
"name": "Detect Empty Workflow Outputs with an Optional Keptick Receipt",
"description": "Check distinct completed-record IDs, including empty and malformed output. Run a fictional local demo without an account; optionally send a count-only receipt to Keptick.",
"active": false,
"nodes": [
{
"id": "intro-note",
"name": "Read first",
"type": "n8n-nodes-base.stickyNote",
"typeVersion": 1,
"position": [
-560,
-340
],
"parameters": {
"content": "## Check the output, including zero\nRun the demo without an account or network request. In Configure check, change demoCase from healthy to empty, invalid, or duplicates. Inspect the last node.\n\nThe sample records are fictional. This checks distinct nonempty IDs in one field, not whether the real business work was correct.",
"width": 570,
"height": 245
}
},
{
"id": "trigger",
"name": "Run the demo",
"type": "n8n-nodes-base.manualTrigger",
"typeVersion": 1,
"position": [
-540,
40
],
"parameters": {}
},
{
"id": "config",
"name": "Configure check",
"type": "n8n-nodes-base.set",
"typeVersion": 3.4,
"position": [
-320,
40
],
"parameters": {
"assignments": {
"assignments": [
{
"id": "case",
"name": "demoCase",
"value": "healthy",
"type": "string"
},
// ... truncated (copy to see full JSON)How to Import This Workflow
- 1Copy the workflow JSON above using the Copy Workflow JSON button.
- 2Open your n8n instance and go to Workflows.
- 3Click Import from JSON and paste the copied workflow.
Don't have an n8n instance? Start your free trial at n8nautomation.cloud
Related Templates
Automated n8n Workflow Backup to GitHub Repository
Overview This workflow automatically backs up every workflow in your n8n instance to a dedicated GitHub repository. It runs on a configurable schedule (or manually) and ensures that all your workflow JSON files are version-controlled and safely stored in a structured folder. The backup process intelligently handles both new workflows (creates a file) and existing ones (updates the file), making it ideal for disaster recovery, collaboration, or tracking changes over time. Step-by-Step Node Breakdown Schedule Trigger (No additional auth) — Triggers the workflow on a recurring interval. By default it runs hourly, but you can customize the schedule (e.g., daily at midnight) to suit your needs. Also supports manual execution via the Manual Trigger node. Manual Trigger (No auth) — Provides a manual button to run the backup immediately, useful for testing or on-demand backups. Get many workflows (Internal n8n API, no external credentials) — Fetches a list of all workflows from your n8n instance using the built-in n8n node. No separate API key is required; it uses the same authentication as your n8n session. Loop Over Items (No auth) — Iterates over each workflow in the list one at a time. This node processes workflows sequentially, preventing race conditions. Getafile (GitHub, OAuth2 / Personal Access Token) — Attempts to retrieve the existing workflow file from your GitHub repository at the path . If the file does not exist (i.e., a new workflow), the node’s error output is triggered. The expression in sanitizes the workflow name by replacing invalid characters (), converting to , and normalizing spaces. Convert to File1 (No auth) — Converts the retrieved GitHub file’s binary data back to a JSON object so it can be compared or overwritten. Extract from File1 (No auth) — Extracts the JSON content from the binary file, preparing it for an update operation. Edit a file (GitHub, OAuth2 / Personal Access Token) — If the workflow already exists on GitHub, this node updates the file with the latest JSON from your n8n instance. The commit message is dynamically generated (e.g., ). Convert to File (No auth) — Converts the current n8n workflow JSON into a binary file () with the workflow’s name as the filename. Create a file (GitHub, OAuth2 / Personal Access Token) — If the workflow is new (i.e., error output), this node creates a new file in the folder. The commit message includes the workflow name and . The workflow loops back to the Loop Over Items node to process the next workflow. The Sticky Note at the top serves as a comment. Setup Instructions GitHub account — You need a GitHub account and a repository (e.g., ) to store the backups. Create an empty repository or use an existing one. GitHub credential in n8n — Add a GitHub OAuth2 or Personal Access Token credential in n8n under Credentials > GitHub. Ensure the token has scope (or at least and ). Configure the nodes — - In Get many workflows, no changes needed. - In Getafile, Create a file, and Edit a file, update the and fields to match your GitHub username and repo name. - Optionally adjust the Schedule Trigger interval (set hours/minutes as desired). Error handling — The workflow references an external error workflow (). If you don’t have that, you should either create a simple error handler or remove the setting in the workflow settings. Use Cases & Adaptations Disaster recovery — Restore all workflows by downloading the JSON files from GitHub and importing them back into n8n. Version history — Track changes to workflows over time via GitHub commits and diffs. Multi-instance sync — Modify the workflow to run on multiple n8n instances, pushing to the same repo (be cautious with conflicts). Selective backup — Add a filter node after to only backup workflows with a specific tag or name pattern. Notification — Insert a Slack or email node after the loop to notify you when a backup completes or if an error occurs.
n8n Upgrade: Detect Affected Workflows with Broken Connections
Summary This workflow helps n8n administrators identify workflows that may have been affected by a past upgrade (specifically n8n version ) where multi-output nodes (like , , ) could have their output connections accidentally re-wired. It provides a self-service webhook endpoint that returns an HTML report listing all workflows with potentially broken connections, making it easy to audit and fix them. Node-by-Node Walkthrough Webhook (No auth) — Listens for HTTP GET requests at the path . When a user visits this URL in their browser, the workflow is triggered. The response mode is set to "Response Node", meaning the final output will be sent back directly. Get all workflows (API Key auth) — Uses the n8n API to fetch all workflows from the instance. You must configure this node with an n8n API credential (a personal access token created under Settings > n8n API). The node has no filters, so it retrieves every workflow. Parse potentially affected workflows (Code node, no auth) — A JavaScript code node that loops through each workflow, inspects its connections, and checks if any multi-output node (defined in the array) has empty outputs. If a node has fewer connected outputs than expected, it is flagged as potentially affected. The node outputs a JSON object with an array of affected workflows, each containing , , , and . Generate Report (HTML node, no auth) — Creates a static HTML document with a styled container, a heading, and an empty list. This serves as the shell for the interactive report generated by the next node. Serve HTML Report (Respond to Webhook node, no auth) — Takes the HTML template from the previous node and injects JavaScript that parses the affected workflows data (from the code node) and dynamically builds a list of clickable links. Each link opens the workflow in a new tab so the admin can inspect and fix the connections. The response headers are set to . Setup Instructions Prerequisites: You must have admin access to the n8n instance (the workflow must be run by the instance owner). Create an n8n API key: Go to Settings > n8n API in your n8n instance and generate a personal access token. Copy the token. Configure the "Get all workflows" node: Add an n8n credential of type "API Key" and paste the token. Leave the filters empty. Customize multi-output nodes (if needed): The code node contains a list with the default nodes (, , ). If you have community nodes with multiple outputs, add them to this array with their correct output count. Activate the workflow: Toggle the workflow to active. Use the report: Open your browser and navigate to . The page will list all affected workflows. Click on a row to open the workflow in a new tab — inspect the connections and re-wire them if needed. Use Cases & Variations Post-upgrade audit: Run this workflow after every n8n upgrade to catch connection issues early. Customized detection: Extend the array in the code node to include any custom node type that has multiple outputs. Slack/Email notification: Instead of serving an HTML report, you could send the list of affected workflows to a Slack channel or email using additional nodes. Scheduled scanning: Replace the Webhook trigger with a Schedule trigger to run the check daily and automatically notify the admin.
Weekly Zigbee2MQTT Backup to SFTP Server
Overview This workflow automates the weekly backup of your Zigbee2MQTT configuration. It triggers every Monday at 2:45 AM, sends a backup request to the Zigbee2MQTT bridge via MQTT, waits for the response containing a base64-encoded ZIP file, decodes it, and uploads the backup to an SFTP server. The workflow includes error handling to stop execution and log failures if anything goes wrong. This is ideal for home automation enthusiasts or administrators who want to ensure their Zigbee network configuration is safely archived off-site or on a central server. Node Breakdown CRON Monday 2:45 am () — No auth. Runs the workflow every Monday at 02:45 AM using the cron expression . This ensures backups happen automatically without manual intervention. Send Zigbee2MQTT backup request () — MQTT Client credentials (broker URL, port, username/password). Publishes the message to the topic . This triggers the Zigbee2MQTT bridge to generate a backup. MQTT Trigger - Backup Response () — MQTT Trigger credentials (same broker). Listens on the topic for the backup data. The trigger waits for a message and passes it to the next node. Parse JSON Object from Message Text () — No auth. Runs JavaScript to parse the incoming MQTT message, extracting the nested field from the JSON payload. This isolates the base64-encoded ZIP content. Convert to File - base64 to binary () — No auth. Takes the property from the parsed JSON (which contains the base64 string) and converts it to a binary file. The output is a ZIP file ready for upload. SFTP zip file content () — SFTP credentials (username/password or private key). Uploads the generated ZIP file to the specified SFTP server path: . The filename includes a timestamp with colons replaced by underscores. Error Handler () — No auth. If any node above fails, this node stops the workflow with the message . It acts as a safety net to prevent partial or corrupted backups. Setup Instructions SFTP Server: You need an SFTP server (e.g., a NAS, cloud VM, or any SSH‑enabled server). Create a user account and note the host, port, username, and password/private key. In n8n, configure an SFTP credential with these details. MQTT Broker: You need a running MQTT broker (e.g., Mosquitto). The workflow connects to the same broker that your Zigbee2MQTT instance uses. In n8n, create an MQTT credential with broker URL, port, username, and password. Zigbee2MQTT: Ensure your Zigbee2MQTT bridge is accessible via MQTT and that it supports the backup request feature (Zigbee2MQTT must be running and connected to the same broker). n8n Configuration: Import this workflow into your n8n instance. Update the SFTP path if needed, and verify the cron schedule matches your desired backup day/time (currently Monday 2:45 AM). Test: Run the workflow manually once to confirm the backup process completes without errors. Check your SFTP server for the uploaded ZIP file. Use Cases & Variations Home Automation Backup: Regularly archive Zigbee network configuration to recover from device failures or coordinator changes. Off-Site Redundancy: Replace the SFTP node with a cloud storage node (e.g., Google Drive, AWS S3) for off‑site backups. Notification on Success/Failure: Add a Telegram or email node after the SFTP upload to inform you of backup completion or errors. Multiple Backup Destinations: Chain additional FTP nodes to send the backup to multiple locations. Different Schedule: Change the cron expression to run daily, or at a specific time on multiple days (e.g., for Monday and Friday).