Workflow Templates

Check Legal Regulations: This workflow involves scraping, so ensure you comply with the legal regulations in your country before getting started. Better safe than sorry! 📌 Purpose This workflow enables automated and AI-driven topic monitoring, delivering concise article summaries directly to a Slack channel in a structured and easy-to-read format. It allows users to stay informed on specific topics of interest effortlessly, without manually checking multiple sources, ensuring a time-efficient and focused monitoring experience. To get started, copy the Google Sheets template required for this workflow from here. 🎯 Target Audience This workflow is designed for: Industry professionals** looking to track key developments in their field. Research teams** who need up-to-date insights on specific topics. Companies** aiming to keep their teams informed with relevant content. ⚙️ How It Works Trigger: A Scheduler initiates the workflow at regular intervals (default: every hour). Data Retrieval: RSS feeds are fetched using the RSS Read node. Previously monitored articles are checked in Google Sheets to avoid duplicates. Content Processing: The article relevance is assessed using OpenAI (GPT-4o-mini). Relevant articles are scraped using Jina AI to extract content. Summaries are generated and formatted for Slack. Output: Summaries are posted to the specified Slack channel. Article metadata is stored in Google Sheets for tracking. 🛠️ Key APIs and Nodes Used Scheduler Node:** Triggers the workflow periodically. RSS Read:** Fetches the latest articles from defined RSS feeds. Google Sheets:** Stores monitored articles and manages feed URLs. OpenAI API (GPT-4o-mini):** Classifies article relevance and generates summaries. Jina AI API:** Extracts the full content of relevant articles. Slack API:** Posts formatted messages to Slack channels. This workflow provides an efficient and intelligent way to stay informed about your topics of interest, directly within Slack.

This workflow allows you to add candidates’ profile assessments to Notion before an interview. Prerequisites Add an input field on your Calendly Invite page where the candidate can enter their LinkedIn URL. Create credentials for your Calendly account. Follow the steps mentioned in the documentation to learn how to do that. Create credentials for Humantic AI following the steps mentioned here. Create a page on Notion similar to this page. Create credentials for the Notion node by following the steps in the documentation. Calendly Trigger node: This node will trigger the workflow when an interview gets scheduled. Make sure to add a field to collect the candidates' LinkedIn URL on your invite page. Humantic AI: This node uses the LinkedIn URL received by the previous node to create a candidate profile in Humantic AI. Humantic AI1: This node will analyze the candidates' profile. Notion node: This node will create a new page in Notion using the information from the previous node.

This workflow gets triggered every Friday at 6 PM with the help of a Cron node. It pulls in data about a random cocktail via the HTTP Request Node and sends the data to a Bannerbear node to create an image based on a template. The image is then finally shared on a specified Rocket.Chat channel.

This workflow automates the process of sending text-to-speech (TTS) voice calls using API. It allows users to submit a form with the message content, recipient's phone number, voice type, and language, and then sends a voice call with the provided text. This workflow is a simple yet powerful way to automate text-to-speech voice calls using API. It’s ideal for notifications, reminders, or any scenario where voice communication is needed. Below is a breakdown of the workflow: 1. How It Works The workflow is designed to send voice calls with text-to-speech functionality. Here's how it works: Form Submission: The workflow starts with a Form Trigger node, where users submit a form with the following fields: Body: The text message to be converted to speech (max 600 characters). To: The recipient's phone number (including the international prefix, e.g., +39xxxxxxxxxx). Voice: The voice type (male or female). Lang: The language for the voice call (e.g., en-us, it-it, fr-fr, etc.). Once the form is submitted, the workflow is triggered. Send Voice Call: The Send Voice node sends a POST request to the ClickSend API (https://rest.clicksend.com/v3/voice/send). The request includes: The text message (Body) to be converted to speech. The recipient's phone number (To). The voice type (Voice). The language (Lang). Machine detection is enabled to detect if the call is answered by a machine. The API processes the request and initiates a voice call to the specified number, where the text is read aloud by the selected voice. Outcome: The recipient receives a voice call, and the submitted text is read aloud in the chosen voice and language. 2. Set Up Steps To set up and use this workflow in n8n, follow these steps: Register on ClickSend: Go to ClickSend and create an account. Obtain your API Key and take advantage of the 2 € free credits provided. Configure ClickSend API in n8n: 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. Set Up the Form Trigger: The Form Trigger node is pre-configured with fields for: Body: The text message to be converted to speech. To: The recipient's phone number. Voice: Choose between male or female voice. Lang: Select the language for the voice call. Customize the form fields if needed (e.g., add more languages or voice options). Test the Workflow: Submit the form with the required details (text, phone number, voice, and language). The workflow will send a voice call to the specified number, and the recipient will hear the text read aloud. Optional Customization: Modify the workflow to include additional features, such as: Adding more languages or voice options. Sending multiple voice calls in bulk. Integrating with other APIs or services for advanced use cases.

