Workflow Templates

How it works This workflow sends WhatsApp messages and emails in bulk using contact data stored in Google Sheets. Contacts are processed in small batches to control throughput and avoid API rate limits. WhatsApp and email are treated as independent channels and are sent only when their status is marked as pending. All success and failure results are written back to Google Sheets to enable tracking, retries, and safe re-runs. Step-by-step Step 1: Fetch contacts & batch processing** Manual Trigger – Starts the workflow manually. Get Contacts – Reads contact data from Google Sheets. Split In Batches – Processes contacts in controlled batch sizes. Step 2: Email preparation & sending** Has Email Address – Checks whether the contact has an email address. IF Mail Pending – Ensures the email is still marked as pending. PrepareEmail email – Loads the selected InboxPlus email template. Build HTML Email – Builds the final HTML email body. Fetch Email Image – Downloads images for inline or attachment usage. Send Gmail – Sends the email via Gmail. Delivered – Confirms successful email delivery. Step 3: WhatsApp message sending** Has Phone Number – Checks whether the contact has a phone number. IF WhatsApp Pending – Ensures the WhatsApp message is still pending. Send template – Sends the approved WhatsApp template message. Sent – Confirms message acceptance by WhatsApp. Step 4: Delivery status updates** Update Sheet – Writes successful delivery results back to Google Sheets. Mail Failure – Updates Google Sheets if email delivery fails. Whatsapp Failure – Updates Google Sheets if WhatsApp delivery fails. Why use this? Prevents duplicate messages with channel-level pending checks Handles WhatsApp and email independently in one workflow Supports safe retries without resending completed messages Keeps Google Sheets as the single source of truth Scales bulk outreach safely using batch-based execution

Tasks Briefing This template posts a clean, Slack-ready morning summary of your Google Tasks due today. It fetches tasks, filters only those due “today” in your timezone, asks a local LLM (via LangChain + Ollama) to produce a short summary (no steps, just a concise brief), strips any hidden <think> blocks, and delivers the message to your chosen Slack channel. How it works Trigger at Morning (Cron) – runs at 7:00 AM (you can change the hour) to kick things off daily. Get many tasks (Google Tasks node) – pulls tasks from your selected Google Tasklist. Code (Filter Due Today) – normalizes dates to your timezone, keeps only tasks due today, and emits a fallback flag if none exist. If – routes: True (has tasks) → continues to the LLM summary path. False (no tasks) → sends a “No tasks due today” message to Slack. Code (Build LLM Prompt) – builds a compact, Markdown-only prompt for the model (no tool calls). Basic LLM Chain (LangChain) + Ollama Model – generates a short summary for Slack. Code (Cleanup) – removes any <think>…</think> content if the model includes it. Send a message (Slack) – posts the final brief to your Slack channel. Required credentials Google Tasks OAuth2 API** – to read tasks from your Google Tasklist. Slack API** – to post the summary into a channel. Ollama** – local model endpoint (e.g., qwen3:4b); used by the LangChain LLM nodes. Setup Instructions Google Tasks credential In Google Cloud Console: enable Google Tasks API, create an OAuth Client (Web), and set the redirect URI shown by n8n. In n8n Credentials, add Google Tasks OAuth2 API with scope: https://www.googleapis.com/auth/tasks (read/write) or https://www.googleapis.com/auth/tasks.readonly (read-only). In the Get many tasks node, select your credential and your Tasklist. Slack credential & channel In n8n Credentials, add Slack API (bot/user token with chat:write). In Send a message nodes, select your Slack credential and set the Channel (e.g., #new-leads). Ollama model (LangChain) Ensure Ollama is running on your host (default http://localhost:11434). Pull a model (e.g., ollama pull qwen3:4b) or use another supported model (llama3:8b, etc.). In Ollama Model node, select your Ollama credential and set the model name to match what you pulled. Timezone & schedule The Cron node is set to 7:00 AM. Adjust as needed. The Code (Filter Due Today) node is configured for Asia/Dhaka; change the TZ constant if you prefer a different timezone. (Optional) Cleanup safety The template includes a Code (Cleanup) node that strips <think>…</think> blocks from model output. Keep this connected before the Slack node. Test the flow Run the workflow once manually: If you have tasks due today, you should see a concise summary posted to your Slack channel. If none are due, you’ll receive a friendly “No tasks due today” message. Activate When everything looks good, toggle the workflow Active to receive the daily summary automatically.

