Workflow Templates

This workflow will trigger daily at 6am to retrieve your day's calendar events from Google Calendar and send them as a summary message to Slack. I've used a low-code method to filter the dates as I can't code much in JSON :) Contact me on https://twitter.com/sami_abid if you have any questions!

CallForge - AI-Powered Marketing Insights Extraction from Sales Calls Automate marketing intelligence gathering from AI-analyzed sales calls and store insights in Notion. 🎯 Who is This For? This workflow is designed for: ✅ Marketing teams looking to extract trends and insights from sales conversations. ✅ Product managers who need direct customer feedback from sales calls. ✅ Revenue operations (RevOps) teams optimizing AI-driven call analysis. It streamlines AI-powered marketing intelligence, identifying customer pain points, competitor mentions, and recurring trends—all automatically stored in Notion. 🔍 What Problem Does This Workflow Solve? Manually reviewing sales call transcripts for marketing insights is time-consuming and inconsistent. With CallForge, you can: ✔ Extract key marketing insights from AI-analyzed sales calls. ✔ Track recurring discussion topics across multiple conversations. ✔ Generate actionable marketing recommendations for strategy and content. ✔ Store structured insights in Notion for seamless access. This automation eliminates manual work and ensures marketing teams get data-driven insights from real customer conversations. 📌 Key Features & Workflow Steps 🎙️ AI-Driven Marketing Insights Processing This workflow processes AI-generated sales call insights and organizes them in Notion databases: Triggers when AI sales call data is received. Identifies marketing-related data (trends, customer pain points, competitor mentions). Extracts key marketing insights, categorizing product discussions and recurring topics. Logs trends across multiple calls, ensuring marketing teams spot recurring themes. Processes actionable insights, capturing marketing strategy recommendations. Stores all findings in Notion, enabling structured, searchable insights. 📊 Notion Database Integration Marketing Insights** → Logs key trends and product mentions from sales calls. Recurring Topics** → Tracks frequently discussed themes across calls. Actionable Recommendations** → Stores AI-generated recommendations for marketing teams. 🛠 How to Set Up This Workflow 1. Prepare Your AI Call Analysis Data Ensure AI-generated sales call insights are available. Compatible with Gong, Fireflies.ai, Otter.ai, and other AI transcription tools. 2. Connect Your Notion Database Set up Notion databases for: 🔹 Marketing Insights (logs trends and product mentions) 🔹 Recurring Topics (tracks frequently discussed customer concerns) 🔹 Actionable Recommendations (stores marketing strategy insights) 3. Configure n8n API Integrations Connect your Notion API key** in n8n under “Notion API Credentials.” Set up webhook triggers** to receive AI-generated sales insights. Test the workflow** using a sample AI sales call analysis. 🔧 How to Customize This Workflow 💡 Modify Notion Data Structure – Adjust fields to match marketing strategy needs. 💡 Refine AI Data Processing Rules – Customize what insights are extracted and logged. 💡 Integrate with Slack or Email – Notify teams when key marketing trends emerge. 💡 Expand CRM Integration – Sync insights with HubSpot, Salesforce, or Pipedrive. CallForge - 01 - Filter Gong Calls Synced to Salesforce by Opportunity Stage CallForge - 02 - Prep Gong Calls with Sheets & Notion for AI Summarization CallForge - 03 - Gong Transcript Processor and Salesforce Enricher CallForge - 04 - AI Workflow for Gong.io Sales Calls CallForge - 05 - Gong.io Call Analysis with Azure AI & CRM Sync CallForge - 06 - Automate Sales Insights with Gong.io, Notion & AI CallForge - 07 - AI Marketing Data Processing with Gong & Notion CallForge - 08 - AI Product Insights from Sales Calls with Notion ⚙️ Key Nodes Used in This Workflow 🔹 If Nodes – Detect if marketing insights, recurring topics, or recommendations exist in AI data. 🔹 Notion Nodes – Create and update entries in Notion databases. 🔹 Split Out & Aggregate Nodes – Process multiple insights and consolidate AI-generated data. 🔹 Wait Nodes – Ensure smooth sequencing of API calls and database updates. 🚀 Why Use This Workflow? ✔ Eliminates manual sales call review for marketing teams. ✔ Provides structured, AI-driven insights for marketing and product strategy. ✔ Tracks competitor mentions and customer pain points automatically. ✔ Improves content marketing and campaign planning with real customer insights. ✔ Scalable for teams using n8n Cloud or self-hosted deployments. This workflow empowers marketing teams by transforming sales call data into actionable intelligence, streamlining strategy, content planning, and competitor analysis. 🚀

