Workflow Templates

Video Guide I prepared a detailed guide that shows the whole process of building an AI tool to analyze Instagram Reels using n8n. Youtube Link Who is this for? This workflow is ideal for social media analysts, digital marketers, and content creators who want to leverage data-driven insights from their Instagram Reels. It's particularly useful for those looking to automate the analysis of video performance to inform strategy and content creation. What problem does this workflow solve? Analyzing video performance on Instagram can be tedious and time-consuming, requiring multiple steps and data extraction. This workflow automates the process of fetching, analyzing, and recording insights from Instagram Reels, making it simpler for users to track engagement metrics without manual intervention. What this workflow does This workflow integrates several services to analyze Instagram Reels, allowing users to: Automatically fetch recent Reels from specified creators. Analyze the most-watched videos for insights. Store and manage data in Airtable for easy access and reporting. Initial Trigger: The process begins with a manual trigger that can later be modified for scheduled automation. Data Retrieval: It connects to Airtable to fetch a list of creators and their respective Instagram Reels. Video Analysis: It handles the fetching, downloading, and uploading of videos for analysis using an external service, simplifying performance tracking through a structured query process. Record Management: It saves relevant metrics and insights into Airtable, ensuring that users can access and organize their video analytics effectively. Setup Create accounts: Set up Airtable, Edify, n8n, and Gemini accounts. Prepare triggers and modules: Replace credentials in each node accordingly. Configure data flow: Ensure modules are set to fetch and analyze the correct data fields as outlined in the guide. Test the workflow: Run the scenario manually to confirm that data is fetched and analyzed correctly.

