Workflow Templates

Upload a PDF and instantly get a neatly formatted Google Doc with all the readable text—no manual copy-paste, no messy line breaks. What this workflow does Accepts PDF uploads via a public form Sends the file to Mistral Cloud for high-accuracy OCR Detects and merges page images with their extracted text Cleans headers, footers, broken lines, and noise Creates a new Google Doc in your chosen Drive folder Writes the polished markdown text into the document What you need Mistral Cloud API key with OCR access Google Docs & Drive credentials connected in n8n Drive folder ID for new documents A PDF file to process (up to 100 MB) Setup Import the workflow into n8n and activate credentials. In Trigger • Form Submission, copy the webhook URL and share it or embed it. In Create • Google Doc, replace the default folder ID with yours. Fill out Mistral API key under Mistral Cloud API credentials. Save and activate the workflow. Visit the form, upload a PDF, name your future doc, and submit. Open Drive to view your newly generated, clean Google Doc. Example use cases Convert annual reports into editable text for analysis. Extract readable content from scan-only invoices for bookkeeping. Turn magazine PDFs into draft blog posts. Digitize lecture handouts for quick search and annotation. Convert image-heavy landing pages / advertorials into editable text for AI to analyze structure and content.

📘 Description: This workflow automates the incident response lifecycle — from creation to communication and archival. It instantly creates Jira tickets for new incidents, alerts the on-call Slack team, generates timeline reports, logs the status in Google Sheets, and archives documentation to Google Drive — all automatically. It helps engineering and DevOps teams respond faster, maintain audit trails, and ensure no incident details are lost, even after Slack or Jira history expires. ⚙️ What This Workflow Does (Step-by-Step) 🟢 Manual Trigger – Start the incident creation and alerting process manually on demand. 🏷️ Define Incident Metadata – Sets up standardized incident data (Service, Severity, Description) used across Jira, Slack, and Sheets for consistent processing. 🎫 Create Jira Incident Ticket – Automatically creates a Jira task with service, severity, and description fields. Returns a unique Jira key and link for tracking. ✅ Validate Jira Ticket Creation Success – Confirms the Jira ticket was successfully created before continuing. True Path: Proceeds to Slack alerts and documentation flow. False Path: Logs the failure details to Google Sheets for debugging. 🚨 Log Jira Creation Failures to Error Sheet – Records any Jira API errors, permission issues, or timeouts to an error log sheet for reliability monitoring. 🔗 Combine Incident & Jira Data – Merges incident context with Jira ticket data to ensure all details are unified for downstream notifications. 💬 Format Incident Alert for Slack – Generates a rich Slack message containing Jira key, service, severity, and description with clickable Jira links. 📢 Alert On-Call Team in Slack – Posts the formatted message directly to the #oncall Slack channel to instantly notify engineers. 📋 Generate Incident Timeline Report – Parses Slack message content to create a detailed incident timeline including timestamps, service, severity, and placeholders for postmortem tracking. 📄 Convert Timeline to Text File – Converts the generated timeline into a structured .txt file for archival and compliance. ☁️ Archive Incident Timeline to Drive – Uploads the finalized incident report to Google Drive (“Incident Reports” folder) with timestamped filenames for traceability. 📊 Log Incident to Status Tracking Sheet – Appends Jira key, service, severity, and timestamp to the “status update” Google Sheet to build a live incident dashboard and enable SLA tracking. 🧩 Prerequisites Jira account with API access Google Sheets for “status update” and “error log” tracking Slack workspace connected via API credentials Google Drive access for archival 💡 Key Benefits ✅ Instant Slack alerts for new incidents ✅ Centralized Jira ticketing and tracking ✅ Automated timeline documentation for audits ✅ Seamless Google Drive archival and status logging ✅ Reduced MTTR through faster communication 👥 Perfect For DevOps and SRE teams managing production incidents Engineering managers overseeing uptime and reliability Organizations needing automated post-incident documentation Teams focused on SLA adherence and compliance reporting