Dynamic Email Signature Creator (PDF + HTML) Create gorgeous, branded, professional email signatures automatically — from a simple POST request. This workflow turns user details into a premium HTML signature, converts it into PDF, and delivers it instantly via Gmail, along with a clean JSON response. ✨ What This Template Does This workflow automatically: Receives user details (name, role, email, phone, links) via Webhook Extracts & validates inputs Generates a modern, premium HTML signature with icons + layout Converts HTML → high-quality PDF using HTMLCSS → PDF service Emails both the HTML signature preview + PDF attachment to the user Returns a clean JSON success response with the pdf_url Works 100% automated — no manual designing needed Perfect for: HR onboarding Corporate identity management Personal branding Team signature standardization Automated client signature setup 🔥 Features Beautiful modern design** Clean branding layout with icons (LinkedIn, Instagram, Website) Professional color palette + typography Auto-generated PDF (print-ready) Mobile-friendly & email-safe HTML Supports any social links Extremely easy to integrate with forms, portals, CRMs Fast: Signature generated in < 3 seconds 🧩 How It Works Webhook receives user information Input extractor formats the fields HTML template dynamically inserts user values HTML → PDF generator creates high-resolution output Email node sends signature + PDF Workflow responds with JSON (pdf_url, status, etc.) ⚙️ Setup Needed Connect these credentials in n8n: HTML → PDF** (PDFMunk account) Gmail** (for sending the final signature email) Update inside the HTML template: Brand colors Logo URL (optional) Social icon colors / links (optional) That’s it — your automated signature generator is live. 🏷️ Tags email-signature, branding, pdf-generator, html-template, gmail, automation, onboarding, corporate

LinkedIn Content Generation Workflow Summary Automated workflow that transforms Notion content notes into publication-ready LinkedIn posts using Claude AI. Monitors Notion database and generates multiple variations based on structured outlines, so that the author can pick the one they like most. Use Cases Automate LinkedIn content creation from content planning database. Generate multiple post variations from a single outline. Maintain consistent voice and formatting across all posts. Scale content production while preserving quality. How It Works Trigger - Monitors Notion "Content Plan" database hourly for updates. Conditional Check - Verifies "LinkedIn Post (Main)" tag and "Ready for Writing" status Main Post - Claude generates single post from project name and notes Outline Analysis - Parallel process creates 3 distinct post concepts with different angles Multi-Post Generation - Each outline becomes a complete LinkedIn post Save to Notion - All posts automatically saved to database AI Setup: Claude Sonnet 4.5 (claude-sonnet-4-5-20250929) Main post: temperature 0.8 (creative) Multi-post: default temperature (consistent) How to Use Setup a content database in notion, or link your existing one: Use field mapping as outlined below or update field mapping in n8n template. Add content to Notion: Project name (topic) Notes (article content/key points) Tag: "LinkedIn Post (Main)" Status: "Ready for Writing" Workflow triggers automatically (hourly check) Retrieve posts from Notion database Review and publish to LinkedIn Requirements Credentials: Notion API (access to Content Plan database) Anthropic API key OpenAI API Key Notion Database: Connect Database Required properties: Project name (text) Notes (rich text) Tags (multi-select with "LinkedIn Post (Main)") Status (select with "Ready for Writing") Notes: Posts optimized for 1800 character limit Generates both single posts and multi-angle variations