Description An AI-powered workflow that analyzes any website to identify missing pages that would improve user experience and business performance. Submit a URL, and the system detects existing pages, researches competitors using Perplexity, and generates a professional gap analysis report with prioritized recommendations—saved directly to Google Docs. What this workflow does This automation delivers a complete website page gap analysis: Smart page detection:** Automatically scans website HTML and identifies 15 common page types (About, Contact, Services, Blog, Portfolio, Pricing, FAQ, Testimonials, Team, Careers, Privacy, Terms, etc.) Business type classification:** Determines if the site is ecommerce, portfolio/agency, blog, SaaS, or service-based to tailor recommendations Competitor research:** Uses Perplexity to research 5-7 top competitors in the same industry and identify their page structures AI gap analysis:** GPT-4.1-mini with web search compares the website against industry standards and competitor best practices Prioritized recommendations:** Generates High/Medium/Low priority suggestions with business value explanations and actionable content ideas Google Docs report:** Saves a professional gap analysis report ready to share with clients or stakeholders Setup requirements Tools you'll need: Active n8n instance (self-hosted or n8n Cloud) Google Docs with OAuth access OpenAI API key (GPT-4.1-mini access with web search) Perplexity API key (for competitor research) Estimated setup time: 15–20 minutes Step-by-step setup 1. Connect Google Docs In n8n: Credentials → Add credential → Google Docs OAuth2 API Complete OAuth authentication Create a new Google Doc for storing reports (or use an existing one) Open "Save Report to Google Docs" node Paste the Google Doc URL in the documentURL field 2. Add OpenAI API credentials Get API key: https://platform.openai.com/api-keys In n8n: Credentials → Add credential → OpenAI API Paste your API key Open "OpenAI GPT-4.1 Mini with Web Search" node Select your OpenAI credential Ensure model is set to gpt-4.1-mini Verify Web Search is enabled in the built-in tools section 3. Add Perplexity API credentials Get API key: https://www.perplexity.ai/settings/api In n8n: Credentials → Add credential → Perplexity API Paste your API key Open "Perplexity Competitor Research Tool" node Select your Perplexity credential 4. Share the form URL Open "Submit Website URL for Analysis" node Copy the Form URL from the node settings Share this URL with anyone who needs to run website audits The form accepts a single field: Website URL 5. Test the workflow Open the Form URL in your browser Enter a test website: https://example.com Submit the form Wait 30-60 seconds for the analysis to complete Check your Google Docs—the gap analysis report should appear Verify that: Existing pages are correctly detected Business type is identified Competitor research is included Recommendations are prioritized and actionable 6. Activate the workflow Toggle the workflow to Active at the top The form will now accept submissions 24/7 Each submission generates a new report appended to your Google Doc How it works 1. URL submission via form User opens the form link and submits a website URL they want to analyze. The form triggers the workflow immediately. 2. HTML fetch and extraction The workflow sends an HTTP request to the submitted URL and retrieves the complete HTML source code of the website's homepage. 3. Automated page detection A code node analyzes the HTML to detect 15 common page types: Navigation pages:** Home, About, Contact, Services, Products Content pages:** Blog, Portfolio, Pricing, FAQ Social proof pages:** Testimonials, Team, Careers Legal pages:** Privacy Policy, Terms of Service The detection works by: Scanning all internal links in the HTML Matching URL patterns (e.g., /about, /contact-us, /services) Searching for navigation keywords in anchor text Normalizing URLs (removing query params, anchors, trailing slashes) 4. Business type classification The code also identifies the website's business type based on HTML content patterns: Ecommerce:** Detects shopping cart, checkout, product pages Portfolio/Agency:** Identifies portfolio, case studies, creative work Blog/Content site:** Finds blog posts, articles, news sections SaaS/Software:** Detects subscription, cloud platform, software keywords Service/Agency:** Identifies consulting, marketing, agency services General:** Default if no specific patterns match 5. Deep competitor research with Perplexity The AI Agent instructs Perplexity to: Crawl the target website thoroughly (navigation, footer, hidden menus) Research 5-7 top competitors in the identified business type Document each competitor's page structure Identify industry-standard pages that successful sites consistently have Perplexity focuses only on user-facing pages and ignores technical files (sitemap.xml, robots.txt, admin pages). 6. AI gap analysis and recommendations GPT-4.1-mini with web search: Compares the website's existing pages against competitor structures Identifies genuinely missing pages (cross-references with detected existing pages) Prioritizes recommendations based on business impact (High/Medium/Low) Provides specific business value explanations for each recommendation Suggests actionable content for each missing page Includes competitor examples showing how others use these pages Critical filtering rules: Never recommends pages already detected Excludes technical files and admin pages Only suggests pages with clear business value Each recommendation must be justified 7. Professional report generation The AI Agent outputs a structured report containing: Website Overview:** URL, business type, analysis date Pages Confirmed as Existing:** Formatted list of detected pages Gap Analysis Summary:** Total pages analyzed, existing vs. missing count Recommended Pages to Add:** Detailed recommendations with priority, business value, content suggestions, and competitor examples Implementation Priority Summary:** Quick-reference lists by priority level Next Steps:** 2-3 actionable implementation steps 8. Save to Google Docs The complete report is inserted into your Google Docs document. Each new analysis appends to the same document, creating a running archive of all audits performed. Key features ✅ Automatic page detection: Scans HTML and identifies 15 common page types without manual input—no need to know the site structure beforehand ✅ Business type intelligence: Classifies websites into 6 business categories to provide industry-relevant recommendations ✅ Perplexity-powered research: Deep competitor analysis covering 5-7 top sites in the same niche with complete page inventories ✅ Smart filtering: Never recommends pages that already exist, even if they use different naming conventions or URL structures ✅ Priority-based recommendations: Every suggestion labeled High/Medium/Low with clear business justification—know what to build first ✅ Actionable content ideas: Not just "add a blog"—specific suggestions for what content should go on each recommended page ✅ Competitor examples: See how successful competitors use each recommended page type in their own sites ✅ Google Docs integration: Professional reports saved automatically—no downloads, no formatting, ready to share ✅ Form-based workflow: Single URL submission—anyone can run audits without touching n8n Troubleshooting HTML fetch fails SSL certificate issues:** Some websites block automated requests. Try adding "rejectUnauthorized": false in HTTP Request options. Cloudflare/bot protection:** Sites with aggressive protection may block the request. Test with a simple site first (like your own). Timeout errors:** Increase timeout setting in HTTP Request node to 30-60 seconds for slow-loading sites. Pages not detected correctly Non-standard URL structure:** The workflow detects pages using common patterns (/about, /contact, etc.). If a site uses unusual URLs like /company-info instead of /about, manual review may be needed. Single-page websites:** Sites built as SPAs (single-page applications) with JavaScript routing may not have distinct page URLs in HTML. The workflow works best with traditional multi-page sites. Check detection details:** The code node outputs detection_details showing exactly what was found. Review this to debug false negatives. Perplexity API errors Rate limits:** Perplexity has usage limits. If you hit them, wait or upgrade your plan. API key invalid:** Verify the key is correct at https://www.perplexity.ai/settings/api Quota exceeded:** Check your Perplexity dashboard for remaining credits. OpenAI web search not working Web search disabled:** Ensure "Web Search" is enabled in the OpenAI Chat Model node under "Built-in Tools" Search context size:** Set to "Medium" for balanced performance Model compatibility:** Web search only works with GPT-4 models, not GPT-3.5 Report not saving to Google Docs Re-authenticate OAuth:** Go to Credentials → Google Docs OAuth2 API → Reconnect Document URL format:** Ensure the URL is a valid Google Docs link (not a folder or Sheets link) Permissions:** Verify the connected Google account has edit access to the document Document locked:** Check if the document is open in another tab with unsaved changes AI recommendations are too generic Perplexity research quality:** The AI relies on Perplexity's research. If competitors have similar structures, recommendations may overlap. Try analyzing a more unique website. Business type misclassification:** Check the detected business_type in the code output. If it's wrong, the recommendations will be off-target. Improve prompt:** Edit the AI Agent system prompt to emphasize more specific or creative recommendations for your niche. Use cases Web design agencies: Audit client websites before proposals. Show exactly which pages are missing compared to competitors, with business justification for each recommendation. Win more projects by demonstrating data-driven insights. SEO consultants: Include page gap analysis in site audits. Identify missing pages that competitors rank for (FAQ, pricing, testimonials). Provide clients with actionable roadmaps for site expansion. In-house marketing teams: Analyze competitor websites quarterly to spot new page types or content strategies. Keep your site competitive by identifying gaps before leadership asks about them. Freelance developers: Offer value-add services to existing clients. Run audits on their sites, identify quick wins (missing FAQ, testimonials, pricing pages), and sell additional development work. Startup founders: Before hiring a design agency, understand what pages you actually need. Get a competitor-researched report showing industry standards for your business type—save time and budget. Content strategists: Identify content opportunities beyond blog posts. See which informational pages (FAQ, case studies, resource libraries) competitors have that you're missing. Expected results Time savings:** 2-3 hours saved per website audit (manual competitor research eliminated) Analysis speed:** Complete gap analysis in 30-60 seconds vs. hours of manual work Competitor coverage:** Research 5-7 competitors automatically vs. 1-2 manual comparisons Report quality:** Professional, shareable reports vs. rough notes or spreadsheets Actionability:** Prioritized recommendations with business value vs. generic "add more pages" advice Scalability:** Run 50+ audits per day without additional effort Support Need help or custom development? 📧 Email: info@isawow.com 🌐 Website: https://isawow.com/