This workflow automatically follows the steps in a custom incident response playbook and manages incidents in PagerDuty, Jira tickets, and notifies the on-call team in Mattermost. This workflow consists of three sub-workflows, each automating specific steps in the playbook. Read more about this use case and learn how to set up the workflows step-by-step in the blog tutorial How to automate every step of an incident response workflow. Prerequisites A PagerDuty account and credentials A Mattermost account and credentials A Jira account and credentials Nodes Webhook nodes trigger the workflows when an incident is created in PagerDuty, and when the incidedent is acknowledged and resolved. Mattermost nodes create an auxiliary channel for the on-call team to discuss the incident with buttons to acknowledge the incident and mark it as resolved. PagerDuty nodes update the status of the incident. Jira nodes create an issue about the incident and update its status when it's resolved.

This workflow is the third of three. You can find the other workflkows here: Incident Response Workflow - Part 1 Incident Response Workflow - Part 2 Incident Response Workflow - Part 3 We have the following nodes in the workflow: Webhook node: This trigger node listens to the event when the Resolve button is clicked. PagerDuty node: This node changes the status of the incident report from Acknowledged to Resolved in PagerDuty. Jira Software node: This node moves the incident issue to Done. Mattermost node: This node publishes a message in the auxiliary channel mentioning that the incident has been marked as resolved in PagerDuty and Jira. Mattermost node: This node publishes a message in the specified Incidents channel that the incident has been resolved by the on-call team.

This workflow automates the process of sending voice calls for verification purposes and combines it with email verification. It uses the ClickSend API for voice calls and integrates with SMTP for email verification. This workflow is a powerful tool for automating phone and email verification, ensuring a seamless and secure user verification process. Below is a breakdown of the workflow: 1. How It Works The workflow is designed to verify a user's phone number and email address through a combination of voice calls and email verification. Here's how it works: Form Submission: The workflow starts with a Form Trigger node, where users submit a form with the following fields: To: The recipient's phone number (including the international prefix, e.g., +1xxxx). Voice: The voice type (male or female). Lang: The language for the voice call (e.g., en-us, it-it, fr-fr, etc.). Email: The recipient's email address. Name: The recipient's name. Set Voice Code: The Set Voice Code node defines the verification code that will be spoken during the voice call. Format Code for Voice: The Code for Voice node formats the verification code by adding spaces between characters for better clarity during the voice call. Send Voice Call: The call includes the verification code, which is read aloud to the recipient. Verify Voice Code: The Verify Voice Code node prompts the user to enter the code they received via the voice call. The Is Voice Code Correct? node checks if the entered code matches the predefined code. If correct, the workflow proceeds to email verification. If incorrect, the user is notified of the failure. Set Email Code: The Set Email Code node defines the verification code that will be sent via email. Send Email: The Send Email node sends an email to the recipient with the verification code using SMTP. Verify Email Code: The Verify Email Code node prompts the user to enter the code they received via email. The Is Email Code Correct? node checks if the entered code matches the predefined code. If correct, the user is notified of successful verification. If incorrect, the user is notified of the failure. 2. Set Up Steps To set up and use this workflow in n8n, follow these steps: ClickSend API Key: Create an account on ClickSend and obtain your API Key. In the Send Voice node, set up HTTP Basic Authentication: Username: Use the username you registered with on ClickSend. Password: Use the API Key provided by ClickSend. SMTP Configuration: Set up SMTP credentials in n8n for the Send Email node. Ensure the SMTP server is configured to send emails from the specified email address. Form Configuration: The Form Trigger node is pre-configured with fields for: To: The recipient's phone number. Voice: Choose between male or female voice. Lang: Select the language for the voice call. Email: The recipient's email address. Name: The recipient's name. Customize the form fields if needed. Set Verification Codes: In the Set Voice Code node, define the verification code that will be spoken during the voice call. In the Set Email Code node, define the verification code that will be sent via email. Test the Workflow: Submit the form with the required details (phone number, voice, language, email, and name). The workflow will: Send a voice call with the verification code. Prompt the user to verify the code. Send an email with the verification code. Prompt the user to verify the email code. Notify the user of success or failure. Need help customizing? Contact me for consulting and support or add me on Linkedin.

