Workflow Templates

🔍 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.

++How it works++ This workflow takes post ideas and prompts from Airtable, creates viral social media content with Claude, and schedules daily posts in PostPulse. ++Set up steps++ Airtable Trigger:* Triggers our workflow via the *Created** field in our base. HTTP Node:** 3rd party API call to generate an AI image. Prompt is sourced from Airtable base. Anthropic's Claude:* Creates a viral social media post using the *Post Idea** field in Airtable base. Download File:** Downloads the generated image from Step 2. Upload Media to PostPulse:** Upload the downloaded image to PostPulse in order to retrieve our path ID. Schedule a Light Post:** Schedule the posting date of our generated Claude post and AI image. Update Airtable Base:* Update *Posted?** field in Airtable to Yes.

📖 Overview This workflow automates your morning wake-up call by calculating the perfect time to leave based on real-time traffic. Instead of a static alarm, n8n continuously monitors road conditions via the Google Maps Distance Matrix API. When the "strike time" is reached, accounting for both live traffic and your morning preparation; the workflow triggers a physical alarm on your iPhone via a Twilio SMS and iOS Shortcuts. 🛠️ System components 1. The Brain (n8n) Check interval: Monitors traffic every minute during your "ready window." Logic: Uses a mathematical expression to determine if you need to wake up now to make your arrival goal. **Formula: T_{wake} = T_{arrival} - (T_{traffic} + T_{prep}) 2. The Log (Google Sheets): Maintains a diagnostic history when an sms is sent to your phone for each day. 3. The Trigger (iPhone): Utilizes an iOS Shortcut Automation that listens for a specific SMS phrase ("Wake up!") to trigger a physical alarm. ⚙️ Setup instructions Step 1: Google Cloud Platform Enable the Distance Matrix API in your Google Cloud Console. Generate an API Key and restrict it to your IP if possible. Step 2: Twilio configuration Gather your Account SID and Auth Token. Ensure your personal mobile number is verified in the Twilio console to receive messages. Step 3: iOS Shortcut automation Open the Shortcuts App → Automation → New Automation. Select Message → Message Contains: Wake up! → Action: Add "Start Timer" or "Create Alarm." Important: Disable "Ask Before Running" and "Notify When Run." 💡 Node breakdown & logic Arrival Schedule (Cron): Defines the window when the workflow should be active (e.g., 7:00 AM – 8:00 AM). Traffic Monitor (Google Maps): Fetches the duration_in_traffic value. Wake-up Evaluator (Filter): Compares if Current Time + Traffic + 20 mins >= Arrival Time. SMS Dispatcher (Twilio): Sends the trigger phrase to your device. Activity Logger (Google Sheets): Records the 1st execution of the day and then, with the use of the google sheet and the IF loop, the workflow will stop sending sms after the first send.

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

This workflow automates the process of generating stylized product photos for e-commerce by combining real product shots with creative templates. It enables the creation of a complete set of images for an SKU from a single product photo and a set of reusable templates. The workflow uses Google Gemini (Nano Banana) for image editing and Airtable as the data source. Example use case. An apparel brand can use this workflow to turn plain product photos (e.g., socks on a white background) into lifestyle images that match their brand aesthetic. By combining each product photo with predefined templates and reference images, the workflow generates a variety of stylized results automatically - ready for marketing or online stores. How it works This workflow expects the following Airtable table setup: "Product Images"** - contains original product photos, one per record. "Reference Images"** - contains reference images for templates, one per record. "Templates"** - contains reusable generation templates. Each template includes a text prompt and up to three reference images. "Jobs"** - contains batch generation jobs. Each job references multiple product images and multiple templates. "Results"** - contains the generated outputs. Each result includes a generated image, references to the job, product image, and template, and a status field (pending, approved, rejected). The workflow is triggered by a webhook that receives a job ID from Airtable. It then: Fetches the job record. Retrieves the associated product images and templates (each with its text prompt and reference images). Downloads all required product and reference images. For each product-template combination, sends these images and the prompt to Google Gemini to generate new AI-edited images. Saves the generated images back into Airtable. NOTE: A separate workflow should handle the human-in-the-loop approval process and any regeneration of rejected results. Requirements Airtable Personal Access Token Google Gemini API key Setup Ensure all required Airtable tables exist. Configure parameters in the parameters node: Set Airtable Base ID Set ID of the attachment field in the "Results" table (where the generated images will be uploaded) Configure credentials for all Airtable nodes. Set Google Gemini API key for the "Generate..." nodes.