N8n recently introduced folders and it has been a big improvement on workflow management on top of the tags. This means the current workflows need to be moved manually to the folders. The simplest idea to try is to convert the current tags into folders and move all the current workflows within the respective tags into the folders This assumes the tag name will be used as the folder name. To Note For workflows that use more than 1 tag, the workflow will be assigned the last tag that runs as the folder. How does it work I took the liberty of simplifying the setup of this workflow that will be needed on your part and also be beginner-friendly Copy and paste this workflow into your n8n canvas. You must have existing workflows and tags before you can run this Set your n8n login details on the node set Credentials with the n8n URL, username, and password. Setup your n8n API credentials on the n8n node get workflows Run the workflow. This opens up a form where you can select the number of tags to move and click on submit The workflow responds with the successful number of workflows that were imported Read more about the template Built by Zacharia Kimotho - Imperol

This n8n template automatically summarizes your WhatsApp group activity from the past week and generates a team report. Why use this? Remote teams rely on chat for communication, but important discussions, decisions, and ideas get buried in message threads and forgotten by Monday. This workflow ensures nothing falls through the cracks. How it works Runs every Monday at 6am to collect the previous week's group messages Groups conversations by participant and analyzes message threads AI summarizes individual member activity into personal reports Combines all individual reports into one comprehensive team overview Posts the final report back to your WhatsApp group to kick off the new week Setup requirements WhatsApp (whapAround.pro) no need Meta API Gemini AI (or alternative LLM of choice) Best practices Use one workflow per WhatsApp group for focused results Filter for specific team members if needed Customize the report tone to match your team culture Adjust the schedule if weekly reports don't suit your team's pace Customization ideas Send reports via email instead of posting to busy groups Include project metrics alongside message summaries Connect to knowledge bases or ticket systems for additional context Perfect for project managers who want to keep distributed teams aligned and ensure important conversations don't get lost in the chat noise.