This telegram bot is designed to send one random recipe a day. This specific bot has filtered out only vegan recipes, so you can choose your diet type and send only recipes for a specific diet. What credentials you need: Set up a telegram bot. Airtable for listing who has joined your bot. This is needed to send one random recipe a day. Recipe (or other) API. This one uses Spoonacular. I hope you enjoy your bot!

This is the first of 4 workflows for a Mattermost Standup Bot. This workflow will create a default configuration file. You can set the default configuration in the Set node (Use Default Config) the values are: config.slashCmdToken - The token Mattermost provides when you make a new Slash Command config.mattermostBaseUrl - The base URL for your Mattermost instance config.botUserToken - The User token for your Mattermost bot config.n8nWebhookUrl - The URL for your "Action from MM" webhook in the "Standup Bot - Worker" workflow config.botUserId - The UserID for your Mattermost Bot user The config file is saved under /home/node/.n8n/standup-bot-config.json This workflow only needs to be run once manually as part of the setup .

Instantly access NFT metadata, collections, traits, contracts, and ownership details from OpenSea! This workflow integrates GPT-4o-mini AI, OpenSea API, and n8n automation to provide structured NFT data for traders, collectors, and investors. How It Works Receives user queries via Telegram, webhooks, or another connected interface. Determines the correct API tool based on the request (e.g., user profile, NFT metadata, contract details). Retrieves data from OpenSea API (requires API key). Processes the information using an AI-powered NFT insights engine. Returns structured insights in an easy-to-read format for quick decision-making. What You Can Do with This Agent 🔹 Retrieve OpenSea User Profiles → Get user bio, links, and profile info. 🔹 Fetch NFT Collection Details → Get collection metadata, traits, fees, and contract info. 🔹 Analyze NFT Metadata → Retrieve ownership, rarity, and trait-based pricing. 🔹 Monitor NFTs Owned by a Wallet → Track all NFTs under a specific account. 🔹 Retrieve Smart Contract Data → Get blockchain contract details for an NFT collection. 🔹 Identify Valuable Traits → Fetch NFT trait insights and rarity scores. Example Queries You Can Use ✅ "Get OpenSea profile for 0xA5f49655E6814d9262fb656d92f17D7874d5Ac7E." ✅ "Retrieve details for the 'Azuki' NFT collection." ✅ "Fetch metadata for NFT #5678 from 'Bored Ape Yacht Club'." ✅ "Show all NFTs owned by 0x123... on Ethereum." ✅ "Get contract details for NFT collection 'CloneX'." Available API Tools & Endpoints 1️⃣ Get OpenSea Account Profile → /api/v2/accounts/{address_or_username} (Retrieve user bio, links, and image) 2️⃣ Get NFT Collection Details → /api/v2/collections/{collection_slug} (Get collection-wide metadata) 3️⃣ Get NFT Metadata → /api/v2/chain/{chain}/contract/{address}/nfts/{identifier} (Retrieve individual NFT details) 4️⃣ Get NFTs Owned by Account → /api/v2/chain/{chain}/account/{address}/nfts (List all NFTs owned by a wallet) 5️⃣ Get NFTs by Collection → /api/v2/collection/{collection_slug}/nfts (Retrieve all NFTs from a specific collection) 6️⃣ Get NFTs by Contract → /api/v2/chain/{chain}/contract/{address}/nfts (Retrieve all NFTs under a contract) 7️⃣ Get Payment Token Details → /api/v2/chain/{chain}/payment_token/{address} (Fetch info on payment tokens used in NFT transactions) 8️⃣ Get NFT Traits → /api/v2/traits/{collection_slug} (Retrieve collection-wide trait data) Set Up Steps Get an OpenSea API Key Sign up at OpenSea API and request an API key. Configure API Credentials in n8n Add your OpenSea API key under HTTP Header Authentication. Connect the Workflow to Telegram, Slack, or Database (Optional) Use n8n integrations to send alerts to Telegram, Slack, or save results to Google Sheets, Notion, etc. Deploy and Test Send a query (e.g., "Azuki latest sales") and receive instant NFT market insights! Unlock powerful NFT analytics with AI-powered OpenSea insights—start now!