📌Who is this for? HR teams, IT Operations, and System Administrators managing employee onboarding at scale. It’s perfect if you use Odoo 18 to trigger account requests and need Redmine + GitLab accounts created instantly and consistently. 📌The Problem Manual account creation creates bottlenecks: IT waits for HR notifications that often get missed or delayed. Duplicate accounts pile up when no one checks existing data first. Account creation timelines are inconsistent (sometimes correct, sometimes wrong). Zero visibility into what succeeded or failed. 📌What It Does Catches an employee account creation request from Odoo 18 → queries employee data → checks for existing accounts → creates only the accounts that are missing → notifies your team via Slack with the full status. Here's the flow in detail: Webhook trigger from Odoo 18 - automatically fires when your HR team marks an employee as needing Redmine, GitLab, or both. Fetch employee data from Odoo 18 - pulls email and account type requirements. Deduplicate requests - separates "needs both," "GitLab only," and "Redmine only" cases. Check for existing accounts - queries Redmine and GitLab to avoid duplicate creation attempts. Create accounts - uses Redmine and GitLab APIs to spin up accounts (only if they don't exist). Slack notification - sends a summary showing what was created, skipped, or failed- including error details if something went wrong. 📌Quick Setup Generate a Webhook URL in n8n and configure Odoo 18 to call it during onboarding. Add Redmine admin API key and GitLab admin access token. Enable /users.json (Redmine) and /users (GitLab) endpoints. Configure Slack webhook for notifications. Test with sample data, then activate. 📌Results Zero duplicates - the system checks before creating. Full visibility - Slack reports every single attempt. Instant delivery - new hires get accounts on day one. Dramatically reduced IT workload. 📌Take It Further Auto-assign projects in Redmine/GitLab post-creation. Generate passwords or TOTP setup and email them to new hires. Log everything to Google Sheets, Notion, or a database. Handle multi-tenant setups if your Odoo manages multiple organizations. Add provisioning for Slack, Google Workspace, VPN, or other systems. 📌Need help customizing? Contact me for consulting and support: Linkedin / Website

An AI inbox labelling manager that has reasoning attached to the ChatGPT inbox manager within n8n. Super simple yet highly effective automation. How it works: • Monitors Gmail inbox → triggers workflow when a new unread email is received. • Fetches email details including subject, body, and sender information. • Sends email content to OpenAI → uses AI to determine the most relevant label based on predefined rules. • AI uses a think tool → justifies why it selected that specific label. • Retrieves Gmail label IDs → matches AI’s choice to correct Gmail label for that email. • Adds the chosen label (e.g., Positive reply, priority email, etc) to the email automatically → optionally marks it as read/starred. • Continues monitoring → every new email is processed automatically, keeping the inbox organized. Set Up Steps • Connect Gmail account to the Gmail Node • Create OpenAI account & API key → go to OpenAI and sign up or log in. Once logged in, click Dashboard in the top menu. On the left sidebar, find API Keys and click Create new key. Copy this key — you’ll need it for n8n. Check your account balance → in the top-right, click your profile icon → Your Profile → Billing. Make sure your account has funds (e.g., $5 USD is enough for testing) so the API requests can run. Do these steps through this link: https://platform.openai.com/ • Retrieve Gmail label IDs → use the Gmail “get labels” node to fetch IDs for all labels you want the AI to use. • Use OpenAI (ChatGPT) node → set up system and user prompts with rules describing each label, and include the label IDs (Important). • Test the workflow → send example emails, check labeling, and refine AI prompt or label rules if needed. • Tip: Pin trigger data for testing (Gmail node "Watch Incoming Emails") → re-use the same email record to speed up testing without sending multiple emails. About this automation Handles multiple labels → adding new labels only requires updating the AI prompt (no extra nodes). Scales easily → works for any number of Gmail labels without cluttering the workflow. For a complete rundown on how to set this up watch my YouTube tutorial linked below See full video tutorial here: https://www.youtube.com/watch?v=7nda4drHcWw My LinkedIn: https://www.linkedin.com/in/seb-gardner-5b439a260/

