Ingredient price trend analysis & buying recommendations with PostgreSQL, API & Slack
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Cron. 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 11 nodes and runs on a schedule (legacy Cron node). Along the way it connects Postgres. It also calls api.example-food-prices.com and hooks.slack.com over HTTP.
How it runs
Trigger: On a schedule (legacy Cron node).
- Fetch API Prices (HTTP Request): calls api.example-food-prices.com
- Setup Database (Postgres): run a query
- Store Price Data (Postgres): uses Postgres
- Calculate Trends (Postgres): run a query
- Generate Recommendations (Code): runs custom JavaScript code
- Store Recommendations (Postgres): uses Postgres
- Get Dashboard Data (Postgres): run a query
- Generate Dashboard HTML (Code): runs custom JavaScript code
- Send Email: sends an email over SMTP
- Send Slack Alert (HTTP Request): calls hooks.slack.com
Services it uses
HTTP calls to: api.example-food-prices.com, hooks.slack.com
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Cron in Daily Price Check: replace with Schedule Trigger.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Cron Daily Price Check | Schedule Trigger |
Nodes used (5)
- Cron
n8n-nodes-base.cron - HTTP Request
n8n-nodes-base.httpRequest - Postgres
n8n-nodes-base.postgres - Code
n8n-nodes-base.code - Send Email
n8n-nodes-base.emailSend
From the author
This automated n8n workflow monitors ingredient price changes from external APIs or manual sources, analyzes historical trends, and provides smart buying recommendations. The system tracks price fluctuations in a PostgreSQL database, generates actionable…