by Hrayr Movsisyan
This workflow automatically fetches job postings from the JSearch API once per day, filters out duplicates, and saves only new jobs to a Google Sheet. It also sends a Telegram summary with the number of newly added jobs. What this workflow does • Builds a custom job search query • Fetches job listings from JSearch • Loads existing job IDs from Google Sheets • Removes already-saved jobs • Writes only new jobs into the sheet • Sends a Telegram summary with job count Why it's useful • Hands-free daily job monitoring • No duplicates — clean data tracking • Uses rate-limit-safe writing • Easy to customize search keywords • Works entirely with no-code steps Requirements • RapidAPI (JSearch) account • Google Sheets account • Telegram Bot token Ideal For • Job researchers • Recruitment automations • Personal job-search tracking • Data collection workflows
by Rahul Joshi
📊 Description Automate proactive brand reputation monitoring across public platforms using AI-driven risk analysis 🤖. This workflow continuously scans Reddit, Glassdoor, and review sites via SerpAPI to detect negative sentiment, public complaints, and early crisis signals 🔍. Each mention is analyzed with AI to assess risk level and urgency, ensuring no critical issue goes unnoticed. High-risk threats automatically trigger real-time Google Chat alerts and create priority Asana tasks 🚨, enabling fast, coordinated response without manual monitoring. 🔍 What This Template Does Runs on an hourly schedule ⏰ to continuously track brand mentions online. Searches public platforms like Reddit and review sites using SerpAPI 🔍. Parses and structures insights from AI-powered search results 📄. Analyzes sentiment and crisis risk using Azure OpenAI 🤖. Filters high-risk reputation threats automatically ⚠️. Sends instant Google Chat alerts for urgent issues 💬. Creates priority Asana tasks to ensure fast team action ✅. ✅ Key Benefits ✅ Detect brand crises before they escalate publicly ✅ Eliminate manual reputation monitoring across platforms ✅ Get real-time alerts only for high-risk issues ✅ Centralize crisis response with automatic task creation ✅ Improve brand trust and response time ✅ AI-powered, scalable, and always-on monitoring ⚙️ Features Hourly automated monitoring trigger SerpAPI Google AI Mode search integration AI-based sentiment and crisis risk classification Structured JSON output for reliability Google Chat alerts for instant visibility Asana task creation for crisis management Fail-safe handling for malformed AI responses 🔑 Requirements SerpAPI account (Google AI Mode search) Azure OpenAI credentials Google Chat OAuth2 credentials Asana OAuth2 credentials Brand name or keywords for monitoring 🎯 Target Audience SaaS founders and startup teams Brand, PR, and reputation managers Digital agencies managing multiple clients Customer support and crisis response teams
by Anne Uy Gothong
This free n8n automation helps anyone—from busy parents to entrepreneurs—get a daily SMS summary of their calendar events. It’s a personal assistant that gives you a heads up of what your day will look like. Great for: starting your day cognizant of the day's events, or for the neurodivergent. Example use case: Parent receives a text summarizing the Family Calendar events at 5AM. Its a reminder of a child's doctor appointment at 1PM and soccer practice at 430PM. The AI then ends the message on an uplifting note. Good to Know Requires user to buy a Twilio phone number to send SMS from. Each message, at the time of writing, is $0.083 CAD. Requires basic knowledge of Google Cloud Console for the activation of Google Calendar API How it Works Every morning at 7AM, your workflow checks Google Calendar for the day’s events. It formats your schedule into a friendly, easy-to-read summary using your favorite AI model (any LLM works—Anthropic, OpenAI, Gemini, etc). That summary is texted directly to your phone via Twilio as a personal daily reminder. How to Use Copy this n8n workflow into your own instance. Hook up your Google Calendar and Twilio accounts. You can choose the specific calendar in the Calendar node. Choose or swap in any AI model you prefer to personalize your summaries. I find Claude sounds the most natural. Enjoy your daily, cheerful calendar digest by SMS at 7AM! Requirements A Google Cloud account (to activate the Calendar API and get credentials—see Google documentation). Twilio account (for sending SMS—get started with Twilio’s easy setup). Any LLM API account (optional, but recommended for polite/friendly summaries). Customize this flow Change SMS times to fit your morning routine. Adjust message formatting for your style or brand. Swap LLM services, tweak prompts, or combine multiple calendars—whatever works for you. Reach out anytime at ralleyreminders.com if you have questions or want to share ideas!
by Elimeleth
📊 Token Usage Metrics Workflow Descripción: Este flujo de trabajo en n8n extrae y resume las métricas de uso de tokens (prompt, completion y total) y los modelos utilizados en una ejecución específica. Requiere el execution_id y un array con los nombres de los nodos de AI (por ejemplo: openai, gemini). Requisitos: execution_id: ID de la ejecución de n8n de la cual se extraerán los datos. model_names: Array con los nombres de los nodos AI a buscar (ejemplo: openai, gemini). Funcionamiento: Obtiene la ejecución con el ID proporcionado. Busca en los nodos indicados la información de token usage dentro de la ejecución. Suma los tokens usados y genera un listado de modelos utilizados. Devuelve métricas totales y un desglose detallado por modelo. Configuración recomendada: Este workflow debe configurarse para ejecutarse siempre al final del flujo de trabajo. Desactivar la opción “Esperar a que termine” para evitar bloqueos y asegurar que se obtenga la ejecución completa. 📊 Token Usage Metrics Workflow Description: This n8n workflow extracts and summarizes token usage metrics (prompt, completion, and total tokens) along with the models used in a specific execution. It requires the execution_id and an array of AI node names (e.g., openai, gemini). Requirements: execution_id: The n8n execution ID from which data will be extracted. model_names: An array of AI node names to search for (e.g., openai, gemini). How It Works: Fetches the execution using the provided ID. Searches the specified nodes for token usage information within the execution. Aggregates token counts and compiles a list of models used. Returns total metrics and a detailed breakdown per model. Recommended Configuration: Configure this workflow to run always at the end of your workflow. Disable the “Wait until finished” option to avoid blocking and ensure the complete execution data is available.
by Rahul Joshi
📊 Description This automation calculates commonly used technical indicators for selected stocks and presents the results in a simple, structured dashboard. It removes the need for manual chart analysis by automatically fetching price data, calculating indicators, and generating clear Buy, Sell, or Neutral signals. The workflow is designed to run daily and provides a consistent technical snapshot for each tracked stock. It is suitable for traders and analysts who want a repeatable and transparent way to monitor technical conditions without relying on manual tools. ⚙️ What This Template Does Runs automatically on a daily schedule Processes a predefined list of stock symbols Fetches recent daily price data from a market data API Calculates RSI, Moving Averages, and MACD Applies rule-based logic to generate Buy, Sell, or Neutral signals Stores indicator values and signals in Google Sheets ✅ Key Benefits Eliminates manual technical analysis Uses standard, widely accepted indicators Produces clear and easy-to-interpret signals Keeps all results in a single dashboard Easy to customize and extend 🧩 Features Daily scheduled execution Historical price data integration RSI (14-period) calculation Moving Averages (SMA 20 and SMA 50) MACD (12, 26, 9) calculation Rule-based Buy / Sell / Neutral classification Google Sheets dashboard output Built-in data validation checks 🔐 Requirements To use this workflow, you will need: A market data API key (Alpha Vantage or similar) A Google Sheets account for storing results Google Sheets credentials configured in n8n An active n8n instance (cloud or self-hosted) 🎯 Target Audience Stock traders and investors Technical analysts Finance and research teams Automation builders working with market data 🛠 Customization Options Update the stock list to track different symbols Adjust indicator periods or thresholds Modify Buy / Sell signal rules Change the schedule frequency Extend the dashboard with additional indicators
by Calistus Christian
What this workflow does Provides the tools layer for the Parent agent to manage Google Calendar: Get (list events), Create, and Delete. Accepts text + sessionid from the Parent and uses an LLM with short-term memory to choose and run the correct tool. Pipeline: Execute Workflow Trigger → Sub-Agent → (Get / Create / Delete) → Google Calendar Category: Productivity / Calendar / Agentic\ Time to set up: ~10 minutes\ Difficulty: Intermediate\ Cost: Mostly free (n8n CE; OpenAI + Google Calendar usage as configured) * What you'll need OpenAI credentials. Google Calendar OAuth2 credentials. A calendar ID (use a placeholder like your.calendar@example.com in the node and select your actual calendar at runtime). * Set up steps Import this Sub-Agent workflow. Open the Google Calendar tool nodes (Get, Create, Delete) and select your OAuth2 credential and calendar. Ensure the Execute Workflow Trigger exposes two inputs: text and sessionid. Connect the Parent's toolWorkflow node to this workflow. * Testing (direct call example) From the Parent, send: "Schedule 'Team Sync' tomorrow 10:00--11:00" → Sub-Agent should call Create. "List events next week" → Get with timeMin/timeMax. "Delete event 'Team Sync'" → Delete with eventId once matched.
by Yar Malik (Asfandyar)
Who’s it for This workflow is designed for researchers, content creators, and AI agents who need to quickly scrape structured web data and capture full-page screenshots for further use. It’s especially useful for automating competitive research, news monitoring, and content curation. How it works The workflow uses the Firecrawl API integrated with n8n to perform web searches and return results in structured formats (Markdown and screenshots). It includes: A search agent that transforms natural language queries into Firecrawl-compatible search strings. HTTP requests to retrieve results from specific sites (e.g., YouTube, news outlets) or across the web. Automatic capture of full-page screenshots alongside structured text. Integration with the OpenAI Chat Model for enhanced query handling. How to set up Import this workflow into your n8n instance. Add and configure your Firecrawl API credentials. Add your OpenAI credentials for natural language query parsing. Trigger the workflow via the included chat input or modify it to run on schedule. Requirements A Firecrawl account with an active API key. n8n self-hosted or cloud instance. OpenAI account if you want to enhance search queries. How to customize the workflow Update the search queries to focus on your preferred sites or keywords. Adjust the number of results with the limit parameter. Extend the workflow to store screenshots in Google Drive, Notion, or your database. Replace the chat trigger with any other event trigger (webhook, schedule, etc.).
by Msaid Mohamed el hadi
🔍 AI-Powered Website Prompt Executor (Apify + OpenRouter) This workflow combines the power of Apify and OpenRouter to scrape website content and execute any custom prompt using AI. You define what you want — whether it’s extracting contact details, summarizing content, collecting job offers, or anything else — and the system intelligently processes the site to give you results. 🚀 Overview This workflow allows you to: Input a URL and define a prompt. Scrape the specified number of pages from the website. Process each page’s metadata and Markdown content. Use AI to interpret and respond to the prompt on each page. Aggregate and return structured output. 🧠 How It Works Input Example { "enqueue": true, "maxPages": 5, "url": "https://apify.com", "method": "GET", "prompt": "collect all contact informations available on this website" } Workflow Steps | Step | Action | | ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | 1 | Triggered by another workflow with JSON input. | | 2 | Calls the Apify actor firescraper-ai-website-content-markdown-scraper to scrape content. | | 3 | Loops through the scraped pages. | | 4 | AI analyzes each page based on the input prompt. | | 5 | Aggregates AI outputs across all pages. | | 6 | Final AI processing step to return a clean structured result. | 🛠 Technologies Used Apify** – Scrapes structured content and Markdown from websites. OpenRouter** – Provides access to advanced AI models like Gemini. LangChain** – Handles AI agent orchestration and prompt interpretation. 🔧 Customization Customize the workflow via the following input fields: url: Starting point for scraping maxPages: Limit the number of pages to crawl prompt: Define any instruction (e.g., “summarize this website,” “extract product data,” “list all emails,” etc.) This allows dynamic, flexible use across various use cases. 📦 Output The workflow returns a JSON result that includes: Processed prompt responses from each page Aggregated AI insights Structured and machine-readable format 🧪 Example Use Cases 🔍 Extracting contact information from websites 📄 Summarizing articles or company profiles 🛍️ Collecting product information 📋 Extracting job listings or news 📬 Generating outreach lists from public data 🤖 Used as a tool within other AI agents for real-time web analysis 🧩 Integrated as an external tool in MCP (Multi-Component Prompt) servers to enhance AI capabilities 🔐 API Credentials Required You will need: Apify API token** – For running the scraper actor OpenRouter API key** – For AI-powered prompt processing Set these credentials in your environment or n8n credential manager before running.
by Davide
The “Multiplatform Social Media Content Creator with GoToHuman Approval” workflow automates the creation, review, and publishing preparation of social media content across multiple platforms. It connects a Google Sheets editorial plan to Claude Sonnet 4.5 and GoToHuman, allowing for seamless collaboration between AI-generated content and human approval. This workflow automates the creation and human-approval of social media content. It pulls post ideas from a Google Sheet, uses an AI model to generate platform-specific content, sends it for human review, and then updates the sheet based on the approval or rejection. Key Advantages ✅ AI-Assisted Content Creation: Automatically transforms content ideas into ready-to-publish social media posts optimized for each platform. ✅ Human-in-the-Loop Approval: The GoToHuman integration ensures every AI-generated post is reviewed and validated by a person before going live. ✅ Centralized Editorial Management: All content ideas, drafts, and approvals are synchronized in Google Sheets, creating a transparent and organized workflow. ✅ Platform-Optimized Output: Adapts tone, format, hashtags, and structure depending on whether the post is for Instagram, Facebook, LinkedIn, or X. ✅ Automated Revision Loop: If rejected, the workflow automatically refines and regenerates improved content—saving manual rework time. ✅ Scalable and Collaborative: Ideal for marketing teams managing large volumes of social content that require quality control and brand consistency. ✅ Time-Saving: Reduces content creation cycles by combining AI writing speed with controlled human oversight. How it Works Trigger & Data Fetch: The process starts either manually or on a schedule. It first connects to a specified Google Sheet and retrieves all rows of data from the "Editorial Plan". AI Content Generation: The workflow loops over each row from the sheet. For each item, it takes the "IDEA" and "PLATFORM" fields and sends them to an Anthropic node ("Social Media Content Creator"). This node uses a detailed, pre-defined system prompt to transform the raw idea into a polished, platform-optimized social media post. Human Approval Loop: The generated post text is then sent to the GoToHuman node. This creates a task in the GoToHuman system, pausing the workflow and waiting for a human reviewer to make a decision. The platform information is also passed along as metadata for context. Decision Point: Once a human reviewer responds, the workflow resumes. A Switch node routes the execution based on the response: If "approved": The workflow proceeds to update the original Google Sheet row. It marks the "APPROVED" column with an "x" and writes the final, approved post content into the "POST" column. If "rejected": The workflow routes the rejected item back to the "Social Media Content Creator" AI node. Before doing so, a "Set" node prepares the data, effectively telling the AI to generate a new version of the post based on the same original idea and platform. This creates an iterative improvement loop until the content is approved. Set up Steps Prepare the Google Sheet: Create a Google Sheet with columns at least for: DATE, IDEA, PLATFORM, POST, and APPROVED. Share this sheet with the Google service account or user that your n8n Google Sheets credential is configured with. Configure Credentials: Google Sheets: Set up a OAuth2 credential in n8n for Google Sheets and authenticate it with an account that has access to your sheet. Anthropic: Create an API key credential in n8n and enter your valid Claude API key. GoToHuman: Configure the GoToHuman node with the necessary API credentials and specify the correct reviewTemplateID for your approval process. Adjust Node Parameters: In the "Get row(s) in sheet" and "Update row in sheet" nodes, ensure the documentId matches your Google Sheet's ID. The sheet name should also be correct (e.g., gid=0 for the first sheet). Review the system prompt in the "Social Media Content Creator" node to ensure it matches your brand's tone, style, and specific platform requirements. In the GoToHuman node, verify that the fields mapping correctly passes the AI-generated text and that the metaKeyValues correctly passes the platform information. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. You can now trigger it manually using the "Execute workflow" button or let it run automatically based on the defined schedule. Need help customizing? Contact me for consulting and support or add me on Linkedin.
by Rahul Joshi
Description: Ensure your customer SLAs never slip with this n8n automation template. The workflow runs on a schedule, fetching open tickets from Zendesk, calculating SLA time remaining, and sending proactive alerts to Slack when tickets approach breach thresholds (75% and 90%). It also updates ticket priority in Zendesk and logs compliance metrics to Google Sheets for reporting. Perfect for support operations, CX teams, and SaaS companies looking to maintain SLA compliance and reduce response delays automatically. ✅ What This Template Does (Step-by-Step) ⏰ Run Every Hour: Automatically triggers every hour to check for SLA-sensitive tickets. 📥 Fetch All Open Zendesk Tickets: Pulls all tickets via the Zendesk API, returning essential fields: ID, status, created_at, sla_due, and priority. 🔍 Filter Only “Open” Tickets: Excludes closed, on-hold, or pending tickets — monitoring focuses only on actionable cases. ⏱️ Calculate SLA Time Remaining: Computes total SLA duration, remaining minutes, and % of SLA consumed for each ticket. 🟡 Warn at 75% Threshold: When 75% of the SLA window has passed, automatically sends a Slack warning to the #general-information channel. 🔴 Escalate at 90% Threshold: For tickets nearing breach (≥90%), the workflow updates Zendesk ticket priority to “High,” adds escalation notes, and notifies the support team for immediate action. 📊 Log SLA Compliance in Google Sheets: Each ticket’s SLA metrics (ID, % elapsed, time remaining, timestamp) are appended to a Google Sheet for tracking and reporting. ✅ No-Ticket Confirmation: If no open tickets exist, the workflow posts a “✅ No open tickets” message to Slack — keeping teams informed of a clear queue. 🧠 Key Features ⏱️ Automated SLA tracking and escalation 📊 Real-time logging to Google Sheets ⚡ Hourly auto-trigger — no manual checks needed 📢 Slack alerts at warning and critical thresholds 🔄 Dynamic Zendesk ticket updates via API 💼 Use Cases 💬 Proactively manage customer support SLAs 🚨 Automatically escalate critical tickets before breach 📈 Maintain transparent SLA compliance reporting 📢 Keep your support team updated in real time 📦 Required Integrations Zendesk API – for ticket retrieval and updates Slack API – for alert notifications Google Sheets – for compliance and reporting logs 🎯 Why Use This Template? ✅ Prevent SLA breaches before they happen ✅ Automate escalation and communication ✅ Provide real-time visibility to support leads ✅ Build a historical SLA performance dataset
by Yuki Hirota
Automated Meeting Recording Transcription & Minutes Distribution Workflow Managing meeting recordings manually—downloading audio, transcribing it, summarizing key points, saving documents, and notifying the team—quickly becomes repetitive and inefficient. This workflow eliminates all of those manual steps by automatically detecting new audio files uploaded to a designated Google Drive folder, converting them into high-quality transcripts using OpenAI, summarizing them into structured meeting minutes, transforming the content into a text file, uploading it back to Google Drive, and finally notifying a Chatwork room with the completed summary. What used to take hours can now be completed automatically within minutes, ensuring consistency, accuracy, and faster information sharing. Who’s it for This workflow is ideal for: Teams that need high-quality, client-ready meeting minutes generated automatically Project managers who require accurate summaries, decision tracking, and action items without manual effort Cross-functional teams handling multiple meetings and requiring structured, searchable documentation Organizations using Google Meet, Zoom, or Teams where recordings must be turned into polished minutes Anyone who wants a consistent, AI-assisted system that analyzes discussions, extracts insights, and formats them professionally By leveraging an advanced Meeting Minutes Generation System—capable of key-point extraction, noise reduction, speaker/topic organization, and review support—this workflow ensures that every meeting is transformed into a clean, structured, and highly usable document. How it works 1. Audio file upload triggers the workflow When a new recording is uploaded to the designated Google Drive folder, the Google Drive Trigger immediately activates and begins processing. 2. The audio file is downloaded The file is retrieved from Google Drive and prepared in binary format for accurate transcription. 3. AI-powered transcription The audio is sent to OpenAI’s transcription engine, producing a complete and highly accurate transcript of the meeting. 4. Generate structured, client-ready meeting minutes The transcript is processed by a specialized Meeting Minutes Generation System powered by a multi-step prompt. Instead of using a fixed template, the system intelligently analyzes the transcription and automatically generates a professionally structured document using the following capabilities: Extraction of key points while removing irrelevant conversation Organization of content by speaker, topic, and logical flow Automatic construction of headings and document structure Draft generation based on client-facing writing standards Review-support logic that allows refinement and improved readability Task-based orchestration (ingestion → key-point extraction → draft generation → review → final approval) Because the system dynamically determines the optimal structure, the resulting minutes adapt to the content of each meeting rather than following a rigid set of categories. If certain information cannot be derived from the transcript, the system will appropriately leave it out rather than forcing placeholder sections. 5. Convert the minutes into a file The structured minutes are converted into a .txt or .docx document, ready for submission or archival. 6. Upload the finalized document The completed meeting minutes are uploaded to a specific Google Drive folder and saved using a timestamped filename. 7. Notify Chatwork A formatted notification—including the summarized content—is automatically posted to a Chatwork room, ensuring immediate team visibility. How to set up Import the workflow into your n8n environment. Authenticate Google Drive and select the folder to monitor for new recordings. Connect your OpenAI API keys for both transcription and structured minutes generation. Specify the Google Drive folder where the finished documents should be stored. Add your Chatwork API token and room ID for automated notifications. Upload a sample audio file to confirm the full end-to-end pipeline works correctly. Requirements n8n instance (cloud or self-hosted) Google Drive account with appropriate folder permissions OpenAI API credentials Chatwork API token Supported audio formats like mp3, wav, m4a, etc. How to customize the workflow Modify the minutes-generation prompt to reflect your organization’s preferred format Add Slack, Teams, or Discord notifications in addition to Chatwork Route different types of meetings to different folders or templates Save transcript and structured minutes separately for compliance or analysis Log metadata or decisions into Google Sheets or project management tools Store minutes in a vector database to enable semantic search across past meetings Attach the final document directly as a file in Chatwork Extend the system to support revision cycles, reviewer comments, or approval workflows
by Rahul Joshi
Description: Guarantee that only fully compliant stories and tasks make it into your release with this n8n automation template. The workflow monitors Jira for issue updates and link changes, validates whether each story meets the Definition of Done (DoD), and automatically flags non-compliant items. It also creates a tracking record in Monday.com for unresolved blockers and sends Slack alerts summarizing readiness status for every version. Perfect for release managers, QA leads, and engineering teams who need an automated guardrail for production readiness. ✅ What This Template Does (Step-by-Step) 🎯 Jira Webhook Trigger: Activates automatically when an issue is updated or linked in Jira — ideal for continuous readiness validation. 📋 Fetch Full Issue Details: Retrieves the complete issue payload, including custom fields, status, and Definition of Done flags. 🔄 Batch Processing (1-by-1): Ensures each issue is validated individually, allowing precise error handling and clean audit trails. ✅ Check Definition of Done (DoD): Evaluates whether the customfield_DoD field is marked as true — a key signal of readiness for release. ⚠️ Flag Non-Compliant Issues: If DoD isn’t met, marks the issue as “Non-Compliant” with the reason “Definition of Done not met.” 📊 Create Tracking Record in Monday.com: Logs non-compliant issues to a dedicated Release Issues board for visibility and coordination with cross-functional teams. 📢 Send Slack Notifications: Posts to the #release-updates channel summarizing compliant vs non-compliant items per version, helping the team take timely action. 🧠 Key Features 🚦 Real-time Jira readiness validation ✅ Automated DoD enforcement before release 📊 Monday.com tracker for all non-compliant issues 📢 Slack summary notifications for release teams ⚙️ Batch-wise validation for scalable QA 💼 Use Cases 🚀 Enforce Definition of Done across linked Jira stories 📦 Automate pre-release checks for every version increment 🧩 Provide visibility into blockers via Monday.com dashboard 📢 Keep engineering and QA teams aligned on release status 📦 Required Integrations Jira Software Cloud API – to monitor issue updates and retrieve details Monday.com API – to log and track non-compliant items Slack API – for real-time release alerts 🎯 Why Use This Template? ✅ Eliminates manual pre-release validation ✅ Reduces release delays due to missed criteria ✅ Keeps all stakeholders aligned on readiness status ✅ Creates a transparent audit trail of compliance