n8n workflow automation

• You need a scheduled (cron) or webhook-triggered n8n workflow and want error handling, retries, and logging baked in from the start.
• You are adding idempotency to an existing n8n flow that duplicates records when it reruns.
• You need a human approval step — a review queue where failed or flagged items wait for manual sign-off before reprocessing.
• You want an auditable automation: every run generates a run_id, logs start/end status, and writes a status row to a tracker (Sheet, DB, etc.).

• You need code-only automation with no n8n dependency — reach for a scripting or CI/CD skill instead.
• You need to bypass security controls or suppress audit trails.
• Your destination systems, dedup keys, or credential strategy are entirely unknown and you are not ready to define them.

The skill defines one or more dedup keys and selects an appropriate storage backend (Sheet or DB) to track processed records. Workflows can safely rerun after failures without creating duplicate entries.

Every node in the generated workflow includes dedicated error branches. Transient failures trigger configurable retry-with-backoff logic; permanent failures route items to a review queue rather than silently dropping them.

Each run receives a unique run_id. Start time, end time, record counts, and error details are written to a status log (Sheet, DB, or similar), giving you a full audit trail for every execution.

Failed or flagged items are written to a review queue (Sheet or DB). A human approval step is required before those items are reprocessed, preventing silent data loss and enabling controlled remediation.

Threshold checks are embedded in the workflow design. If record counts or success rates fall outside expected bounds, the workflow stops and fires an alert rather than completing with undetected errors.

When explicitly requested, the skill outputs a valid n8n-importable workflow.json alongside a runbook.md that documents nodes, data contracts, failure modes, and operational procedures.

Describe a cron trigger (e.g., Monday 08:00 Europe/London), target recipients, and a Drive upload destination. The skill produces a Cron → Fetch → Aggregate → Email workflow with retry branches and a review queue for any send failures.

Provide a sample incoming JSON payload and a destination tracker. The skill generates a Webhook → Validate → Process → Append Status Row workflow that logs every run and routes errors to a notification + queue node.

Supply an existing n8n workflow JSON and define the dedup key (e.g., record ID). The skill redesigns the flow to check for existing records before writing, ensuring reruns after failures never produce duplicate rows.

For workflows that process sensitive or high-value records, the skill adds a HITL gate: failed items land in a Sheet/DB queue, and a human must approve each item before the workflow reprocesses it.