Agent skill · operations · sundial-org
n8n-workflow-automation
Designs and outputs n8n workflow JSON with robust triggers, idempotency, error handling, logging, retries, and human-in-the-loop review queues. Use when you need an auditable automation that won’t silently fail.
Why this skill is useful
Adds executable n8n workflow JSON generation with robust error handling, logging, and human-in-the-loop review that the AI cannot generate on its own.
What it needs
Requires n8n installed locally. About 2k tokens when loaded. Last updated 2026-03-07. 639 stars on the source repository.
What this skill does
n8n workflow automation with retries, logging, and review queues PURPOSE Designs and outputs n8n workflow JSON with robust triggers, idempotency, error handling, logging, retries, and human-in-the-loop review queues. WHEN TO USE TRIGGERS: Build an n8n workflow that runs every Monday and emails the compliance summary. Add error handling and retries to this workflow, plus a review queue for failures. Create a webhook workflow that logs every run and writes a status row to a tracker. Make this n8n flow idempotent so it does not duplicate records when it reruns. Instrument this workflow with audit logs and a human approval step. DO NOT USE WHEN… You need code-only automation without n8n (use a scripting/CI skill). You need to bypass security controls or hide audit trails. You need to purchase or recommend prohibited items/services. INPUTS REQUIRED: Workflow intent: trigger type + schedule/timezone + success criteria. Targets: where to write results (email/Drive/Sheet/DB) and required fields. OPTIONAL: Existing n8n workflow JSON to modify. Sample payloads / example records. Definition of dedup keys (what makes a record unique). EXAMPLES: Cron: Monday 08:00 Europe/London; send summary email + Drive upload Webhook: receive JSON; route to folders OUTPUTS Default (read-only): a workflow design spec (nodes, data contracts, failure modes). If explicitly requested: workflow.json (n8n importable JSON) + runbook.md (from template). Success = workflow is idempotent, logs every run, retries safely, and routes failures to a review queue. WORKFLOW 1. Clarify trigger: Cron/webhook/manual; schedule/timezone; concurrency expectations. 2. Define data contract: input schema, required fields, and validation rules. 3. Design idempotency: choose dedup key(s) and storage (DB/Sheet) to prevent duplicates on retries. 4. Add observability: generate runid, log start/end, store status row and error details. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sundial-org/n8n-workflow-automation