HumationHuman + Automation
Back to Catalog

Ingredient price trend analysis & buying recommendations with PostgreSQL, API & Slack

Oneclick AI SquadOneclick AI Squad
326 views
2/3/2026
MergeStandardizationWebhookData ProcessingETL
Official Page

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 insights, and sends alerts via email and Slack to help restaurants optimize their purchasing decisions.

What is Price Trend Analysis?

Price trend analysis uses historical price data to identify patterns and predict optimal buying opportunities. The system analyzes price movements over time and generates recommendations on when to buy ingredients based on current trends and historical patterns.

Good to Know

  • Price data accuracy depends on the reliability of external API sources
  • Historical data improves recommendation accuracy over time (recommended minimum 30 days)
  • PostgreSQL database provides robust data storage and complex trend analysis capabilities
  • Real-time alerts help capture optimal buying opportunities
  • Dashboard provides visual insights into price trends and recommendations

How It Works

  1. Daily Price Check - Triggers the workflow daily to monitor price changes
  2. Fetch API Prices - Retrieves the latest prices from an external ingredient pricing API
  3. Setup Database - Ensures database tables are ready before inserting new data
  4. Store Price Data - Saves current prices to the PostgreSQL database for tracking
  5. Calculate Trends - Analyzes historical prices to detect patterns and price movements
  6. Generate Recommendations - Suggests actions based on price trends (buy/wait/stock up)
  7. Store Recommendations - Saves recommendations for future reporting
  8. Get Dashboard Data - Gathers necessary data for dashboard generation
  9. Generate Dashboard HTML - Builds an HTML dashboard to visualize insights
  10. Send Email Report - Emails the dashboard report to stakeholders
  11. Send Slack Alert - Sends key alerts or recommendations to Slack channels

Database Structure

The workflow uses PostgreSQL with two main tables:

  1. price_history - Historical price tracking with columns:

    • id (Primary Key)
    • ingredient (VARCHAR 100) - Name of the ingredient
    • price (DECIMAL 10,2) - Current price value
    • unit (VARCHAR 50) - Unit of measurement (kg, lbs, etc.)
    • supplier (VARCHAR 100) - Source supplier name
    • timestamp (TIMESTAMP) - When the price was recorded
    • created_at (TIMESTAMP) - Record creation time

  2. buying_recommendations - AI-generated buying suggestions with columns:

    • id (Primary Key)
    • ingredient (VARCHAR 100) - Ingredient name
    • current_price (DECIMAL 10,2) - Latest price
    • price_change_percent (DECIMAL 5,2) - Percentage change from previous price
    • trend (VARCHAR 20) - Price trend direction (INCREASING/DECREASING/STABLE)
    • recommendation (VARCHAR 50) - Buying action (BUY_NOW/WAIT/STOCK_UP)
    • urgency (VARCHAR 20) - Urgency level (HIGH/MEDIUM/LOW)
    • reason (TEXT) - Explanation for the recommendation
    • generated_at (TIMESTAMP) - When recommendation was created

Price Trend Analysis

The system analyzes historical price data over the last 30 days to calculate percentage changes, identify trends (INCREASING/DECREASING/STABLE), and generate actionable buying recommendations based on price patterns and movement history.

How to Use

  • Import the workflow into n8n
  • Configure PostgreSQL database connection credentials
  • Set up external ingredient pricing API access
  • Configure email credentials for dashboard reports
  • Set up Slack webhook or bot credentials for alerts
  • Run the Setup Database node to create required tables and indexes
  • Test with sample ingredient data to verify price tracking and recommendations
  • Adjust trend analysis parameters based on your purchasing patterns
  • Monitor recommendations and refine thresholds based on actual buying decisions

Requirements

  1. PostgreSQL database access
  2. External ingredient pricing API credentials
  3. Email service credentials (Gmail, SMTP, etc.)
  4. Slack webhook URL or bot credentials
  5. Historical price data for initial trend analysis

Customizing This Workflow

Modify the Calculate Trends node to adjust the analysis period (currently 30 days) or add seasonal adjustments. Customize the recommendation logic to match your restaurant's buying patterns, budget constraints, or supplier agreements. Add additional data sources like weather forecasts or market reports for more sophisticated predictions.

Ingredient Price Trend Analysis and Buying Recommendations

This n8n workflow automates the process of analyzing ingredient price trends, identifying potential buying opportunities, and sending timely notifications. It's designed to help businesses, particularly in the food and beverage industry, optimize their ingredient procurement by leveraging historical data and external APIs.

What it does