Boost your productivity with this AI-powered email and calendar assistant: This AI-powered template has 2 workflows. It manages your Gmail inbox and Google Calendar, classifies emails with custom labels, and suggests replies and meeting times — all fully automated with OpenAI and n8n. Automatically analyze your Gmail inbox Suggest replies, priorities, and meeting times Checks your Google Calendar for conflicts and free slots Maintain conversation context using Thread History Vector Store The agent proactively acts using a Tools Agent architecture, with integrated memory and real-time tool invocation. It's perfect for busy professionals who want a personal assistant for communication and scheduling. Included features: ✅ Do actions on incoming mails 8like Labeling etc) ✅ Summarize and Assist fot the latest emails ✅ Draft replies and schedule meetings contextually ✅ Handle time zone conversion and MessageID referencing ✅ Context retention of last conversation history - using VectorStore 📦 Requirements: Gmail + Google Calendar credentials via n8n credentials OpenAI API key n8n VectorStore nodes (or external integration like Pinecone, Qdrant, or Chroma)

Supabase AI Agent with RAG & Multi-Tenant CRUD Version: 1.0.0 n8n Version: 1.88.0+ Author: Koresolucoes License: MIT Description A stateful AI agent workflow powered by Supabase and Retrieval-Augmented Generation (RAG). Enables persistent memory, dynamic CRUD operations, and multi-tenant data isolation for AI-driven applications like customer support, task orchestration, and knowledge management. Key Features: 🧠 RAG Integration: Leverages OpenAI embeddings and Supabase vector search for context-aware responses. 🗃️ Full CRUD: Manage agent_messages, agent_tasks, agent_status, and agent_knowledge in real time. 📤 Multi-Tenant Ready: Supports per-user/organization data isolation via dynamic table names and webhooks. 🔒 Secure: Role-based access control via Supabase Row Level Security (RLS). Use Cases Customer Support Chatbots: Persist conversation history and resolve queries using institutional knowledge. Automated Task Management: Track and update task statuses dynamically. Knowledge Repositories: Store and retrieve domain-specific information for AI agents. Instructions 1. Import Template Go to n8n > Templates > Import from File and upload this workflow. 2. Configure Credentials Add your Supabase and OpenAI API keys under Settings > Credentials. 3. Set Up Multi-Tenancy (Optional) Dynamic Webhook Path**: Replace the default webhook path with /mcp/tool/supabase/:userId to enable per-user routing. Table Names**: Use a Set Node to dynamically generate table names (e.g., agent_messages_{{userId}}). 4. Activate & Test Enable the workflow and send test requests to the webhook URL. Tags AI Agent RAG Supabase CRUD Multi-Tenant OpenAI Automation Screenshots License This template is licensed under the MIT License.

This workflow provides a simple approach to counting the items returned by a node. It uses a Set node with the Execute Once option: The expression uses $input.all() (documented here) to fetch all incoming items at once, and .length (documented for example here) to count them.

Create a Branded AI Website Chatbot Engage website visitors with an intelligent chat widget powered by OpenAI. This template includes: 💬 Natural conversation handling 📅 Microsoft Outlook calendar integration 📝 Lead capture and information gathering 🔄 Human handoff capabilities Simply add a JavaScript snippet to your website and configure the workflow to match your needs. Follow our detailed setup guide to get started in minutes. > Note: Widget includes a "Powered By" affiliate link

