Magento 2 low stock alert via Slack & Gmail (MSI compatible)
Daily Magento 2 stock check Automation
It identifies SKUs with low inventory per source and sends daily alerts via:
π¬ Gmail (HTML email)
π¬ Slack (formatted text message)
This automation empowers store owners and operations teams to stay ahead of inventory issues by proactively monitoring stock levels across all Magento 2 sources. By receiving early alerts for low-stock products, businesses can restock before items sell outβensuring continuous product availability, reducing missed sales opportunities, and maintaining customer trust.
Avoiding stockouts not only protects your brand reputation but also keeps your store competitive by preventing customers from turning to competitors due to unavailable items. Timely restocking leads to higher fulfillment rates, improved customer satisfaction, and ultimately, stronger revenue and long-term loyalty.
β Features:
- Filters out configurable, virtual, and downloadable products
- Uses Magento 2 MSI stock per source
- Customizable thresholds (default: β€10 overall or β€5 per source)
- HTML-formatted email report
- Slack notification with a code-formatted
- Runs daily via Cron (08:50 AM)
- No need of any 3rd part Modules
- One time Setup
π Credentials Used
- HTTP Request (Magento 2 REST API using Bearer Token)
- Gmail (OAuth2)
- Slack (OAuth2 or Webhook)
π Tags
Magento, Inventory, MSI, Stock Alert, Ecommerce, Slack, Gmail, Automation
π Category
E-commerce β Magento 2 (Adobe Commerce)
π€ Author
Kanaka Kishore Kandregula
Certified Magento 2 Developer
https://gravatar.com/kmyprojects
https://www.linkedin.com/in/kanakakishore
Magento 2 Low Stock Alert via Slack & Gmail (MSI Compatible)
This n8n workflow automates the process of checking for low-stock products in a Magento 2 store (compatible with Multi-Source Inventory - MSI) and sends out alerts via Slack and/or Gmail. It helps store managers stay informed about critical stock levels, enabling timely restocking and preventing out-of-stock situations.
What it does
This workflow performs the following steps:
- Schedules a Check: The workflow is triggered on a predefined schedule (e.g., daily, hourly) to initiate the stock check.
- Fetches Product Data: It makes an HTTP request to a Magento 2 API endpoint to retrieve product information, likely including stock levels.
- Processes Product Data: A Code node is used to process the raw data received from Magento, likely extracting relevant product details and stock quantities.
- Filters for Low Stock: An If node evaluates the processed product data to identify items that have fallen below a specified low-stock threshold.
- Sends Slack Alert (Optional): For products identified as low stock, it sends a notification to a designated Slack channel with details about the affected products.
- Sends Email Alert (Optional): Additionally, for low-stock products, it can send an email notification via Gmail to a specified recipient list.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Magento 2 Store: Access to a Magento 2 store with API access enabled.
- Magento 2 API Credentials: API URL and authentication details (e.g., OAuth tokens or API keys) for your Magento 2 instance.
- Slack Account: A Slack workspace and a configured Slack credential in n8n to post messages.
- Gmail Account: A Gmail account and a configured Gmail credential in n8n to send emails.
Setup/Usage
- Import the Workflow:
- Download the provided JSON file for this workflow.
- In your n8n instance, click "New" to create a new workflow.
- Go to "File" > "Import from JSON" and upload the downloaded JSON file.
- Configure Credentials:
- HTTP Request (Magento): Edit the "HTTP Request" node (ID: 19).
- Update the
URLto your Magento 2 API endpoint for fetching product data (e.g.,/rest/V1/products). - Configure the
Authenticationmethod (e.g., OAuth2, API Key) with your Magento credentials.
- Update the
- Slack: Edit the "Slack" node (ID: 40).
- Select or create a new Slack credential.
- Specify the
Channelwhere alerts should be posted. - Customize the
Textof the message as needed, using expressions to include product details.
- Gmail: Edit the "Gmail" node (ID: 356).
- Select or create a new Gmail credential.
- Enter the
Toemail address(es) for recipients. - Customize the
SubjectandBodyof the email, using expressions to include product details.
- HTTP Request (Magento): Edit the "HTTP Request" node (ID: 19).
- Configure Low Stock Threshold:
- Edit the "Code" node (ID: 834) to adjust the logic for identifying low-stock products. This is where you'll define what constitutes "low stock" based on your product data structure.
- Edit the "If" node (ID: 20) to refine the conditions for triggering alerts based on the output of the "Code" node.
- Set Schedule:
- Edit the "Schedule Trigger" node (ID: 839).
- Configure the desired
Interval(e.g., every hour, once a day) for the workflow to run.
- Activate the Workflow:
- Once all configurations are complete, save the workflow.
- Toggle the workflow to "Active" to start monitoring your Magento 2 stock levels.
Related Templates
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chatβturn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. π What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing π§ Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation π Required Credentials OpenAI API Setup Go to platform.openai.com β API keys (sidebar) Click "Create new secret key" β Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai β Dashboard β API Keys Generate a new API key β Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) βοΈ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflowβchat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" π― Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration β οΈ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review
This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.
Dynamic Hubspot lead routing with GPT-4 and Airtable sales team distribution
AI Agent for Dynamic Lead Distribution (HubSpot + Airtable) π§ AI-Powered Lead Routing and Sales Team Distribution This intelligent n8n workflow automates end-to-end lead qualification and allocation by integrating HubSpot, Airtable, OpenAI, Gmail, and Slack. The system ensures that every new lead is instantly analyzed, scored, and routed to the best-fit sales representative β all powered by AI logic, sir. --- π‘ Key Advantages β‘ Real-Time Lead Routing Automatically assigns new leads from HubSpot to the most relevant sales rep based on region, capacity, and expertise. π§ AI Qualification Engine An OpenAI-powered Agent evaluates the leadβs industry, region, and needs to generate a persona summary and routing rationale. π Centralized Tracking in Airtable Every lead is logged and updated in Airtable with AI insights, rep details, and allocation status for full transparency. π¬ Instant Notifications Slack and Gmail integrations alert the assigned rep immediately with full lead details and AI-generated notes. π Seamless CRM Sync Updates the original HubSpot record with lead persona, routing info, and timeline notes for audit-ready history, sir. --- βοΈ How It Works HubSpot Trigger β Captures a new lead as soon as itβs created in HubSpot. Fetch Contact Data β Retrieves all relevant fields like name, company, and industry. Clean & Format Data β A Code node standardizes and structures the data for consistency. Airtable Record Creation β Logs the lead data into the βLeadsβ table for centralized tracking. AI Agent Qualification β The AI analyzes the lead using the TeamDatabase (Airtable) to find the ideal rep. Record Update β Updates the same Airtable record with the assigned team and AI persona summary. Slack Notification β Sends a real-time message tagging the rep with lead info. Gmail Notification β Sends a personalized handoff email with context and follow-up actions. HubSpot Sync β Updates the original contact in HubSpot with the assignment details and AI rationale, sir. --- π οΈ Setup Steps Trigger Node: HubSpot β Detect new leads. HubSpot Node: Retrieve complete lead details. Code Node: Clean and normalize data. Airtable Node: Log lead info in the βLeadsβ table. AI Agent Node: Process lead and match with sales team. Slack Node: Notify the designated representative. Gmail Node: Email the rep with details. HubSpot Node: Update CRM with AI summary and allocation status, sir. --- π Credentials Required HubSpot OAuth2 API β To fetch and update leads. Airtable Personal Access Token β To store and update lead data. OpenAI API β To power the AI qualification and matching logic. Slack OAuth2 β For sending team notifications. Gmail OAuth2 β For automatic email alerts to assigned reps, sir. --- π€ Ideal For Sales Operations and RevOps teams managing multiple regions B2B SaaS and enterprise teams handling large lead volumes Marketing teams requiring AI-driven, bias-free lead assignment Organizations optimizing CRM efficiency with automation, sir --- π¬ Bonus Tip You can easily extend this workflow by adding lead scoring logic, language translation for follow-ups, or Salesforce integration. The entire system is modular β perfect for scaling across global sales teams, sir.