Webhook → OpenAI → Jira “Bug Suspicion” → Slack QA Escalation This workflow ingests bug reports via a webhook, uses OpenAI to triage and tag them, creates a Jira Bug in project APP with AI-driven labels and alerts QA in Slack. Import the JSON, add OpenAI + Jira + Slack credentials, set the webhook path, choose your Slack channels and activate. Quick Start – Implement in 60 Seconds Import the JSON into n8n. Add credentials to AI Bug Analysis (OpenAI), Create Jira nodes and both Slack Alert nodes. Set webhook path advanced-bug-triage; test with a POST body containing priority, summary and category. Adjust Slack channels qa-alerts-high and qa-general if needed. Activate and verify a test POST flows through Jira and Slack. That’s it. Jira issue gets created and Slack gets notified instantly. What It Does The workflow acts as an AI-assisted bug triage bridge. A webhook receives incoming bug suspicions, which are then analyzed by OpenAI to determine priority and category. Based on the AI output, the flow routes to the appropriate Jira creation path and applies standardized labels for consistent reporting. After creating the Jira Bug in project APP, the workflow escalates to Slack: high-priority items go to qa-alerts-high, while normal items go to qa-general. The result is a fast, low-friction path from external bug signals to actionable Jira issues with immediate QA visibility. Who’s It For QA teams wanting automated Jira escalation. Developers integrating external systems with Jira. Product teams capturing automated “bug suspicion” signals. Monitoring or Sentry-like pipelines. Companies wanting lightweight reporting without building custom infrastructure. Pre-Requisites n8n (cloud or self-hosted). Jira account with permission to create Bug issues. Jira project key: APP (or customize). OpenAI credentials (for AI Bug Analysis) Slack Workspace + Bot token. Ability to send POST request to n8n Webhook endpoint. How It Works & Setup Instructions Webhook Trigger** (advanced-bug-triage): Accepts POST payloads (e.g., summary, description, priority, category). AI Bug Analysis** (OpenAI): Analyzes the payload for sentiment/priority/category (configure your prompt/fields as needed). Priority Switch**: Routes items to the correct Jira creation path (High/Medium/Low). Create Jira (High/Medium/Low)**: Creates Bug issues in project APP, labeling with ai-triaged and the AI-detected category. Slack Alert (High / Normal)**: Notifies QA with the Jira key; high priority goes to qa-alerts-high, others to qa-general. Step 1: Configure Webhook Node Method: POST Path: bug-suspicion Endpoint example: https://YOUR-N8N-URL/webhook/bug-suspicion Step 2: Add OpenAI Credentials Open OpenAI node Select credentials Modify the prompts as needed Step 3: Add Jira Credentials Open Create Jira Bug node Select credentials Ensure access to project APP Ensure permission to create Bug issue type Step 4: Add Slack Credentials Open Slack QA Escalation node Choose Slack Bot credentials Set QA channel Slack message uses: Issue is created in jira for this key <ISSUE-KEY> Step 5: Test Webhook { "title": "Login button unresponsive" } Step 6: Activate Workflow Enable Active toggle. How to Customize Nodes Webhook Trigger Add API keys, tokens or Basic Auth Add JSON validation Jira Node You may add: "additionalFields": { "labels": "bug-suspicion,auto-detected", "description": "={{$json["details"]}}" } Slack Node Customize formatting, attachments, mentions or channels. AI Node for Bug Analysis Tune the prompt, map input fields or adjust model parameters for stricter/looser triage. Priority Switch Modify routing thresholds, add more branches or change default fallback. Add-ons (Optional Enhancements) Email alerts. Severity scoring using AI. Push bug data to Notion or Google Sheets. Add screenshots/logs. Multi-channel notifications. Auto-assign Jira issues based on category or component. Add a fallback email notification for high-priority tickets. Push payloads to a data store (e.g., Sheets/DB) for analytics. Add a secondary Slack DM to on-call for P1. Enrich tickets with logs/links/screenshots from the payload. Use Case Examples Automated QA test failures → Jira + Slack. Monitoring system detects abnormal activity. Browser extension for internal bug reporting. CI/CD pipeline error → instant QA alert. External scripts or tools triggering bug reports. Monitoring alerts auto-create Jira bugs with AI-prioritized severity and Slack escalation. Customer support form pushes suspected bugs directly into Jira with category labels. QA automation failures stream into Jira with priority-based Slack alerts. SRE on-call receives P1 Slack alerts while lower priorities route to the general QA channel. Product beta feedback is categorized by AI and logged as Jira bugs for triage. Troubleshooting Guide | Issue | Cause | Solution | |-------|--------|-----------| | Webhook not receiving data | Wrong URL/method | Use POST + correct path | | Jira issue not created | Wrong credentials/project | Verify Jira credentials + APP project | | Slack message not sent | Bot not allowed in channel | Invite bot to channel | | Jira fields empty | Missing JSON field | Ensure payload includes "title" | | Slack shows undefined | Jira response changed | Add Debug node to inspect output | | Workflow not running | Not activated | Turn ON "Active" | Need Help? If you want help customizing this workflow or building similar n8n workflow automations, the WeblineIndia team can assist with: Jira integrations Slack automation API-based bug pipelines DevOps automation AI-driven severity scoring And so much more. Reach out anytime for implementation or enhancements.