Template Overview This template is designed for individuals and businesses who want to maintain a consistent presence on the Fediverse while also posting on Threads or managing multiple Fediverse profiles. By automating the process of resharing statuses or posts, this workflow saves time and ensures regular engagement across accounts. Use Case The template addresses the challenge of managing activity across Fediverse accounts by automatically boosting or resharing posts from a specific account to your own. It is especially helpful for users who want to consolidate engagement without manually reposting content across multiple platforms or profiles. How It Works The workflow runs on a scheduled trigger and retrieves recent posts from a specified Fediverse account, such as your Threads.net account. It uses a JavaScript filter to identify posts from the current day and then automatically boosts or reshares them to your selected Mastodon profile. Preconditions You need a Mastodon account with developer access. Identify a Threads.net or other Fediverse account which you want to boost. Basic familiarity with APIs and setting up credentials in n8n. Setup Steps Step 1: Create a Developer Application on Mastodon Log in to your Mastodon account and navigate to Preferences > Development > New Application. Fill out the required information and create your application. Set Scopes to atleast read, profile, write:statuses. Click Submit. Note down the access token generated for this application. Step 2: Get the Account ID Use the following command to retrieve the account ID for the profile you want to boost: curl -s "https://mastodon.social/api/v1/accounts/lookup?acct=<ACCOUNTNAME>" Alternatively, paste the URL into a GET node on n8n. From the returned JSON, copy the "id" field value (e.g., {"id":"110564198672505618", ...}). Step 3: Update the "Get Statuses" Node Replace <ACCOUNTID> in the URL field with the ID you retrieved in Step 2: https://mastodon.social/api/v1/accounts/<ACCOUNTID>/statuses Step 4: Configure the "Boost Statuses" Node Authentication type will already be set to Header Auth. Grab the access token from Step 1. In the Credential for Header Auth field, create a new credential. Click the pencil icon in the top-left corner to name your credential. In the Name field, enter Authorization. In the Value field, enter Bearer <YOUR_MASTODON_ACCESS_TOKEN>. (Note: there is a space after "Bearer.") Save the credential, and it should automatically be selected as your Header Auth. Step 5: Test the Workflow Run the workflow to ensure everything is set up correctly. Adjust filters or parameters as needed for your specific use case. Customization Guidance Replace mastodon.social with your own Mastodon domain if you're using a self-hosted instance. Adjust the JavaScript filter logic to meet your specific needs (e.g., filtering by hashtags or keywords). For enhanced security, store the access token as an n8n credential. Embedding it directly in the URL is ++not recommended++. Notes This workflow is designed to work with any Mastodon domain. Ensure your Mastodon account has appropriate permissions for boosting posts. By following these steps, you can automate your Fediverse engagement and focus on creating meaningful content while the workflow handles the rest!

Setting up n8n workflow Overview The Docker Grafana WHMCS module uses a specially designed workflow for n8n to automate deployment processes. The workflow provides an API interface for the module, receives specific commands, and connects via SSH to a server with Docker installed to perform predefined actions. Prerequisites You must have your own n8n server. Alternatively, you can use the official n8n cloud installations available at: n8n Official Site Installation Steps Install the Required Workflow on n8n You have two options: Option 1: Use the Latest Version from the n8n Marketplace The latest workflow templates for our modules are available on the official n8n marketplace. Visit our profile to access all available templates: PUQcloud on n8n Option 2: Manual Installation Each module version comes with a workflow template file. You need to manually import this template into your n8n server. n8n Workflow API Backend Setup for WHMCS/WISECP Configure API Webhook and SSH Access Create a Basic Auth Credential for the Webhook API Block in n8n. Create an SSH Credential for accessing a server with Docker installed. Modify Template Parameters In the Parameters block of the template, update the following settings: server_domain – Must match the domain of the WHMCS/WISECP Docker server. clients_dir – Directory where user data related to Docker and disks will be stored. mount_dir – Default mount point for the container disk (recommended not to change). Do not modify the following technical parameters: screen_left screen_right Deploy-docker-compose In the Deploy-docker-compose element, you have the ability to modify the Docker Compose configuration, which will be generated in the following scenarios: When the service is created When the service is unlocked When the service is updated nginx In the nginx element, you can modify the configuration parameters of the web interface proxy server. The main section allows you to add custom parameters to the server block in the proxy server configuration file. The main\_location section contains settings that will be added to the location / block of the proxy server configuration. Here, you can define custom headers and other parameters specific to the root location. Bash Scripts Management of Docker containers and all related procedures on the server is carried out by executing Bash scripts generated in n8n. These scripts return either a JSON response or a string. All scripts are located in elements directly connected to the SSH element. You have full control over any script and can modify or execute it as needed.