This workflow turns a Google Sheet into a fully automated content calendar for BlueSky. It handles single posts, multi-post threads, and image attachments, allowing you to manage your entire social presence from a simple spreadsheet. Who is this for Ideal for social media managers, content creators, and growth marketers who want to schedule content in bulk without using expensive third-party tools. What it does It runs on a schedule to check your Google Sheet for posts marked "Ready." It automatically handles: Threading:** Links posts together if they share a Thread ID and Sequence. Images:** Downloads image URLs and uploads them as blobs to BlueSky. Status Updates:** Marks rows as "Posted" and saves the live URL back to your sheet. How to set up Google Sheet: Create a sheet with these columns: Content, Thread ID, Sequence (use '1' for single posts), Image URL, Scheduled Time, Status, Post Link. Important: Even if it is a single post (not a thread), you must add a unique Thread ID. Note: Image URL is optional. Format: Set the "Scheduled Time" column type to Plain Text to prevent date errors. (A sample Google Sheet link is provided inside the workflow notes). Credentials: Enter your BlueSky Handle and App Password in the "Configuration" node. Select Sheet: In both the "Get row(s)" and "Update row" nodes, select your specific Google Sheet. 🚀 The BlueSky Growth Suite This workflow is part of a 3-part automation suite designed to help you grow on BlueSky: Part 1: Post Scheduler** (This template) Part 2: Analytics Tracker** (Track likes/reposts back to Sheets) Part 3: Lead Magnet Bot** (Auto-DM users who reply to your posts)

📈 YouTube Trend Finder Workflow using n8n & RapidAPI Description: Easily discover trending YouTube videos by country and language using this automated n8n workflow. The flow leverages the YouTube Trend Finder API and logs insights to Google Sheets — ideal for content creators, marketers, and researchers. 🔗 Node-by-Node Explanation | Node Name | Type | Description | |-----------------------------|--------------------|-----------------------------------------------------------------------------| | 1. On form submission | Form Trigger | Captures user input for country and language through a web form. | | 2. Trend Finder API Request | HTTP Request | Sends a request to YouTube Trend Finder API with the form data. | | 3. Re format output | Code | Extracts and reshapes API response data like title, link, and tags. | | 4. Google Sheets | Google Sheets | Appends the trending video data into a structured spreadsheet. | 🎯 Use Cases 🔍 Content Research: Find top-trending videos in any region or language for idea inspiration. 📈 Marketing Intelligence: Track video trends to tailor your video marketing strategy. 📰 Trend Monitoring: Journalists and analysts can quickly surface viral video topics. ✅ Benefits of this Workflow No Coding Required:** Easy-to-use form interface for non-technical users. Real-Time Trends:* Instantly access trending YouTube content with the *YouTube Trend Finder API**. Automated Logging:** Stores data directly in Google Sheets for future analysis or sharing. Customizable:** Easily modify for more inputs like video category, max results, or add filters. Create your free n8n account and set up the workflow in just a few minutes using the link below: 👉 Start Automating with n8n Save time, stay consistent, and grow your LinkedIn presence effortlessly!