Description Automatically convert structured Slack messages into Jira issues with parsed titles, descriptions, and priorities. This workflow also downloads file attachments from Slack (e.g., screenshots, logs, or documents) and uploads them directly into the created Jira issue. It then confirms success back to the Slack channel, ensuring transparency and seamless collaboration. 📋💬📎 What This Template Does Monitors a designated Slack channel for new issue reports. 🔔 Parses Slack message text with regex to extract title, description, priority, and type. 🧠 Creates a new Jira issue with the structured data. 🎫 Detects and processes attachments, splitting multiple files into batches. 📂 Downloads files from Slack using secure URLs and Slack bot authentication. 🔑 Uploads attachments directly into the created Jira issue. 📎 Sends a Slack confirmation with Jira issue key, link, and summary details. ✅ Key Benefits Eliminates manual Jira ticket creation from Slack messages. ⏱️ Preserves critical context by attaching screenshots, logs, and documentation. 📎 Ensures structured, standardized issue reporting across teams. 🔄 Provides instant Slack confirmation with direct Jira links. 📲 Handles multiple attachments gracefully with batch processing. ⚡ Features Slack Trigger – Monitors specific channels for new issue messages. 💬 Message Parsing Engine – Extracts title, description, priority, and type using regex + fallback logic. 📝 Jira Integration – Creates structured Jira issues with proper fields (summary, description, priority, type). 🎫 Attachment Handling – Splits, downloads, and uploads Slack files into Jira automatically. 📂 Slack Confirmation – Sends formatted success messages with clickable Jira links. 🔗 Robust Data Handling – Supports rich text, multiple files, and smart mappings of Slack priorities to Jira. 🧠 Requirements n8n instance (cloud or self-hosted). Slack Bot API credentials with channels:history, files:read, and chat:write permissions. Jira Software Cloud API credentials with project and issue creation permissions. Pre-configured Slack channel for reporting issues. Jira project set up with supported issue types (bug, task, feature, etc.). Target Audience Software development teams managing issue intake from Slack. 👩‍💻 QA and testing teams reporting bugs directly from Slack. 🧪 IT support teams needing structured Jira issues with attachments. 🛠️ Agile teams looking for seamless Slack → Jira integration. 🚀 Remote teams requiring real-time visibility into Jira issue creation. 🌐 Step-by-Step Setup Instructions Connect Slack and Jira credentials in n8n. 🔑 Configure the Slack channel ID to listen for issue reports. 💬 Map Jira project and issue type IDs in the “Create Jira Issue” node. 🎫 Customize parsing logic for message formats (default: Title: X, Description: Y, Priority: Z). 📝 Ensure Slack files can be downloaded with your bot token (files:read scope). 📂 Test with a sample message containing a title, description, and attachment. ✅ Deploy and monitor Slack → Jira issue creation in real-time. ⚡

🧑‍💻 Description This workflow automatically fetches new Gmail messages since the last run and appends them into a Google Sheet with their ID, snippet, and timestamp. It’s designed for professionals, small business owners, and operations teams who need a simple way to keep an ongoing log of emails, build lightweight CRMs, or power downstream automations like email tracking, reporting, or follow-up reminders. ⚙️ Setup Instructions for Gmail → Google Sheets Email Log 1️⃣ Connect Gmail In n8n → Credentials → New → Gmail OAuth2 Log in with your Gmail account & approve access Attach this credential to the Get new messages node in the workflow 2️⃣ Connect Google Sheets Copy this Google Sheet template into your own Drive In n8n → Credentials → New → Google Sheets (OAuth2) → log in with your Google account & save In the workflow, select your Spreadsheet ID and Worksheet (Sheet1 by default) in the Google Sheets nodes 🧠 How Email Logging Automation Works Get Current Emails** → Reads the last logged messages from Google Sheets Get Max Date** → Finds the most recent email timestamp Combine** → Passes the last timestamp and today’s date together Get New Messages** → Fetches all new Gmail messages after the last logged date Add Emails to Sheets** → Appends message ID, snippet, and date to the sheet 🎛️ Customization Guidance Filter by Sender or Subject** → Modify the Gmail query to only log messages from specific addresses or with certain keywords. Track Labels** → Add Gmail labels to your sheet to separate categories (e.g., “Leads,” “Support,” “Invoices”). Auto-Reply** → Extend with an additional Gmail node to send automated responses to new messages. Send Alerts** → Add a Slack or Email node to ping your team whenever a new email is logged. Analytics** → Use Google Sheets formulas or connect to BI tools to analyze trends like response times or sender frequency. 📬 Contact Need advanced customization (e.g., multi-inbox tracking, CRM integration, or automated follow-ups)? 📧 robert@ynteractive.com 🔗 Robert Breen 🌐 ynteractive.com

