n8n HTTP API Reconciliation Workflow: Match Success Runs

Stop Silent Successes: Reconcile n8n “Success” Runs with Your Provider via HTTP

This n8n HTTP API Reconciliation Workflow (Match Success Runs) runs hourly to compare your internal log of successful workflow runs against a provider’s event records. It then reconciles both sources using a shared idempotency key, emitting a traceable alert payload only when mismatches or unknowns are detected—otherwise it stays silent.

What this workflow does

• Runs on a schedule: Executes every hour.
• Uses a reconciliation window: Compares the last two hours of activity, with the end time lagged by 15 minutes to handle provider ingestion delays.
• Fetches internal successes: Calls your internal logging endpoint over HTTP to retrieve the workflow actions you recorded as successful.
• Fetches provider events: Calls the provider’s events/messages API over HTTP for the same time window.
• Reconciles by idempotency: Joins records by the idempotency key and classifies each item as ACCEPTED, DELTA, or UNKNOWN, producing an evidence-rich reconciliation report.
• Alerts only on issues: If any item is DELTA or UNKNOWN, it prepares an alert subject and body containing the full reconciliation JSON. If everything is confirmed, it produces no action.

Use cases

• Validate that “successful” n8n actions truly match provider-side event delivery.
• Detect ingestion delays, retry edge cases, or mismatched idempotency keys across systems.
• Support SaaS operators with audit-grade evidence when reconciliation is inconsistent.

Technical details

• Node stack: if, set, code, no op, sticky note, HTTP Request.
• Integrations: Two HTTP Request endpoints—your internal “claimed successes” API and the provider events/messages API (including required authentication).
• Key requirement: Both sources must share the same stable idempotency_key field (e.g., idempotency_key).
• Config step: Update the reconciliation code to align with your response shapes (e.g., CLAIM_PATH / PROVIDER_PATH).

Built for n8n users, automation engineers, and SaaS operators who need reliable HTTP-based reconciliation and actionable alerts when reality doesn’t match “success.”