Idempotent Order Processing in n8n with Data Table + API

Idempotent order processing in n8n—prevents duplicates with a Data Table + API

This callable sub-workflow ensures each order is processed exactly once in your n8n automation. It checks an n8n Data Table for an existing order_id, skips duplicates, and only calls your external HTTP endpoint for truly new orders—then returns the outcome to the parent workflow.

What this workflow does

Designed to be invoked from a parent workflow via Execute Workflow, it follows a simple idempotent pattern:

• Receives input: gets order_id, customer_id, and total from the parent workflow.
• Checks the Data Table: looks up order_id in an n8n Data Table (default name: orders).
• If found → skip: returns a “skipped” result containing the stored order data.
• If not found → claim & process:
  • Inserts a new row with status received (pending) to claim the order before processing.
  • Sends the order payload to your external processing API using an HTTP POST with header authentication.
  • Updates the Data Table row with the processing result and a processed_at timestamp.
  • Returns the processed result back to the parent workflow.

Use cases

• Prevent duplicate submissions when webhooks or polling jobs re-send the same order.
• Guarantee exactly-once behavior across retries in order processing SaaS pipelines.
• Use Data Table state to coordinate multi-step workflows that must remain consistent.

Technical details

• Callable execution: Execute Workflow Trigger for sub-workflow invocation.
• Idempotency logic: Data Table lookup + if branching.
• Data handling: Set steps to map returned fields.
• API integration: HTTP Request step (HTTP POST) using a configured HTTP Header Auth credential.
• Persistence: Data Table columns for order_id, customer_id, total, status, received_at, and processed_at.