Reconcile CRM vs Invoicing Owner Fields (HTTPS API, n8n)

Reconcile CRM billing details with invoice summaries—safely and automatically (HTTPS API, n8n)

This n8n workflow reconciles billing-related data between a CRM and invoicing system by field ownership. It reads both sides, applies only the source-owned differences, verifies the target independently, and maintains a metadata journal to prevent uncertain writes.

What this workflow does

• Receives an HTTPS request via authenticated webhook: the webhook accepts only an entity reference. The caller cannot provide field values or a destination URL.
• Chooses ownership using distinct source tokens: different tokens select whether CRM ownership or invoicing ownership drives the comparison and updates.
• Validates and checks the entity journal: if intent is unresolved or outcomes are uncertain, it blocks new requests in either direction before any provider write happens.
• Reads normalized data from both adapters: both adapters return current records with strong ETags, then the workflow compares only the authenticated source’s owned fields.
• Writes only when needed—and only per owned field: matching values result in no PATCH. For differences, it persists a minimal intent row, re-reads the source, and blocks write if the source changes or is unavailable.
• Uses conflict-safe updates: per-field target PATCH requests include If-Match and an Idempotency-Key. Revision conflicts or uncertain outcomes are retained for review.
• Verifies after acknowledgement: after a successful acknowledgement, it performs an independent target GET to confirm expected fields, revision, and write marker—then updates the final journal before returning “applied.”

Use cases

• Keep CRM billing details aligned with invoice summaries after edits in either system.
• Prevent double updates with idempotency and handle revision conflicts cleanly.
• Audit and replay reconciliation attempts when outcomes are uncertain or data is missing/deleted.

Technical details

• n8n nodes: webhook, if, code, HTTP request, data table, sticky note.
• Uses vendor-neutral REST adapters for CRM and invoicing records, with ETags, If-Match, PATCH, and independent GET verification.
• Maintains a metadata journal for replay and uncertain-write review.