This workflow simplifies and automates the following steps:

  1. Scheduled Trigger: The workflow is initiated on a recurring schedule, ensuring regular price trend analysis.
  2. Fetch Ingredient Data: It makes an HTTP request to an external API (likely a PostgreSQL API as hinted by the directory name) to retrieve current and historical ingredient price data.
  3. Process Data with Custom Logic: A Code node is used to apply custom business logic, likely to analyze price trends, calculate moving averages, identify price dips, or compare current prices against historical benchmarks to determine buying recommendations.
  4. Send Email Notification: Based on the analysis, an email notification is sent, presumably containing the buying recommendations or alerts about significant price changes.
  5. Postgres Database Interaction: Although not directly connected to the main flow in the provided JSON, the presence of a "Postgres" node suggests that the workflow might also interact with a PostgreSQL database for storing historical data, logging analysis results, or retrieving additional context for the recommendations.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance to host and execute the workflow.
  • External API Endpoint: An API endpoint that provides ingredient price data (e.g., a custom PostgreSQL API as suggested by the directory name).
  • SMTP Server Credentials: For the "Send Email" node to function, you'll need SMTP server details (host, port, user, password) configured as an n8n credential.
  • PostgreSQL Database (Optional but recommended): If you intend to use the "Postgres" node for data storage or retrieval, you will need access to a PostgreSQL database and its credentials configured in n8n.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON.
    • In your n8n instance, click "New" in the workflows section.
    • Click the three dots next to the workflow name and select "Import from JSON".
    • Paste the JSON content or upload the file.
  2. Configure Credentials:
    • Locate the "Send Email" node and configure its credentials with your SMTP server details.
    • If you plan to use the "Postgres" node, configure its credentials with your PostgreSQL database connection details.
  3. Configure HTTP Request:
    • Open the "HTTP Request" node.
    • Update the URL to point to your ingredient price data API endpoint.
    • Configure any necessary headers, authentication, or query parameters for your API.
  4. Customize Code Logic:
    • Open the "Code" node.
    • Modify the JavaScript code to implement your specific price trend analysis, recommendation logic, and data transformation requirements. This is where you'll define what constitutes a "buying recommendation."
  5. Set Schedule:
    • Open the "Cron" node.
    • Configure the desired schedule for the workflow to run (e.g., daily, weekly).
  6. Activate the Workflow:
    • Once configured, activate the workflow in n8n to start automated price trend analysis and recommendations.

Related Templates

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616

Tax deadline management & compliance alerts with GPT-4, Google Sheets & Slack

AI-Driven Tax Compliance & Deadline Management System Description Automate tax deadline monitoring with AI-powered insights. This workflow checks your tax calendar daily at 8 AM, uses GPT-4 to analyze upcoming deadlines across multiple jurisdictions, detects overdue and critical items, and sends intelligent alerts via email and Slack only when immediate action is required. Perfect for finance teams and accounting firms who need proactive compliance management without manual tracking. 🏛️🤖📊 Good to Know AI-Powered: GPT-4 provides risk assessment and strategic recommendations Multi-Jurisdiction: Handles Federal, State, and Local tax requirements automatically Smart Alerts: Only notifies executives when deadlines are overdue or critical (≤3 days) Priority Classification: Categorizes deadlines as Overdue, Critical, High, or Medium priority Dual Notifications: Critical alerts to leadership + daily summaries to team channel Complete Audit Trail: Logs all checks and deadlines to Google Sheets for compliance records How It Works Daily Trigger - Runs at 8:00 AM every morning Fetch Data - Pulls tax calendar and company configuration from Google Sheets Analyze Deadlines - Calculates days remaining, filters by jurisdiction/entity type, categorizes by priority AI Analysis - GPT-4 provides strategic insights and risk assessment on upcoming deadlines Smart Routing - Only sends alerts if overdue or critical deadlines exist Critical Alerts - HTML email to executives + Slack alert for urgent items Team Updates - Slack summary to finance channel with all upcoming deadlines Logging - Records compliance check results to Google Sheets for audit trail Requirements Google Sheets Structure Sheet 1: TaxCalendar DeadlineID | DeadlineName | DeadlineDate | Jurisdiction | Category | AssignedTo | IsActive FED-Q1 | Form 1120 Q1 | 2025-04-15 | Federal | Income | John Doe | TRUE Sheet 2: CompanyConfig (single row) Jurisdictions | EntityType | FiscalYearEnd Federal, California | Corporation | 12-31 Sheet 3: ComplianceLog (auto-populated) Date | AlertLevel | TotalUpcoming | CriticalCount | OverdueCount 2025-01-15 | HIGH | 12 | 3 | 1 Credentials Needed Google Sheets - Service Account OAuth2 OpenAI - API Key (GPT-4 access required) SMTP - Email account for sending alerts Slack - Bot Token with chat:write permission Setup Steps Import workflow JSON into n8n Add all 4 credentials Replace these placeholders: YOURTAXCALENDAR_ID - Tax calendar sheet ID YOURCONFIGID - Company config sheet ID YOURLOGID - Compliance log sheet ID C12345678 - Slack channel ID tax@company.com - Sender email cfo@company.com - Recipient email Share all sheets with Google service account email Invite Slack bot to channels Test workflow manually Activate the trigger Customizing This Workflow Change Alert Thresholds: Edit "Analyze Deadlines" node: Critical: Change <= 3 to <= 5 for 5-day warning High: Change <= 7 to <= 14 for 2-week notice Medium: Change <= 30 to <= 60 for 2-month lookout Adjust Schedule: Edit "Daily Tax Check" trigger: Change hour/minute for different run time Add multiple trigger times for tax season (8 AM, 2 PM, 6 PM) Add More Recipients: Edit "Send Email" node: To: cfo@company.com, director@company.com CC: accounting@company.com BCC: archive@company.com Customize Email Design: Edit "Format Email" node to change colors, add logo, or modify layout Add SMS Alerts: Insert Twilio node after "Is Critical" for emergency notifications Integrate Task Management: Add HTTP Request node to create tasks in Asana/Jira for critical deadlines Troubleshooting | Issue | Solution | |-------|----------| | No deadlines found | Check date format (YYYY-MM-DD) and IsActive = TRUE | | AI analysis failed | Verify OpenAI API key and account credits | | Email not sending | Test SMTP credentials and check if critical condition met | | Slack not posting | Invite bot to channel and verify channel ID format | | Permission denied | Share Google Sheets with service account email | 📞 Professional Services Need help with implementation or customization? Our team offers: 🎯 Custom workflow development 🏢 Enterprise deployment support 🎓 Team training sessions 🔧 Ongoing maintenance 📊 Custom reporting & dashboards 🔗 Additional API integrations Discover more workflows – Get in touch with us

Oneclick AI SquadBy Oneclick AI Squad
93