Arabic OCR Telegram Bot How it Works Receive PDF Files - Users send PDF documents via Telegram to the bot OCR Processing - Mistral AI's OCR service extracts Arabic text from document pages Text Organization - Processes and formats extracted content with page numbers Create Google Doc - Generates a formatted document with all extracted text Deliver Results - Sends users a clickable link to their processed document Set up Steps Setup Time: ~20 minutes Create Telegram Bot - Get bot token from @BotFather on Telegram Configure APIs - Set up Mistral AI OCR and Google Docs API credentials Set Folder Permissions - Create Google Drive folder for storing results Test Bot - Send a sample Arabic PDF to verify OCR accuracy Deploy Webhook - Activate the Telegram webhook for real-time processing Detailed API configuration and Arabic text handling notes are included as sticky notes within the workflow. What You'll Need: Telegram Bot Token (free from @BotFather) Mistral AI API key (OCR service) Google Docs/Drive API credentials Google Drive folder for document storage Sample Arabic PDF files for testing Key Features: Real-time progress updates (5-step process notifications) Automatic page numbering in Arabic Direct Google Docs integration Error handling for non-PDF files

How it works Every hour, the workflow checks the RSS feed https://www.artificialintelligence-news.com/feed/ for new articles. For each new item, it extracts the title, snippet, and full content, then sends them to an AI model to summarize and optionally translate. The processed summary is passed to another AI model (with a personalized “Patrik” assistant tone) to generate a newsletter-style text. Finally, the result is saved as a draft email in Gmail, ready to review and send. How to use Set your preferred language in the Information Extractor system prompt. Update the RSS feed URL if you want to pull articles from a different source. Customize the assistant tone in the Message a model node for your newsletter style. Connect your Gmail account to the Create a draft node. Activate the workflow — every hour it will fetch new articles, generate newsletter content, and save them as Gmail drafts. Customising this workflow Change the source: Replace the RSS feed URL in the RSS Feed Trigger node. Language & length: Edit the system prompt in the Information Extractor to set your preferred language and summary style. Tone & format: Adjust the Message a model node to define the assistant’s personality, structure (headlines, bullets, CTA), or output as HTML. Email settings: Change the subject, sender, or draft folder in the Create a draft node. Frequency: Modify the trigger schedule to run daily, weekly, or at custom intervals.

Description This workflow sends a summary of your meeting minutes via Gmail, directly from the notes stored in your Google Sheet. Context Taking notes during meetings is important, but sharing them with the team can be time-consuming. This workflow makes it simple: just write down your meeting minutes in a Google Sheets, and n8n will automatically send them by email after each meeting. Who is this for? Perfect for anyone who: Uses Google Sheets to keep track of meeting notes. Wants to automatically share minutes with teammates or stakeholders. Values speed, productivity, and automation. Requirements Google account. Google Sheets (with your meeting minutes). You will need to setup the required columns first : Topic, Status, Owner, Next Step. Gmail. How it works ⏰ Trigger starts after a new row is added in your Google Sheet. 📑 The meeting minutes are retrieved from the sheet. 📨 Gmail automatically sends the minutes to the configured recipients. Steps 🗒️ Use the sticky notes in the n8n canvas to: Add your Google credentials (Sheets + Gmail). Define your sheet and recipient email addresses. Test the workflow to check if the minutes are sent. You’ll get this: An email containing your full meeting minutes, straight from your notes. Tutorial video Watch the Youtube Tutorial video About me : I'm Yassin, IT Project Manager, Agile & Data specialist. Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin

Track AI search rankings from Perplexity to Google Sheets and Slack This workflow automates Generative Engine Optimization (GEO) tracking by monitoring how your company appears in AI search results. It generates strategic queries, simulates searches on AI engines like Perplexity via BrowserAct, logs the responses for historical tracking, and delivers a graded performance report to Slack. Target Audience SEO specialists, brand managers, marketing directors, and growth teams focusing on AI visibility and reputation management. How it works Initialize Tracking: The workflow runs on a schedule, creates a new dated tab in your Google Sheet, and fetches your company details (Name and Category). Generate Strategy: An AI Agent (using OpenRouter/Gemini) generates three specific search queries: Discovery: Broad category search (e.g., "Best CRM for startups"). Comparison: Direct competitor face-off (e.g., "Pipedrive vs Salesforce"). Validation: Specific fact-checking (e.g., "Is Pipedrive good for visual pipelines?"). Simulate Searches: BrowserAct executes these queries on an AI answer engine (like Perplexity) to capture the real-time AI response. Log Data: The workflow loops through the results and saves the raw AI answers to the daily Google Sheet. Analyze & Report: A second AI Agent reviews the saved data, grades the visibility (Green/Yellow/Red), and sends a summarized "GEO Scorecard" to Slack. How to set up Configure Credentials: Connect your Google Sheets, Slack, BrowserAct, and OpenRouter accounts in n8n. Prepare BrowserAct: Ensure the GEO Results & Rank Tracking template is saved in your BrowserAct account. Setup Google Sheet: Create a Google Sheet with a tab named Main Sheet. Add headers: Company name and Worknig category. Fill in row 2 with your details. Select Spreadsheet: Open the Create sheet, add headers, Get Company data, Retrieve Stored Data, and Store Extracted Data nodes to select your specific spreadsheet. Configure Notification: Open the Send Message to Team on Slack node and select your target Slack channel. Google Sheet Headers Tab 1: Main Sheet (Input) Company name Working Category Tab 2+: [Date] (Generated automatically by the workflow) Search Result Requirements BrowserAct* account with the *GEO Results & Rank Tracking** template. Google Sheets** account. Slack** account. OpenRouter** account (or compatible LLM credentials). How to customize the workflow Change the AI Engine: Modify the BrowserAct template to search on ChatGPT or Google Gemini instead of Perplexity. Adjust Grading Logic: Update the system prompt in the Company data analyzer node to change how the AI scores the results (e.g., focus more on sentiment than ranking). Expand Reporting: Add an Email node to send a weekly summary of the Google Sheet data to stakeholders. Need Help? How to Find Your BrowserAct API Key & Workflow ID How to Connect n8n to BrowserAct How to Use & Customize BrowserAct Templates Workflow Guidance and Showcase Video Master GEO: Track Your AI Search Rankings with n8n & Perplexity 🌍