Try It Out! This n8n template demonstrates how to build an autonomous AI news agent using Decodo MCP that automatically finds, scrapes, and delivers fresh industry news to your team via Slack. Use cases are many – automated news monitoring for your industry, competitive intelligence gathering, startup monitoring, regulatory updates, research automation, or daily briefings for your organization. How it works Define your news topics using the Set node – AI, MCP, web scraping, whatever matters to your business. The AI Agent processes those topics using the Gemini Chat Model, determining which tools to use and when. Here's where it gets interesting: Decodo MCP gives your AI agent the tools to search Google, scrape websites, and parse content automatically – all while bypassing geo-restrictions and anti-bot measures. The agent hunts for fresh articles from the last 48 hours, extracts clean data, and returns structured JSON results. Format Results cleans up the AI's messy output and removes duplicates. Your polished news digest gets delivered to Slack with clickable links and summaries. How to use Schedule trigger runs daily at 9 AM – adjust timing or swap for webhook triggers as needed. Customize topics in the Set node to match your industry. Scales effortlessly: add more topics, tweak search criteria, done. Requirements Decodo MCP credentials (free trial available) – grab the Smithery connection URL with keys and paste it straight into your n8n MCP node. Done. Gemini API key for the AI processing – drop it into the Google Gemini Chat Model node and pick whichever Gemini model fits your needs. Slack workspace for delivery – n8n's Slack integration docs have you covered. What the final output looks like Here's what your team receives in Slack every morning: Need help? Join the Discord or email support@decodo.com for questions. Happy Automating!

