Skip to content
ExpertEnterpriseWeb Scraping & Data ExtractionScheduled trigger31 nodes

Collect job posts: PostgreSQL & Slack

Runs on a schedule across PostgreSQL, Slack and Google Sheets, diffs the two sides and writes only the gaps, then scrapes the values straight out of the HTML. Built for price monitoring, around a "Fetch Target Page" step, in 31 documented nodes.

Collect job posts with HTTP / REST API and PostgreSQL for your team. An original, ready-to-import n8n workflow built around the 'Web Scraping' pattern for data & analytics. It runs on a schedule and orchestrates 31 nodes across PostgreSQL, Slack, Google Sheets. It uses n8n's LangChain AI nodes (Agent/Chain + chat model). Retry-on-fail is enabled on external calls. Import the JSON, add your credentials, and adapt the parameters. What used to take a morning now runs on its own.

Key benefits

  • Keeps PostgreSQL and Slack in step for price monitoring, without anyone re-typing a row
  • Compares PostgreSQL against Slack before writing, so only genuine differences land
  • Safe to re-run: records already in PostgreSQL or Slack are skipped, across all 31 nodes of this price-monitoring build
  • A failed PostgreSQL or Slack call is retried rather than dropped, at any of the 31 nodes in this price-monitoring build
  • Branches rejoin before PostgreSQL, so a price-monitoring run reports once rather than 31 times

Use cases

  • Teams keeping PostgreSQL and Slack aligned by hand for price monitoring
  • Reconciling PostgreSQL against Slack after the two quietly drifted apart
  • Price monitoring work where "Fetch Target Page" is still a manual step before PostgreSQL
  • Price monitoring work that only reaches PostgreSQL on a schedule, when someone remembers to start it

Integrations

PostgreSQLSlackGoogle SheetsHTTP / REST APINotionAnthropic

Workflow preview (31 nodes)

The template's actual node layout and connections. Node parameters and credential slots unlock with the download.

Daily ScheduleSchedule TriggerFetch Target PageHttp RequestExtract Listings (CSS)HtmlRows from ArraysCodeLoad Previous SnapshotPostgresDiff vs Last RunCompare DatasetsAlert New FindingsSlackUpdate Changed RowsPostgresWrite Fresh SnapshotPostgresMerge Diff OutcomesMergeEnrich with Reference D…Http RequestFold In Enrichment Fiel…SetOffload to Post-Process…Execute WorkflowRecord Sub-workflow Res…Execution DataFingerprint for Idempot…CodeDrop Already-Processed …Remove DuplicatesLoad Previous Snapshot 2NotionCompute Drift vs Snapsh…CodeStamp Completion TimeDate TimePersist Run MetadataExecution DataSerialize Run Output (C…Convert To FileArchive Row SnapshotPostgresGuard Non-Empty urlFilterStamp Processing TimeDate TimeSave Execution MetadataExecution DataSummarize Run StatsSetAppend Audit Row (Googl…Google SheetsSend Summary to SlackSlackCapture Failure ContextSetEscalate Failure to Sla…SlackPark in Dead-Letter Que…Google Sheets

What's inside (31 nodes)

A look at the node types this workflow uses. No purchase required — full parameters and credentials are yours after you buy.

CodeCompare DatasetsConvert To FileDate TimeExecute WorkflowExecution DataFilterGoogle SheetsHtmlHttp RequestMergeNotionPostgresRemove DuplicatesSchedule TriggerSetSlack

From download to running in 3 steps

  1. 1
    Import. In n8n, open Workflows → menu → “Import from File” and pick the downloaded JSON.
  2. 2
    Connect. Add your own credentials on the app nodes - n8n highlights exactly which ones need them.
  3. 3
    Activate. Run it once to test, then toggle Active. The automation is live.

What you'll learn

Architect level

The deepest tier - sub-workflow delegation, state snapshots, and full observability.

  • Extracting values from raw HTML with CSS selectors
  • Fetching pages over HTTP and shaping the response into items
  • Diffing against the previous snapshot so only real changes alert

Every node carries its own documentation on the canvas, plus notes explaining why the architecture was built this way, a credential setup guide, troubleshooting, and three practice exercises. Sample data comes pinned to the trigger, so you can hit Execute and watch data flow before connecting a single account.

Common questions

What exactly do I get?

The complete, ready-to-import n8n workflow as a JSON file, delivered instantly after payment. Import it into your own n8n (cloud or self-hosted), add your credentials, and it runs.

How do I import it into n8n?

In n8n, open Workflows, click the three-dot menu, choose “Import from File”, and select the downloaded JSON. Then connect your own app credentials on the highlighted nodes.

Do I need anything else for it to work?

You need your own n8n instance and accounts/credentials for the apps this workflow connects to (PostgreSQL, Slack, Google Sheets, HTTP / REST API, …). No coding is required.

What if it doesn't work for me?

If the file is faulty, won't import, or isn't as described, contact us within 7 days and we'll fix it or refund you - see our refund policy.

Can I modify or resell it?

You can freely adapt and use it in your own or your clients' projects. Reselling or redistributing the template file itself is not permitted.

Original n8n workflow template created and owned by WorkflowCrate. After purchase you receive the ready-to-import JSON file and a license to use and adapt it in your own projects.