Track NFT listings, offers, orders, and trait-based pricing in real time! This workflow integrates OpenSea API, AI-powered analytics (GPT-4o-mini), and n8n automation to provide instant insights into NFT trading activity. Ideal for NFT traders, collectors, and investors looking to monitor the market and identify profitable opportunities. How It Works A user submits a query about NFT listings, offers, or order history. The OpenSea Marketplace Agent determines the correct API tool: Retrieve active NFT listings for a collection. Fetch valid offers for individual NFTs or entire collections. Identify the cheapest NFT listings by collection or token ID. Track the highest offer made for a single NFT. Access detailed order history for a transaction. The OpenSea API (requires API key) is queried to fetch real-time data. The AI engine processes and structures the response, making it easy to interpret. The NFT marketplace insights are delivered via Telegram, Slack, or stored in a database. What You Can Do with This Agent 🔹 Find the Best NFT Listings → Retrieve the cheapest available listings in any collection. 🔹 Track Offers on NFTs → See all active offers, including highest bids. 🔹 Analyze Collection-Wide Market Data → Compare listings, offers, and sales activity. 🔹 Retrieve Order Details → Search by order hash to check buyer, seller, and transaction status. 🔹 Fetch NFT Trait-Based Offers → Identify rare traits that receive premium bids. 🔹 Monitor Multi-Chain Listings → Works across Ethereum, Polygon (Matic), Arbitrum, Optimism, and more. Example Queries You Can Use ✅ "Show me the 10 cheapest listings for Bored Ape Yacht Club." ✅ "Find the highest bid for CryptoPunk #1234." ✅ "Track all open offers for Azuki NFTs." ✅ "Retrieve details for this OpenSea order: 0x123abc... on Ethereum." ✅ "List all NFTs for sale in the 'CloneX' collection." Available API Tools & Endpoints 1️⃣ Get All Listings by Collection → /api/v2/listings/collection/{collection_slug}/all (Fetches active listings for a collection) 2️⃣ Get All Offers by Collection → /api/v2/offers/collection/{collection_slug}/all (Retrieves all offers for a collection) 3️⃣ Get Best Listing by NFT → /api/v2/listings/collection/{collection_slug}/nfts/{identifier}/best (Finds the lowest-priced NFT listing) 4️⃣ Get Best Listings by Collection → /api/v2/listings/collection/{collection_slug}/best (Fetches the cheapest listings per collection) 5️⃣ Get Best Offer by NFT → /api/v2/offers/collection/{collection_slug}/nfts/{identifier}/best (Retrieves the highest offer for an NFT) 6️⃣ Get Collection Offers → /api/v2/offers/collection/{collection_slug} (Shows collection-wide offers) 7️⃣ Get Item Offers → /api/v2/orders/{chain}/{protocol}/offers (Fetches active item-specific offers) 8️⃣ Get Listings by Chain & Protocol → /api/v2/orders/{chain}/{protocol}/listings (Retrieves active listings across blockchains) 9️⃣ Get Order Details by Hash → /api/v2/orders/chain/{chain}/protocol/{protocol_address}/{order_hash} (Checks order status using an order hash) 🔟 Get Trait-Based Offers → /api/v2/offers/collection/{collection_slug}/traits (Fetches offers for specific NFT traits) Set Up Steps Get an OpenSea API Key Sign up at OpenSea API and request an API key. Configure API Credentials in n8n Add your OpenSea API key under HTTP Header Authentication. Connect the Workflow to Telegram, Slack, or Database (Optional) Use n8n integrations to send alerts to Telegram, Slack, or save results to Google Sheets, Notion, etc. Deploy and Test Send a query (e.g., "Get the best listing for BAYC #5678") and receive instant insights! Stay ahead of the NFT market—gain powerful insights with AI-powered OpenSea analytics!

