Reconcile Postgres records with an HTTP API and notify drift via Slack

by Melbin Francis ✓ · 1 views · created 2026-09-15 · Document Extraction

What this workflow does

This workflow has 20 nodes and runs on a schedule (every day at 03:00). Along the way it connects Postgres and Slack.

How it runs

Trigger: On a schedule (every day at 03:00).

1. Drift Rules (Edit Fields (Set)): sets 11 fields: api_url, api_records_field, compare_fields…
2. Read The Database Side (Postgres): run a query
3. Read The API Side (HTTP Request): calls an HTTP API
4. Line Them Up (Compare Datasets): uses Compare Datasets
5. Split Out: splits a list into separate items
6. Label Rows Missing From The API (Edit Fields (Set)): sets 9 fields: record_key, drift_kind, drifted_fields…
7. Records That Already Agree (Edit Fields (Set)): sets 9 fields: record_key, drift_kind, drifted_fields…
8. Explain Which Fields Differ (Code): runs custom JavaScript code
9. Label Rows Missing From The Database (Edit Fields (Set)): sets 9 fields: record_key, drift_kind, drifted_fields…
10. Gather Every Difference (Merge): merges the data from its input branches

…plus 7 more steps. See the full node list below.

Services it uses

PostgresSlack

Before you upgrade to n8n 3.0

Nodes used (12)

• Schedule Triggern8n-nodes-base.scheduleTrigger
• Edit Fields (Set)n8n-nodes-base.set
• Postgresn8n-nodes-base.postgres
• HTTP Requestn8n-nodes-base.httpRequest
• Split Outn8n-nodes-base.splitOut
• Compare Datasetsn8n-nodes-base.compareDatasets
• Coden8n-nodes-base.code
• Mergen8n-nodes-base.merge
• Filtern8n-nodes-base.filter
• Ifn8n-nodes-base.if
• Slackn8n-nodes-base.slack
• No Operation, do nothingn8n-nodes-base.noOp

From the author

Quick overview This workflow runs nightly to reconcile a Postgres table with records returned by an HTTP API, detect missing or mismatched rows, flag critical drift in the database, and post a drift summary (and critical alerts) to Slack. How it works 1. Runs…

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