Overview: AI-Powered Interview Scheduling & Reminders This workflow automates the end-to-end process of scheduling technical or behavioral interviews. It captures interview data via Webhook, creates a Google Calendar event with an integrated Google Meet link, generates a personalized, professional reminder email using AI (GPT-4.1-mini), and automatically sends it via Gmail exactly 24 hours before the interview. Setup Instructions To implement this workflow, follow these steps: Webhook: Copy the Production URL and configure it in your Recrutei ATS to send interview JSON data. Google Calendar: Connect your account. The node is pre-configured to generate a "hangoutsMeet" conference link. OpenAI: Requires a valid API Key. The AI acts as a Recruitment Assistant to draft a professional email body. Wait Node: Currently set to "1 day before" the interview. You can adjust this timing based on your communication policy. Gmail: Connect your recruiter or company account to perform the final delivery. Recrutei's API: Inserts your Recrutei token in the Authorization header.

Automated QuickBooks Payment Reminders with Dynamic Invoice Tables This workflow provides a powerful solution for businesses using QuickBooks Online to automate their payment reminder process. It solves the time-consuming and manual task of chasing late payments by creating a fully automated system that ensures every customer with an outstanding balance receives a timely, professional, and consolidated reminder email. The workflow periodically fetches all unpaid invoices from your QuickBooks account. Its core strength lies in its ability to group multiple outstanding invoices for a single customer into one email, presenting them in a clean, easy-to-read table. This improves clarity for your customers, reduces email clutter, and significantly increases the likelihood of prompt payment. This template was crafted with care by the team at Prompt-Wizards to help you streamline your finances and build stronger customer relationships through smart automation. How the Workflow Operates Scheduler: The workflow initiates on a customizable schedule (e.g., every day at 9 AM). Get Unpaid Invoices: It fetches all invoices from your QuickBooks account that have an outstanding balance greater than zero and were created within a specified date range. Get Customer Wise Invoice list: This Code node intelligently processes the list of invoices and groups them by customer name, preparing the data for email generation. Invoice Template: This Code node dynamically generates a beautiful, responsive HTML email for each customer, complete with a personalized greeting, an invoice table, and the total amount due. Send Reminder Email: The final node sends the uniquely crafted email to the customer's billing address on file. Prerequisites Before you begin, please ensure you have the following: An active n8n instance. A QuickBooks Online account with API access. An email service (e.g., SMTP, Gmail, Outlook) connected to n8n as credentials. Step-by-Step Setup Guide Follow these instructions carefully to configure the workflow for your business in under 5 minutes. 1. Connect Your QuickBooks Account You must authenticate your QuickBooks account to allow n8n to fetch invoice data. Select the Get Unpaid Invoices node. In the Credentials section on the right, either select your existing QuickBooks account from the dropdown or click Create New to connect your account. (Optional): In the Options section of this node, you can adjust the TxnDate filter. It is pre-set to look at invoices from the last 90 days. You can change this date range to suit your needs. 2. Personalize the Email Template Personalize the email to match your brand and include your payment information. Open the Invoice Template node. Inside the code editor, find and replace these two placeholder values: Your Payment Link: On line 115, find href="https://your-payment-portal-link.com" and replace the placeholder URL with a link to your actual payment portal or website. Your Company Details: On line 120, find Your Company Name | ... and replace the placeholder text with your real company name and address in the email footer. 3. Configure Your Email Account You must connect the email account you want to send reminders from. Select the Send Reminder Email node. In the Credentials section, select your email account (e.g., Gmail, Outlook) or create a new connection. The To Address, Subject, and HTML fields are already configured with expressions to work automatically. No changes are needed here! 4. Activate the Workflow Open the Scheduler node to set the schedule for how often you want the workflow to run. Save the workflow using the button at the top. Click the Active toggle at the top right of the screen. Your automated payment reminder system is now live!!! For questions or to explore more custom solutions, visit us at Elegant Biztech or contact us at sales@elegantbiztech.com.