Using the power and ease of Telegram, send a simple text or audio message to a bot with a request to add a new Task to your Notion Tasks database. How it works ChatGPT is used to transacribe the audio or text message, parse it, and determine the title to add as a new Notion Task. You can optionally include a "do date" as well and ChatGPT will include that when creating the task. Once complete you will receive a simple confirmation message back. Minimal Setup Required Just follow n8n's instructions on how to connect to Telegram and create your own chatBot, provide the chatID in the 2 Telegram nodes, and you're finished! A few optional settings include tweaking the ChatGPT system prompt (unnecessary) and the timezone for your Notion Task(s).

Automatically discover trending developer and security topics, generate SEO-optimized blog posts, and publish them to WordPress as drafts — complete with AI-generated featured images. How it works Discover trends — Perplexity AI identifies the hottest topic from the last 24-48 hours Queue topics — Topics are saved to Google Sheets for tracking and management Generate content — Perplexity creates complete blog posts with titles, sections, keywords, and meta descriptions Create draft — Content is published as a WordPress draft for your review Generate image — HuggingFace FLUX creates a featured image based on the content Attach media — The image is uploaded to WordPress and assigned to the post Setup steps Add credentials for Perplexity AI, Google Sheets, WordPress, and HuggingFace Create a Google Sheet with columns: Topic, is_generated, title, content, keywords, meta_description Replace YOUR_GOOGLE_SHEET_ID in the Google Sheets nodes with your sheet ID Replace your-site.com with your WordPress site URL Replace YOUR_TOKEN_HERE with your HuggingFace API token Update the authorId in the WordPress node to match your author Tools used Perplexity AI** — Trend discovery and content generation Google Sheets** — Topic queue and workflow tracking WordPress REST API** — Post creation and media uploads HuggingFace FLUX** — AI image generation Ideal for developers, content marketers, and agencies who want automated content pipelines with editorial control.

Who’s it for This workflow is for marketers, founders, and content strategists who want to identify business opportunities by analyzing Reddit discussions. It’s ideal for B2B, SaaS, and tech professionals looking for fresh LinkedIn post ideas or trend insights. How it works / What it does This workflow automatically: Fetches Reddit posts & comments based on a selected subreddit and keyword. Extracts pain points & insights using OpenAI (ChatGPT) to identify key frustrations and trends. Generates LinkedIn post ideas with headlines, hooks, and CTAs tailored for professional audiences. Saves all results into Google Sheets for easy tracking, editing, and sharing. It uses AI to turn unstructured Reddit conversations into actionable content marketing opportunities. How to set up Clone this workflow in your n8n instance. Configure credentials: Reddit OAuth2 (for fetching posts & comments) OpenAI API key (no hardcoding—use credentials in n8n) Google Sheets OAuth2 (for output) Run the workflow or trigger it using the built-in Form Trigger (provide subreddit & keyword). Check the generated Google Sheet for analyzed insights and post suggestions. Requirements n8n (self-hosted or cloud) Reddit account with API credentials OpenAI API key (GPT-4o recommended) Google Sheets account How to customize the workflow Change the AI prompt to adjust tone or depth of insights. Add filtering logic to target posts with higher engagement. Modify the Google Sheets output schema to include custom fields. Extend it with Slack/Email notifications to instantly share top insights.