Disclaimer: Community nodes are used, and template can only be used on self-hosted n8n instances. This n8n template from Intuz provides a complete solution to automate your entire B2B lead generation pipeline, from discovering recently funded companies to drafting hyper-personalized outreach emails with AI. Who's this workflow for? Sales Development Representatives (SDRs) Business Development Teams Growth Hackers Startup Founders Marketing Agencies How it works 1. Scrape Funded Companies: The workflow begins by using Apify to scrape a target list of recently funded companies directly from a Crunchbase search. 2. Enrich with Apollo.io: It takes each company and uses the Apollo.io API to find key decision-makers (like VPs, Directors) and enrich their contact information, including finding their email addresses. 3. Populate Google Sheets: All the gathered lead data—company name, contact name, title, email, LinkedIn URL, etc.—is neatly organized and added to a Google Sheet. 4. AI-Personalized Email Crafting: The workflow sends the lead's information to OpenAI (GPT-4) with a highly specialized prompt, instructing it to write a concise, impactful, and hyper-personalized "first touch" cold email. 5. Update Lead List with Email Content: Finally, the unique, AI-generated email is saved back into the Google Sheet alongside the corresponding lead's information, making it ready for you to send. Pre-conditions and Requirements Before you can successfully execute this workflow, you must have the following accounts, credentials, and assets in place. 1. n8n Instance: You need an active n8n instance (self-hosted). 2. Apify Account & Crunchbase Access: Apify Account: A registered account on Apify. Crunchbase Account: An active, logged-in Crunchbase account (a paid subscription is recommended for accessing detailed search filters). 3. Apollo.io API: You need an Apollo.io plan that includes API access. You can generate the API from settings. 4. Google Sheet: Create a new Google Sheet to store your leads. The workflow is configured for two tabs: one for raw data ("HealthCare" in the template) and one for email generation ("Company sheet"). 5. OpenAI Account: An account with OpenAI with API access and billing set up. Setup Instructions 1. Apify Connection: Connect your Apify account in the Run an Actor node. You'll need an apify scrapper, here's the link In the Custom Body field, update the search.url with your target Crunchbase discovery URL and provide a valid cookie for authentication. 2. Apollo.io Connection: Connect your Apollo.io account using HTTP Header Authentication in the three Apollo nodes. You will need to provide your API key. 3. Google Sheets Connection: Connect your Google Sheets account. Create a spreadsheet and update the Document ID and Sheet Name in the three Google Sheets nodes to match yours. Ensure your sheet columns are set up to receive the data. 4. OpenAI Connection: Connect your OpenAI account in the Message a model node. The prompt is pre-engineered for high-quality output, but you can tailor it to better fit your specific value proposition. 5. Activate Workflow: Click "Execute workflow" to run the automation manually and watch your AI-powered lead list build itself. Customization Guide This workflow is a powerful template. To adapt it to your specific business needs, you should review and modify the following nodes. 1. Changing Your Target Companies (The Source) Node: Run an Actor What to change: The search.url parameter inside the customBody. How to do it: Go to Crunchbase and perform a search for your ideal companies (e.g., filter by different funding rounds, industry, location, keywords, etc.). Copy the URL from your browser's address bar after the search results have loaded. Paste this new URL as the value for "search.url" in the node. You can also adjust "count": 10 to pull more or fewer companies per run. Be mindful of Apify and Apollo credit usage. 2. Defining Your Ideal Contact Persona Node: Apollo - Get User What to change: The person_seniorities and person_titles arrays in the jsonBody. How to do it: 1. Seniority: Modify the person_seniorities list to match who you sell to. Examples: ["c_level", "founder"] or ["manager", "contributor"]. 2. Job Titles: This is crucial. Replace the existing list of titles ("engineering", "technology", etc.) with keywords relevant to your target buyer. For example, if you sell to marketing teams, you might use: ["marketing", "demand generation", "growth", "content", "brand"]. 3. Configuring Your Google Sheet Destination Nodes: Append or update row in sheet and Update row in sheet What to change: The documentId and sheetName. How to do it: Open your Google Sheet. The documentId is the long string of characters in the URL between /d/ and /edit. Copy and paste it into the "Document ID" field in both nodes. The sheetName (or Sheet ID/gid) needs to be set for your specific tabs. Make sure the sheet names/IDs in the nodes match the tabs in your document. Column Mapping: If you change the column names in your Google Sheet, you must update the column mapping inside these nodes to ensure the data is written to the correct place. 4. Tailoring the AI Email Generation Node: Message a model (OpenAI) What to change: The prompt, the model, and the input variables. How to do it: The Prompt: This is the heart of your outreach. Read the entire prompt carefully and edit it to reflect your company's value proposition, tone of voice, and specific call-to-action. Value Proposition: Change the line "We help them cut that specific infrastructure spend..." to match what your product does. Use a powerful, single data point if you have one. Call-to-Action (CTA): Modify the final question ("Curious if infra efficiency is on your roadmap...") to something that fits your sales process. Tone: Adjust the initial instructions (e.g., "Your tone is that of a peer...") if you want a different style. The Model: The workflow uses gpt-4.1. You can switch to a different model like gpt-4o (potentially better/faster) or gpt-3.5-turbo (much cheaper, but lower quality) depending on your budget and needs. Input Variables: The prompt uses {{ $json['Company Name'] }}, {{ $json['Person Designation'] }}, and {{ $json.Industry }}. If you want to add more personalization (e.g., based on a company's funding amount), you would first need to ensure that data is passed to this node, then add the new variable (e.g., {{ $json['Funding Amount'] }}) into the prompt. Connect with us Website: https://www.intuz.com/services Email: getstarted@intuz.com LinkedIn: https://www.linkedin.com/company/intuz Get Started: https://n8n.partnerlinks.io/intuz For Custom Workflow Automation Click here- Get Started