Smart Email Auto-Responder with AI Classification Automatically Categorize and Reply to Emails using LangChain + Google Gemini + Gmail + SMTP + Brevo This n8n workflow is designed to intelligently manage incoming emails and automatically send personalized responses based on the content. It classifies emails using LangChain's Text Classifier, sends HTML responses depending on the category, and updates Gmail and Brevo CRM accordingly. Key Features Triggers and Classifies Emails Listens for new Gmail messages every hour Uses AI-based classification to identify the type of inquiry For Example: Guest Post YouTube Review Udemy Course Inquiry Responds Automatically Sends professional HTML replies customized for each type Uses SMTP to deliver emails from your domain Enhances Workflow with Automation Marks processed emails as read Applies Gmail labels Adds sender to Brevo contact list Optional AI Chat Integration Uses Google Gemini (PaLM 2) to enhance classification or summarization Tools & Integrations Required Gmail account (OAuth2) LangChain (Text Classifier node) Google Gemini API account SMTP credentials (e.g., Gmail SMTP, Brevo, etc.) Brevo/Sendinblue account and API key Step-by-Step Node Guide 1. Gmail Trigger Polls Gmail every hour for new emails. Filters out internal addresses (e.g., @syncbricks.com). Avoids replying to already-responded emails (Re: subject filter). 2. LangChain Text Classifier Uses AI to categorize the content of the email based on pre-defined categories: Guest Post** Youtube** Udemy Courses** 3. Google Gemini (PaLM) Chat Model (Optional) Provides additional AI support to enhance classification accuracy. Can be used to summarize or enrich the context if needed. 4. Email Send Nodes Each response category has a separate SMTP node with a custom HTML email: Guest Post Inquiry** YouTube Video Inquiry** Udemy Course Inquiry** 5. Gmail: Mark as Read Marks the email so it isn’t processed again. 6. Gmail: Apply Label Adds a label (e.g., Handled by Bot) for organization. 7. Brevo: Create/Update Contact Saves the sender to your CRM for future communication or marketing. Email Templates Included Guest Post Template Includes pricing, website list, submission guidelines, and payment instructions. YouTube Review Template Includes package pricing, review samples, video thumbnails, and inquiry instructions. Step by Step Tutorial GET n8n Now N8N COURSE n8n Book More courses: http://lms.syncbricks.com YouTube Channel: https://youtube.com/@syncbricks How to Use Import the template into your n8n instance. Configure your Gmail OAuth2 and SMTP credentials. Set up your LangChain Text Classifier and Google Gemini API credentials. Update label ID in the Gmail node and ensure all custom fields like from.value[0].name match your use case. Run the workflow and watch it respond intelligently to new inquiries. Best Practices Always test with mock emails first. Keep the Google Gemini node optional if you want to reduce cost/API calls. Use Gmail filters to auto-label certain types of emails. Monitor your Brevo contacts to track new leads. Attribution & Support Developed by Amjid Ali This template took extensive time and effort to build. If you find it useful, please consider supporting my work. Buy My Book: Mastering n8n on Amazon Full Courses & Tutorials: http://lms.syncbricks.com Follow Me Online: LinkedIn: https://linkedin.com/in/amjidali Website: https://amjidali.com YouTube: https://youtube.com/@syncbricks