Daily Weather Reports with OpenWeather API, Google Sheets, and Gmail This workflow fetches real-time weather data from the OpenWeather API, stores it in a Google Sheet, formats it into a beautifully styled HTML report and emails it to recipients automatically every day at 10:00 AM. It helps teams track and monitor daily weather trends and optionally correlate them with energy production or field operations. Who’s it for? Renewable energy teams monitoring solar/wind energy output vs weather Facility or operations managers requiring daily climate updates Researchers or analysts logging environmental metrics Any team needing automated, daily weather reports by email How it works? The workflow begins with a Schedule Trigger set to run at 10:00 AM IST daily. It calls the OpenWeather API to fetch weather metrics for a predefined location. The data is then passed to a Google Sheets node named "Append Weather to Sheet", which stores all the key values into a structured spreadsheet. A Set or Function node generates a clean, styled HTML email using inline CSS and the weather values. Finally, a Gmail node sends this report to one or more recipients with a clear subject line and formatted body. How to set up? Create/Open your n8n instance (Cloud or Self-hosted). Connect the following credentials: Google Sheets (OAuth2) Gmail (OAuth2) Set your OpenWeather API key in the HTTP Request node (api.openweathermap.org). Replace latitude/longitude in the request URL as per your location. Link a Google Sheet and define the correct tab name and headers. Configure recipient email(s) in the Gmail node. Deploy the workflow and test. Requirements n8n account (self-hosted or cloud) OpenWeather API key (free or paid) Google account with access to: Google Sheets Gmail A valid Google Sheet created with the following headers (columns): Country Location Latitude Location Longitude Temperature (°C) Feels Like (°C) Min Temp (°C) Max Temp (°C) Humidity (%) Pressure (hPa) Sea Level (hPa) Ground Level (hPa) Visibility (m) Wind Speed (m/s) Wind Direction (°) Wind Gust (m/s) Cloudiness (%) Sunrise (UTC) Sunset (UTC) Date Time (UTC) How to customize? Change the scheduled time in the Schedule Trigger node. Modify the location coordinates in the OpenWeather API URL. Update the HTML template with different formatting or styling. Add a second email or sheet for energy output to correlate with weather. Extend the workflow with Slack, Notion, or Telegram alerts. Add‑ons Integrate with a solar energy API to track power production with weather. Post weather summaries to Notion, Slack or internal dashboards. Generate a visual chart in Google Sheets over time using the collected data. Trigger alerts when specific thresholds are exceeded (e.g., wind gust > 10 m/s). Use Case Examples Solar farm reporting**: Monitor daily weather impact on solar panel output. Logistics planning**: Notify teams of visibility or wind risks before dispatch. Site operations**: Send forecasts to maintenance or ground staff. Academic/weather logging**: Track atmospheric data over time. Common Troubleshooting | Issue | Possible Cause | Solution | | ------------------------------ | ---------------------------------------- | --------------------------------------------------------- | | Email not sent | Gmail credentials not connected properly | Reconnect Gmail account via n8n credential manager | | Weather data is missing fields | API response changed or API key invalid | Verify OpenWeather API key and URL format | | Google Sheet not updating | Incorrect spreadsheet ID or tab name | Double-check spreadsheet ID and sheet name in node | | HTML email renders incorrectly | Broken or missing tags in HTML | Test output HTML separately in browser/email preview tool | Need Help? If you need assistance setting up or customizing this workflow, feel free reach out. We’re here to help!

Who’s it for This automation template is designed for content creators, social media managers, and automation enthusiasts who want to automatically scrape X (Twitter) posts with images and publish them directly to a Telegram channel — without writing a single line of code. With this workflow, you can keep your Telegram community constantly updated with the latest tweets from any account. It collects, cleans, and shares content in a fully automated cycle. How It Works Trigger – Start scraping from a specific X (Twitter) account using its unique ID and username. Fetch Data – The workflow calls the Twitter API (or a scraping endpoint) to gather recent tweets. Format & Filter – Extracts key fields (author name, username, text, URL, creation date, images, video) and keeps only tweets containing text and at least one image. Remove Duplicates – Ensures no tweet is processed or posted twice. Save to Google Sheets – Stores cleaned tweet data for backup and future use. Clean Text – Removes unwanted links and hashtags for a polished message. Loop & Publish – Sends each tweet (text + image) to your Telegram channel. Delay – Waits 3 minutes between each post to prevent spamming. How to Use Enter the Twitter ID and username of the target account. Connect your Google Sheets account to store scraped tweets. Connect your Telegram bot and specify the channel for publication. Run the workflow — tweets will be automatically scraped, filtered, saved, and posted to Telegram. Requirements A valid Twitter API connection or alternative scraping endpoint. A Google Sheet to store tweet data. A Telegram Bot linked to your channel. n8n (or any compatible automation platform) to run the workflow. Need help Contact me for consulting and support: LinkedIn / YouTube