(Retail) Customer Cleanup API → Supabase and send Notification This workflow provides an API-first solution to validate, clean, deduplicate and store customer data in Supabase. It ensures consistent customer records, prevents duplicates and keeps both internal teams and customers informed through automated notifications. This workflow acts as a backend customer intake API. It validates and normalizes incoming customer data, checks for existing users in Supabase, stores new customers safely and returns clear API responses. Internal teams receive Slack and Telegram updates, while customers get an email confirmation on successful creation. You receive: Centralized customer data validation** Automatic duplicate prevention** Supabase-backed customer storage** Real-time API responses** Team notifications + user confirmation email** Ideal for retail, e-commerce and SaaS teams that want clean customer data without manual intervention. Quick Start – Implementation Steps Import the provided n8n workflow JSON. Configure Supabase credentials with read/write access. Connect Slack, Telegram and Gmail/SMTP credentials. Copy the Webhook URL and use it as your customer intake API. Activate the workflow — your customer API is live. What It Does This workflow automates customer data intake and processing: Receives customer data via a POST API call. Cleans and normalizes names, email and phone numbers. Validates required fields and formats using JavaScript. Aggregates clear, field-specific validation errors. Checks Supabase to prevent duplicate users. Stores valid, new customers in Supabase. Returns structured API responses (success, validation error or duplicate). Sends notifications to Slack and Telegram. Emails the customer after successful account creation. This ensures reliable, consistent customer records across systems. Who’s It For This workflow is ideal for: Retail and e-commerce platforms CRM and customer data teams SaaS product teams Backend automation teams Marketing teams needing clean contact lists Developers building API-driven systems Requirements to Use This Workflow To run this workflow, you need: n8n instance** (cloud or self-hosted) Supabase project** with a customers table Supabase service role key Slack workspace** with API access Telegram bot** + chat ID Gmail or SMTP account** for user notifications How It Works API Request – Client sends customer data to the webhook endpoint. Validation & Cleanup – JavaScript validates and formats data. Validation Fail – Returns 400 response with clear error messages. Duplicate Check – Supabase is queried using the email address. Duplicate Found – Returns 409 response without creating a record. Create Customer – New customer is saved in Supabase. Success Response – API confirms successful creation. Notifications – Slack, Telegram and customer email are triggered. Setup Steps Create a Supabase table with fields for customer data, validation status and errors. Add Supabase credentials to n8n. Import the workflow JSON into n8n. Configure the Webhook node and copy the API URL. Review the validation logic if custom rules are required. Configure Slack, Telegram and email credentials. Test using Postman for invalid, duplicate and valid requests. Activate the workflow. How To Customize Nodes Customize Validation Rules Update the JavaScript validation node to add country-specific phone rules or additional fields. Customize Duplicate Logic Extend duplicate checks to include phone numbers or other identifiers. Customize Notifications Modify Slack and Telegram messages, add emojis, mentions or execution metadata. Add-Ons (Optional Enhancements) You can extend this workflow to: Add API key authentication Enable rate limiting Log failed attempts separately Support multi-country phone validation Add CRM or email marketing sync Implement soft deletes or upserts Use Case Examples 1. Customer Registration API Centralize customer creation for web and mobile apps. 2. Data Hygiene Automation Prevent invalid or duplicate contacts in your database. 3. Retail & CRM Integration Keep customer records consistent across systems. 4. Marketing Readiness Ensure only clean, valid contacts enter campaigns. Troubleshooting Guide | Issue | Possible Cause | Solution | | ----------------------- | ----------------------------- | ----------------------------------- | | Validation always fails | Incorrect payload structure | Ensure data is sent in request body | | Duplicate user created | Duplicate check misconfigured | Verify Supabase filter conditions | | No Slack alert | Invalid credentials | Reconnect Slack API | | No email sent | Gmail/SMTP not configured | Verify sender account | | API not responding | Webhook not active | Activate the workflow | Need Help? If you need help customizing or extending this workflow, adding authentication, scaling for high traffic, integrating CRMs or enhancing validation, the n8n automation team at WeblineIndia can assist you with production-ready automation and integration support. Contact us today.

