Monitor competitor price shifts with Apify, Postgres, OpenAI, and Slack
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 12 nodes and runs on a schedule (every day at 06:00). Along the way it connects Postgres, OpenAI Chat Model, Slack and Apify (community).
How it runs
Trigger: On a schedule (every day at 06:00).
- Select Pages to Monitor (Code): runs custom JavaScript code
- Run Apify Scraper (Apify): run actor and get dataset
- Normalize Product Data (Code): runs custom JavaScript code
- Save Daily Snapshot to DB (Postgres): run a query
- Check Data Integrity (Code): runs custom JavaScript code
- Detect Price Changes (Postgres): run a query
- Send Slack Warning (Slack): post (message)
- Collect Price Changes (Code): runs custom JavaScript code
- Repricing Analysis Agent (AI Agent): runs an AI agent, with model: Chat Model
- Send Slack Alert (Slack): post (message)
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @apify/n8n-nodes-apify is verified or supports 3.0 (used in Run Apify Scraper).
Nodes used (7)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Code
n8n-nodes-base.code - Apify
@apify/n8n-nodes-apify.apify - Postgres
n8n-nodes-base.postgres - AI Agent
@n8n/n8n-nodes-langchain.agent - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Slack
n8n-nodes-base.slack
From the author
Quick overview This workflow runs every morning to scrape competitor product pages with Apify, store daily price snapshots in Postgres/Supabase, detect unusual price moves using SQL views, and post actionable repricing commentary (plus scraping health…