This workflow automatically forwards incoming Gmail emails to a Telegram chat only if the email subject contains specific keywords (like "Urgent" or "Server Down"). The workflow extracts key details such as the sender, subject, and message body, and sends them as a formatted message to a specified Telegram chat. This is useful for real-time notifications, security alerts, or monitoring important emails directly from Telegram — filtering out unnecessary emails. Prerequisites: Before setting up the workflow, ensure the following: The Gmail API should be enabled. Create a bot using @BotFather and obtain the API key. Retrieve the telegram Chat ID (for personal messages or group messages). Set up OAuth2 for Gmail and use the Bot Token for Telegram. Customisation Options : Modify the subject keywords in the IF Node to change the filtering criteria. Customize how the email details appear in Telegram (bold subject, italic body, etc.). Extend the workflow to include email attachments in Telegram. Steps : Step 1: Gmail Trigger Node (On Message Received) Select "Gmail Trigger" and add it to the workflow. Authenticate with your Google Account. Set Trigger Event to "Message Received". (Optional) Add filters for specific senders, labels, or subjects. Click "Execute Node" to test the connection. Click "Save". Step 2: IF Node (Conditional Filtering) Add an "IF" Node after the Gmail Trigger. Configure the condition to check if the email subject contains specific keywords (e.g., "Urgent", "Server Down", "Alert"). If the condition is true, proceed to the next step. If false, you can stop or route it elsewhere (optional). Step 3: Telegram Node (Send Message Action) Click "Add Node" and search for Telegram. Select "Send Message" as the action. Authenticate using your Telegram Bot Token. Set the Chat ID (personal or group chat). Format the message using email details received from the email trigger node and set the message in text. Steps 4. Connect & Test the Workflow Link Gmail Trigger → if node → Telegram Send Message. Save and execute the workflow manually. Send a test email to your Gmail account. Verify if the email details appear in your Telegram chat. About the Creator, WeblineIndia This workflow is created by the Agentic business process automation developers at WeblineIndia. We build automation and AI-driven tools that make life easier for your team. If you’re looking to hire dedicated developers who can customize workflows around your business, we’re just a click away.

This workflow streamlines the process of creating events in Google Calendar using event data stored in a Google Sheet. The process begins by retrieving the latest event entry from Google Sheets, ensuring only the most recent event details are processed. Once fetched, a Function node formats the event date to align with Google Calendar's required format—ensuring consistency and preventing date-related errors. After formatting, the structured event details are sent to Google Calendar, where an event is created with essential information such as the event title (summary), description, date, and location. Additionally, the workflow allows customization by setting the event's status as either "Busy" or "Available," helping attendees manage their schedules. A background color can also be assigned for better visibility and categorization. By automating this process, you eliminate the need for manual event creation, ensuring seamless synchronization between Google Sheets and Google Calendar. This improves efficiency, accuracy, and productivity, making event management effortless. Prerequisites : Before setting up this workflow, ensure the following: You have an active Google account connected to Google Sheets and Google Calendar. The Google Sheets API and Google Calendar API are enabled in the Google Cloud Console. n8n has the necessary OAuth2 authentication configured for both Google Sheets and Google Calendar. Your Google Sheet has columns for event details (event name, description, location, date, etc.). |Event Name|Event Description|Event Start Date|Location| |-|-|-|-| |Birthday|Celebration|27-Mar-1989|City| |Anniversary|Celebration|10-Jun-2015|City| Customization Options : Modify the Google Sheets trigger to track updates in specific columns. Adjust the data formatting function to support: Different date/time formats Time zone settings Custom event colors Attendee invitations Steps : Step 1: Add the Google Sheets Trigger Node Click "Add Node" and search for Google Sheets. Select "Google Sheets Trigger" and add it to the workflow. Authenticate using your Google account (select an existing account if already authenticated). Select the Spreadsheet and Sheet Name to monitor. Set the Trigger Event to "Row Added". Click "Execute Node" to test the connection. Click "Save". Step 2: Process Data with Function Node Click "Add Node" and search for Function. Add the Function Node and connect it to the Google Sheets Trigger Node. In the function editor, write a script to extract and format data. Ensure the required fields (title, location, date) are properly structured. Click "Execute Node" to verify the formatted output. Click "Save". Step 3: Add the Google Calendar Node Click "Add Node" and search for Google Calendar. Select "Create Event" operation. Authenticate with Google Calendar. Map the required fields Title Description Location Start time Optional: Set Event Status and Event Colors. Click "Execute Node" to test event creation. Click "Save". Step 4: Final Steps Connect all nodes in sequence (Google Sheets Trigger → Function Node → Google Calendar Node). Test the workflow by adding a sample row in Google Sheets. Verify that the event is created in Google Calendar with the correct title, description, date, and location. About WeblineIndia This workflow was built by the AI development team at WeblineIndia. We help businesses automate processes, reduce repetitive work, and scale faster. Need something custom? You can hire AI developers to build workflows tailored to your needs.