Title Japanese Document Translation Quality Checker with DeepL & Google Drive to Slack Who’s it for Localization teams, QA reviewers, and operations leads who need a fast, objective signal on Japanese document translation quality without manual checks. What it does / How it works This workflow watches a Google Drive folder for new Japanese documents, exports the text, translates JA→EN with DeepL, then back-translates EN→JA. It compares the original and back-translation to estimate a quality score and summarizes differences. A Google Docs report is generated, and a Slack message posts the score, difference count, and report link—so teams can triage quickly. How to set up Connect credentials for Google Drive, DeepL, and Slack. Point the Google Drive Trigger to your “incoming JP docs” folder. In the Workflow Configuration (Set) node, fill targetFolder (report destination) and slackChannel. Run once, then activate and drop a test doc. Requirements n8n (Cloud or self-hosted), Google Drive, DeepL, and Slack credentials; two Drive folders (incoming, reports). How to customize the workflow Tune the diff logic (character → token/line level, normalization rules), adjust score thresholds and Slack formatting, or add reviewer routing/Jira creation for low-score cases. Always avoid hardcoded secrets; keep user-editable variables in the Set node.

Nano Banana Pro AI Product Advertisement Generator via Telegram Who's It For E-commerce businesses needing quick product ads Social media marketers without design resources Small business owners creating promotional content Product photographers seeking automated enhancements What It Does Transforms basic product photos into professional advertisements using AI. Users send a product image with caption text via Telegram, and receive commercial-grade ads with studio lighting, premium backgrounds, and typography overlays. How It Works User sends product photo with caption to Telegram bot Image converted to base64 for AI processing Google Gemini analyzes image and extracts marketing text from caption AI generates detailed design enhancement instructions (400+ words) Nano Banana Pro creates 1-2 professional advertisement versions Enhanced images automatically sent back to user Requirements Telegram Bot API credentials (via BotFather) Google Gemini API key with nano-banana-pro-preview access n8n instance (self-hosted or cloud) Setup Instructions Create Telegram Bot Message BotFather on Telegram Send /newbot command and follow prompts Copy the API token Configure n8n Credentials Add Telegram Bot API token Add Google Gemini API key Import workflow JSON Update credential references Activate workflow Test the Workflow Send image with caption format: "Product Name | Tagline | Call to Action" Example: "Premium Sneakers | Mountain Edition | Shop Now" Key Features Original product remains 100% unchanged Text extracted only from user's caption (no AI-generated taglines) Professional design enhancements applied Studio-quality lighting and color grading Luxury background selection based on product category Typography overlays using caption text 30-60 second processing time Returns 1-2 advertisement variants Node Breakdown Telegram Trigger - Listens for messages with images Download Image File - Retrieves image from Telegram servers Image to Base64 - Converts image for AI processing AI Design Analysis - Gemini extracts caption text and generates design blueprint covering composition, lighting, backgrounds, color grading, effects, and typography Combine Image & Analysis - Merges image data with design instructions Prepare API Payload - Structures data for Nano Banana Pro API Generate Enhanced Image - Creates professional ad using AI Convert Base64 to Image - Converts first generated ad to file Convert Base64 to Image1 - Converts second ad variant (if available) Send Image - Returns enhanced ads to user via Telegram Customization Options Adjust Design Style Modify AI Design Analysis prompt to change lighting intensity, background preferences, color grading, or typography styles Change Caption Parsing Update extraction rules for different text elements or multi-language support Add Output Formats Request different aspect ratios (16:9 social media, 4:5 Instagram, 9:16 Stories) Error Handling Add fallback nodes to handle image generation failures Usage Analytics Insert database node to track requests and caption data Caption Examples "NIKE AIR MAX | Run Beyond Limits | Shop Now" "Himalayan Coffee Beans - Fresh from the Mountains - Order Today" "Luxury Smartwatch | Track Your Success | Available Now" Important Notes Product never altered, only enhanced visually Empty captions result in ads without text overlays Best with clear photos on simple backgrounds Monitor API quotas to avoid rate limits Processing time varies by API response speed