Who is This For? This is for normal people or people just starting off and wanting to have a AI chatbot that can process data to use when talking to the user. How to Use You will need to have your own OpenRouter (Free) and OpenAI APIs as well as Google Drive, Pinecone, and Airtable. What Do You Want? If you want to have your AI Agent remember the user's preferences even after the session is over then you can keep the Airtable node in, if not you can delete it.

This workflow, developed by our AI developers at WeblineIndia, is designed to automate the process of capturing form submissions and storing them in Airtable. By leveraging automation, it eliminates manual data entry, ensuring a smooth and efficient way to handle form data. The purpose of creating this workflow is to streamline data management, helping businesses save time, reduce errors, and maintain an organized, structured database for easy access and future use. Steps: Trigger on Form Submission (Form Node)** What It Does: Activates the workflow whenever a form is submitted. How to Set It Up: Use the Form Submission Trigger node to detect new form submissions. This ensures the workflow starts automatically when a user fills out the form. Store Data in Airtable (Airtable Node)** What It Does: Transfers the form data into an Airtable base. How to Set It Up: Use the Airtable Node to map form fields to corresponding columns in your Airtable table, storing the data accurately. Finalize and Activate** What It Does: Completes the setup to automate data storage upon form submission. How to Set It Up: Save and activate the workflow. Once active, it will automatically record all new form submissions in Airtable.

A sentiment intelligence sub-agent for the Binance Spot Market Quant AI Agent. It aggregates crypto news from major sources, filters by token keyword (e.g., BTC, ETH), and produces a Telegram-ready summary including market sentiment and top headlines—powered by GPT-4o. 🎥 Live Demo: 🛠️ Workflow Function This tool performs the following steps: | 🔧 Step | 📌 Description | | ------------------------ | ----------------------------------------------------------------------------- | | Webhook Input | Accepts { "message": "symbol" } via HTTP POST | | Crypto Keyword Extractor | GPT model extracts the valid crypto symbol (e.g., "SOL", "DOGE", "ETH") | | RSS News Aggregators | Pulls latest headlines from 9+ crypto sources (CoinDesk, Cointelegraph, etc.) | | Merge & Filter Articles | Keeps only articles containing the specified token | | Prompt Builder | Creates prompt for GPT with filtered headlines | | GPT-4o Summarizer | Summarizes news into 3-part response: Summary, Sentiment, Headline Links | | Telegram Formatter | Converts GPT output into a Telegram-friendly message | | Response Handler | Returns formatted message to the caller via webhook | 📥 Webhook Trigger Format { "message": "ETH" } This triggers a full execution of the workflow and returns output like: 📣 ETH Sentiment: Neutral • BlackRock’s tokenized fund expands to Ethereum mainnet (CoinDesk) • Ethereum fees remain high, analysts call for L2 migration (NewsBTC) • Vitalik warns about centralized risks in staking (Cointelegraph) 📚 Installation Guide 1. Import & Enable Load the .json into your n8n Editor Enable webhook trigger in the top-right corner Ensure it's reachable via POST /webhook/custom-path 2. Required Credentials OpenAI API Key** (GPT-4o capable) No API keys required for RSS feeds 3. Connect to Quant Agent Add an HTTP Request node in your main AI agent Point to this workflow's webhook with body { "message": "symbol" } Capture the response to include in your Telegram output 🔍 Real Use Cases | Scenario | Result | | ---------------------------------- | ---------------------------------------------------------------- | | BTC Sentiment before a key event | Returns 8–12 filtered articles with bullish/neutral/bearish tone | | Daily pulse for altcoins like DOGE | Shows relevant headlines, helpful for intraday trading setups | | Telegram chatbot integration | Enables user to query sentiment via /sentiment ETH | | Macro context for Quant AI outputs | Adds emotional/news context to technical-based trade decisions | 🧾 Licensing & Attribution © 2025 Treasurium Capital Limited Company Architecture, prompts, and trade report structure are IP-protected. No unauthorized rebranding or resale permitted. 🔗 For support: LinkedIn – Don Jayamaha

This workflow stores responses form responses of Typeform in Airtable. The workflow also sends the response to a channel on Slack. You will have to configure the Set node if your form uses different fields.