Description Execute email actions directly from Notion. Set an email’s status to Responded, Delegated, Routed, or Archived, and this workflow handles the Gmail action, Slack notification, or Jira routing automatically. Context This is the action layer for the Inbox Zero Engine. When you set an email’s status in Notion, the workflow executes the appropriate action: • Responded: sends the draft reply via Gmail thread • Delegated: forwards the email + sends a Slack DM to the delegate • Routed: creates items in Jira, RICE+ backlog, or customer health • Archived: applies Gmail labels After each action, the entry is marked as “Processed” in Notion. Who is this for? • PMs using Notion as their command center • Anyone who wants to process email without leaving Notion • Teams that delegate and route emails frequently Requirements • Notion account with Email Intelligence database • Gmail OAuth2 • Slack Bot token How it works Trigger Watches Email Intelligence in Notion for status changes. Action Router 4-way switch: Responded sends reply, Delegated forwards + DMs, Routed creates tickets, Archived labels in Gmail. Closed Loop Updates each entry to “Processed” with timestamp and reference. What you get • One-click email actions from Notion • Automatic Gmail replies, forwards, and archiving • Slack notifications for delegated emails • Full audit trail in Notion About me : I’m Yassin a Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin

How it works Connects to your n8n instance via API and fetches all credentials you have set up Maps each credential type to its real service name (supports 40+ services: OpenAI, Slack, Notion, Airtable, Google, Stripe, and more) Sends the full list to Claude AI, which researches current pricing tiers, free limits, and API rate limits for every service Builds a colour-coded HTML email report sorted by tier: 🟢 Free · 🟡 Freemium · 🔴 Paid only Includes: free quota, paid plan starting price, API rate limit, and key notes for each service Set up steps Create an HTTP Header Auth credential named n8n API Key — Header Name: X-N8N-API-KEY, Header Value: your n8n API key (Settings → API → Create API Key) Connect your Anthropic account credential for Claude AI pricing research Connect your Gmail OAuth2 credential for the report email Open the Configuration node and set your n8n instance URL and notification email address Run manually or add a Schedule trigger for automated weekly reports

Who is this for? E-commerce store owners, product managers, marketplace sellers, and pricing analysts who want to automatically track competitor pricing and get actionable alerts when their products are overpriced or underpriced relative to the market. What this workflow does This workflow runs daily to compare your product prices against live competitor prices from Google Shopping. It identifies pricing gaps, calculates suggested prices that protect your margins, sends instant Slack alerts for critical issues, logs everything to a historical price tracking sheet, and delivers a comprehensive daily summary via Slack and email. How it works Daily trigger fires on a configurable schedule (default: every 24 hours). Reads your product catalog from a Google Sheet — auto-detects column names regardless of naming convention. Searches Google Shopping for each product using SearchAPI to find real-time competitor prices. Analyzes the pricing gap — compares your price to the market average and classifies each product as UNDERPRICED, SLIGHTLY_UNDER, COMPETITIVE, SLIGHTLY_OVER, or OVERPRICED. Suggests optimal prices based on market averages while maintaining a minimum margin above your cost. Sends instant Slack alerts when a product hits critical or warning thresholds. Logs all results to a price_log tab in your Google Sheet for trend analysis. Sends a daily summary via Slack message and HTML email with a full breakdown of all products. Setup steps Create a Google Sheet with a products tab containing columns: product_name, my_price (required), and optionally sku, my_cost. Add a second tab called price_log with headers: date, product_name, sku, my_price, my_cost, margin_now, competitor_lowest, competitor_average, competitor_highest, competitor_count, gap_pct, signal, suggested_price, action. Get a SearchAPI key from searchapi.io and set it as the n8n environment variable SEARCHAPI_KEY. Connect Google Sheets OAuth2 credentials and update the sheet ID in both Sheets nodes. Connect Slack OAuth2 credentials and configure your alert channel. Connect Gmail OAuth2 credentials and update the recipient email address. Requirements n8n instance (self-hosted or cloud) SearchAPI.io account and API key Google Cloud project with Sheets API enabled Slack workspace with a bot configured Gmail account with OAuth2 credentials How to customize Pricing thresholds** — Adjust the 0.85, 0.95, 1.05, 1.15 multipliers in the "Analyze Pricing Gap" node to change sensitivity. Minimum margin** — Change the 1.15 cost multiplier to set your floor margin (default: 15%). Schedule** — Modify the trigger interval for more or less frequent checks. Notifications** — Replace or add Slack/email with Telegram, Discord, Microsoft Teams, or webhooks. Region** — Change the gl parameter in the search node from us to your target market country code.