Who this is for This workflow is for content teams, marketers, and solo site owners who draft posts in Google Sheets and want a reliable way to publish to WordPress automatically — including featured images and tags. What it does Pulls rows from a Google Sheet where status = READY Processes rows one-by-one (safe for multiple posts in a single run) If image_url is present, downloads the image and uploads it to WordPress Media, then uses it as featured_media Parses hashtags into clean tag slugs, checks if each tag exists in WordPress, and creates missing tags Publishes the post via the WordPress REST API (/wp-json/wp/v2/posts) with the collected tag IDs Updates the same Google Sheets row to POSTED and writes posted_at + post_url How to set up 1) Make a copy of the Google Sheets template: https://docs.google.com/spreadsheets/d/1lJDeaN75c1hBk0gddsdvbeXDuxDr5Q-NablHRSjvLjQ/edit?gid=0#gid=0 2) Connect Google Sheets credentials in n8n and point the workflow to your spreadsheet + sheet tab. 3) Connect WordPress credentials (recommended: Application Password) for REST API access. 4) Ensure your sheet has columns like: id, status, title, excerpt, body, image_url, hashtags. Requirements WordPress site with REST API enabled Credentials set via n8n (no hardcoded secrets) Publicly accessible image_url (or adjust the workflow for private assets) How to customise Swap Manual Trigger for Cron to publish on a schedule Add categories, custom post types, or draft mode Extend error handling to write error_message and set status = ERROR when publishing fails

🚀 Overview This workflow is a powerful B2B Lead Generation engine designed specifically for SDRs (Sales Development Representatives). It automates the entire process of finding, enriching, and qualifying prospects directly from Google Maps based on any industry and location. Instead of manual searching, this pipeline uses a "Search & Enrich" strategy to extract high-value data that isn't available in standard search results, such as direct phone numbers and websites. ✨ Key Features User-Friendly Input: Triggered via an **n8n Form, making it easy for non-technical team members to start a search. Deep Enrichment: Uses the **Google Places API (Text Search & Details) to get granular information. Smart Pagination**: Built-in logic to handle next_page_token, ensuring you fetch all available leads (e.g., up to 60+ per run). Data Intelligence: A custom **JavaScript node normalizes data, removes special characters, and handles duplicates using a composite key (Name + Address). Quality Gate: Includes a validation step to ensure only leads with a **valid phone number reach your database. 🛠️ How it Works Form Trigger: Enter the "Business Type" and "City". API Discovery: The workflow queries Google Maps and handles pagination automatically. Item Splitting: Each result is isolated to fetch specific Place Details. Merge & Clean: Data from both API calls are merged and sanitized via code. Validation: The workflow filters out incomplete leads. Sheet Logging: Validated leads are appended to a Google Sheets spreadsheet in real-time. 📋 Requirements Google Maps API Key** (with Places API enabled). Google Sheets** credentials. An active n8n instance.

Active Job Scraper Workflow Using RapidAPI Jobs Search Realtime Data API This powerful Active Job Scraper workflow uses the RapidAPI Jobs Search Realtime Data API to fetch real-time job listings from leading job boards like Indeed, LinkedIn, ZipRecruiter, and Glassdoor. Overview Leverage the Jobs Search Realtime Data API on RapidAPI to gather fresh job data from Indeed, LinkedIn, ZipRecruiter, and Glassdoor. This n8n workflow lets you: Search jobs by location, keywords, job type, and remote options across these major platforms. Collect detailed job information including descriptions and metadata. Automatically save the scraped results into Google Sheets for easy tracking and analysis. Why Choose This Workflow? By integrating the RapidAPI Jobs Search Realtime Data API, you can scrape job listings from the most popular job sites—Indeed, LinkedIn, ZipRecruiter, and Glassdoor—all in one place. Customize your search parameters and get results tailored to your needs. Workflow Components | Node | Description | |------------------|-----------------------------------------------------------------| | Form Trigger | Collects input such as location, search term, job type, and remote status. | | HTTP Request | Calls the RapidAPI Jobs Search Realtime Data API to fetch jobs from Indeed, LinkedIn, ZipRecruiter, and Glassdoor. | | Code Node | Processes and formats the API response data. | | Google Sheets | Appends the extracted job listings to your spreadsheet. | 🔑 How to Get API Key from RapidAPI Jobs Search Realtime Data API Follow these steps to get your API key and start using it in your workflow: Visit the API Page 👉 Click here to open Jobs Search Realtime Data API on RapidAPI Log in or Sign Up Use your Google, GitHub, or email account to sign in. If you're new, complete a quick sign-up. Subscribe to a Pricing Plan Go to the Pricing tab on the API page. Select a plan (free or paid, depending on your needs). Click Subscribe. Access Your API Key Navigate to the Endpoints tab. Look for the X-RapidAPI-Key under Request Headers. Copy the value shown — this is your API key. Use the Key in Your Workflow In your n8n workflow (HTTP Request node), replace: "x-rapidapi-key": "your key" with: "x-rapidapi-key": "YOUR_ACTUAL_API_KEY"

