Reconcile claimed workflow successes with provider HTTP APIs and code

by Jarvis Piugg · 0 views · created 2026-09-14 · Engineering, AI Summarization

What this workflow does

This workflow has 13 nodes and runs on a schedule (every 15 minutes). It uses only n8n's built-in nodes. It also calls replace_me over HTTP.

How it runs

Trigger: On a schedule (every 15 minutes).

1. Set reconciliation window and thresholds (Edit Fields (Set)): sets 5 fields: window_start, window_end, provider_name…
2. Fetch what WE claimed succeeded (HTTP Request): calls replace_me
3. Fetch what the PROVIDER confirms (HTTP Request): calls replace_me
4. Check both sources answered (Code): runs custom JavaScript code
5. Are both sources readable? (If): checks a condition and branches into true / false
6. Normalise both sides to one shape (Code): runs custom JavaScript code
7. Report window as UNKNOWN not reconciled (Edit Fields (Set)): sets 3 fields: verdict, subject, body
8. Reconcile claims against provider events (Code): runs custom JavaScript code
9. Suppress rows already alerted (Code): runs custom JavaScript code
10. Anything new to report? (If): checks a condition and branches into true / false

…plus 1 more step. See the full node list below.

HTTP calls to: replace_me

Before you upgrade to n8n 3.0

Nodes used (6)

• Schedule Triggern8n-nodes-base.scheduleTrigger
• Edit Fields (Set)n8n-nodes-base.set
• HTTP Requestn8n-nodes-base.httpRequest
• Coden8n-nodes-base.code
• Ifn8n-nodes-base.if
• No Operation, do nothingn8n-nodes-base.noOp

From the author

Quick overview Every 15 minutes this workflow compares your own log of successful runs with the provider's confirmed events over a six-hour window, joins both sides by idempotency key, and emits one of six honest verdicts instead of assuming silence means…

View the original on n8n.io → Check your own copy