Automation & n8n

Direct answer

What D2 means by Automation & n8n

Production automation needs more than a workflow that runs once. A reliable n8n system needs explicit authentication, validation, idempotency, retry, error handling, persistence, observability and recovery paths.

Question 01

When should a workflow use n8n instead of custom code?

Use n8n when orchestration, integrations and operational visibility are more valuable than building every control surface from scratch. Use custom code where the core logic, throughput or product constraints require it; the two can coexist.

Question 02

How should duplicate webhook events be made idempotent?

Create a stable event or business key, persist processed state and reject or safely replay duplicate events so retries do not create duplicated downstream side effects.

Question 03

What should retry and error workflows look like?

Retry only errors that are plausibly transient, cap attempts with backoff and route terminal failures into an error workflow with enough context for diagnosis and replay.

Question 04

Which reliability layers belong in a production n8n stack?

At minimum: controlled secrets, validation, idempotency, retries, error routing, durable state where needed, logging/metrics, backups and a documented recovery path.

Methodology

How D2 approaches this topic

D2 designs automations around failure modes and operational ownership first, then chooses nodes, APIs and infrastructure that preserve recoverability and observability.

• Separate source evidence from assumptions and keep unresolved items visible.
• State the reporting period and metric definition before comparing outcomes.
• Prefer decision rules that connect operating signals to economics.
• Review platform-specific rules against current first-party documentation when they change.