Who is this for This template is essential for Remote Operations Managers, HR Teams, and Project Leads managing distributed teams across different countries. It prevents scheduling conflicts by automatically flagging when a regional team is out of office and identifying when multiple teams are off simultaneously. What it does Stop manually Googling "Is it a holiday in Berlin today?" This workflow automates your team availability calendar. It triggers on a weekly schedule. It takes your team's locations (e.g., KR, MX) and a "Lookahead" range (e.g., 50 days). It fetches official public holidays for both the current and next year using the Nager.Date API (to ensure year-end holidays aren't missed). It filters the results to find only holidays occurring within your defined lookahead window. It compares dates across countries to identify "Shared Holidays" (dates where multiple teams are off). It logs these holidays into a Notion database and notifies the team via Slack, specifically highlighting if a holiday is shared. How to set up Notion: Create a Database with properties: Name (Title), Date (Date), and Shared Countries (Text). Slack: Connect your Slack account in the credentials. Configuration: Define Team Countries: Enter the 2-letter country codes (e.g., "KR", "US") in the Set node. Define Days to Lookahead: Set how many days into the future you want to check (default is 50). Add to Notion: Select your Database ID. How to customize Filter Logic:** The "Filter Upcoming" node handles the date logic. You can modify this to check for specific holiday types (e.g., exclude "Optional" holidays). Shared Logic:** The "Find Shared Holidays" node calculates overlaps. You can adjust the JavaScript here if you want to change the format of the shared message sent to Slack. Destinations:** Swap the Notion node for Google Calendar to block off time directly.

This template gives you a framework to use skills in any n8n agent. You can use this as a starting point and add any other tools or patterns needed for your use case. What are “skills”? Skills are a context management standard created by Anthropic for use in Claude code. Basically, instead of having a HUGE system prompt, skills split that into lots of small, structured instruction files that tell an agent how to do a specific kind of task. Instead of stuffing a massive prompt full of rules, the agent: finds the relevant skill file reads it and follows the steps inside It’s a simple pattern that makes managing system prompts for general purpose agents much more straightforward. See an example of a skills repo here. What this workflow does Responds to messages in n8n Chat (or Chat Hub) Builds an “available skills” index from one or more GitHub repos Lets the agent browse folders + fetch skill files (Markdown) as needed Uses the skill content to guide how it completes tasks How it (roughly) works A chat message comes in. The workflow lists directories in the configured skills repos (root + /skills if present), filters out noise, and merges everything into one directory map. That directory map gets injected into the agent’s system prompt so it knows what skill files exist. When it needs instructions, it uses tools: List Files by Path Name to explore folders Get a File From GitHub to pull the skill file as raw text (no base64) Same “skills” pattern as the CLI tools The flow is: find a skill → open it → follow the steps, the same way it works in the CLI tools, but running inside n8n, so you don’t need to download or install anything locally. How to set it up (Required) Add your GitHub credentials to each node that needs it (Required) Add your OpenRouter credentials to the chat node or replace with the provider of your choosing (Optional) Add more repos to SKILLS_REPOS (any skills GitHub repo works as long as your credentials have access to it, such as any public repo) (Optional) Add more tools and turn it into whatever agent you actually need