Workflow Templates

Send Post‑Interview Feedback Nudges from Google Sheets to Slack (with Email Fallback) This n8n workflow automates the process of sending post-interview feedback reminders to interviewers. It checks a Google Sheet daily for pending feedback entries and sends personalized Slack DMs or email nudges based on the availability of Slack IDs. It ensures consistent follow-ups and eliminates manual tracking. Who’s it for HR and Talent Acquisition teams Recruitment coordinators Engineering/Design/Product team leads conducting interviews Anyone managing interview feedback collection using Google Sheets and Slack How it works Trigger: The workflow starts every day at 6:00 PM using the Schedule Trigger. Fetch Data: It reads a Google Sheet with interview entries via the Google Sheets (Read Sheet) node. Check Feedback Submission: An IF node filters entries where feedback has not been marked as “Yes.” Slack Check: Another IF node checks if a valid Slack ID is present. If Slack ID exists: Sends a Slack DM reminder. If Slack ID is missing: Sends a fallback reminder via email using Gmail. Update Status: Updates the sheet to mark the reminder as sent, avoiding future duplicates. How to set up Prepare a Google Sheet with columns: candidate_email, interviewer_email, feedback_submitted, slack_id, reminder_sent. Connect your Google Sheets, Slack, and Gmail accounts in n8n. Set the Schedule Trigger to your preferred time (e.g., 6:00 PM). Map the correct columns in each node. Deploy and test the workflow. Requirements A working n8n instance. Google Sheets with structured feedback data. Slack workspace and bot token with DM permissions. Gmail account connected to n8n for fallback reminders. Interviewers listed with either Slack ID or valid email. How to customize Change the schedule (e.g., run hourly or on specific days). Customize Slack or Email message templates. Add conditional formatting for different interview types or roles. Integrate additional columns for logging timestamps or retries. Expand to MS Teams or other email providers. Add‑ons Google Sheets Timestamping**: Log the exact time when reminders were sent. Multi-language Reminder Support**: Based on interviewer’s preferred language. Feedback Form Auto-linking**: Embed Google Form links dynamically in messages. Notion or Airtable Integration**: Extend tracking to other platforms. Use Case Examples A recruiter managing 10+ interviews daily ensures feedback is collected within 24 hours. An engineering manager automates reminders for panelists to fill candidate scorecards. HR teams use it during hiring surges to eliminate feedback bottlenecks. Common Troubleshooting | Issue | Possible Cause | Solution | | ---------------------------- | --------------------------------- | ------------------------------------------------------- | | Reminders not sending | Schedule Trigger not firing | Check cron expression or timezone settings | | Slack messages not delivered | Slack ID missing or invalid | Ensure Slack IDs are mapped correctly in the Sheet | | Emails not sent | Gmail node not authorized | Reconnect Gmail credentials in n8n | | Entries repeatedly reminded | Sheet not updating after reminder | Confirm Update node is marking reminder_sent as “Yes” | | Slack bot errors | Insufficient permissions | Ensure bot has permission to send DMs | Need Help? Need a hand setting this up or want to customize it further for your recruitment workflow? Just drop a message to our n8n automation team at WeblineIndia — we’re here to help streamline your hiring feedback process!

AWS IAM Access Key Rotation Reminder Automation Workflow Watch the demo video below: Who’s it for DevOps/SRE teams responsible for AWS account security. Security/compliance officers ensuring key rotation policies are followed. Any AWS account owner who wants automatic detection of stale access keys. How it works / What it does Weekly Scheduler — triggers the workflow on a recurring basis. Get Many Users — fetches all IAM users in the AWS account. Get User Access Key(s) — retrieves the access keys associated with each user. Filter Out Inactive Keys — removes keys that are not active (e.g., status Inactive). Access Key Older Than 365 Days — checks the key creation date and flags keys older than one year. Send Slack Message — notifies a Slack channel with details of the outdated key(s) for review and action. No Operation — safely ends the workflow if no keys match the condition. How to set up Configure the Weekly Scheduler to run at your desired cadence (e.g., every Monday). Use Get Many Users to list all IAM users. For each user, call ListAccessKeys (Get User Access Key(s)) to fetch their key metadata. Apply a filter to keep only keys with status Active. Add a condition to compare CreateDate against today - 365 days. Send results to Slack using the Slack Post Message node. Requirements n8n (latest version). AWS credential in n8n configured for us-east-1 (IAM requires signing with this region). IAM permissions: iam:ListUsers iam:ListAccessKeys Slack bot credentials with permission to post messages in the desired channel. How to customize the workflow Change threshold** — adjust the 365 days condition to 90, 180, or any other rotation policy. Escalation** — mention @security or create a Jira/Ticket when old keys are found. Logging** — push flagged results into a Google Sheet, database, or log management system for audit. Automation** — instead of only notifying, add a step to automatically deactivate keys older than the threshold (after approval). Multi-account support** — duplicate or loop across multiple AWS credentials if you manage several AWS accounts.

💰 Package Recommender with Sales Pipeline Tracking What It Does Automatically recommends the right service package based on budget, sends beautifully formatted proposal emails with case studies, logs everything to a sales pipeline tracker, and schedules your follow-up reminders. Converts inquiries into booked calls without manual proposal writing. How It Works Form Trigger → Lead submits budget and challenge details Log to Pipeline → All inquiry data saved to tracking sheet Budget Router → Directs to Basic ($0-3K), Standard ($3-6K), or Premium ($6K+) Set Package Variables → Loads appropriate features, pricing, case study Send Proposal Email → Gorgeous HTML email with personalized package details Update Pipeline → Marks "Package Sent" and sets follow-up date (+3 days) Calendar Reminder → Creates event in 3 days reminding you to follow up 🚀 SETUP INSTRUCTIONS Step 1: Create Sales Pipeline Sheet Create Google Sheet with tab "Package Inquiries" Add columns: Timestamp | Name | Email | Phone | Budget | Timeline | Challenge | Package Recommended | Package Price | Status | Date Sent | Follow-Up Date Update YOUR_GOOGLE_SHEET_ID in nodes 2, 7, and calendar description Step 2: Customize Package Details Edit nodes 4, 5, 6 (Set Package Details nodes) Update pricing, features, and case studies for your services Replace booking links with your actual Calendly/scheduling URLs Adjust package names if needed Step 3: Configure Email Template Edit node 7 email design/branding Update "Your Name" and signature Customize colors (currently: purple gradient, green CTA) Test email rendering across devices Step 4: Setup Calendar Integration Add Google Calendar OAuth2 credentials Verify follow-up timing (currently +3 days) Customize reminder description with your workflow Update Google Sheet link in calendar event

Transform your lead qualification process with automated AI-powered phone calls triggered directly from Salesforce lead creation. What this workflow does: Webhook Trigger: Receives new lead data from Salesforce Automated Calling: Initiates phone calls via Retell AI Smart Monitoring: Polls call status until completion AI Analysis: Uses OpenAI to analyze call transcripts Salesforce Integration: Creates follow-up tasks with insights Perfect for: Sales teams wanting to qualify leads faster Companies using Salesforce CRM Organizations looking to automate initial prospect outreach Teams wanting AI-powered call analysis You'll need: Salesforce org with lead creation triggers Retell AI account and agent setup OpenAI API access Basic n8n workflow knowledge Setup time: ~15 minutes Author: Sri Kolagani Template Type: Free

There's a clear need for an easier way to manage attendee photos from live events, as current processes for collecting, sharing, and categorizing them are inefficient. n8n can indeed help to solve this challenge by providing the data input interface via its forms and orchestrate AI-powered classification of images using AI nodes. However, in some cases - say you run regular events or with high attendee counts - the volume of photos may result in unsustainably high inference fees (token usage based billing) which could make the project unviable. To work around this, Featherless.ai is an AI/LLM inference service which is subscription-based and provides unlimited tokens instead. This means costs are essentially capped for AI usage offering greater control and confidence on AI project budgets. Check out the final result here: https://docs.google.com/spreadsheets/d/1TpXQyhUq6tB8MLJ3maeWwswjut9wERZ8pSk_3kKhc58/edit?usp=sharing How it works A form trigger is used share a form interface to guests to upload their photos from their device. The photos are in one branch, are optimised in size before sending to a vision-capable LLM to classify and categorise against a set list of tags. The model inference service is provided by Featherless and takes advantage of their unlimited token usage subscription plan. The photos in another branch are copied into Google Drive for later reference. Once both branches are complete, the classification results and Google Drive link are appended to a Google Sheets table allowing for quick sorting and filtering of all photos. How to use Use this workflow to gain an incredible productivity boost for social media work. When all photos are organised and filter-ready, editors spend a fraction of the time to get community posts ready and delivered. Sharing the completed Google sheet with attendees helps them to better share memories within their own social circles. Requirements FeatherLess.ai) account for Open Source Multimodal LLMs and unlimited token usage. Google Drive for file storage Google Sheet for organising photos into categories Customising this workflow Feel free to refine the form with custom styles to match your branding. Swap out Google services with equivalents to match your own environment. eg. Sharepoint and Excel.

WhatsApp Micro-CRM with Baserow & WasenderAPI Struggling to manage WhatsApp client communications? This n8n workflow isn't just automation; it's your centralized CRM solution for small businesses and freelancers. How it works Capture Every Message:** Integrates WhatsApp messages directly via WasenderAPI. Effortless Contact Management:** Automates contact data standardization and intelligently manages records (creating new or updating existing profiles). Rich Client Profiles:** Retrieves profile pictures and decrypts image media, giving you full context. Unified Data Hub:** Centralizes all conversations and media in Baserow, no more scattered interactions. Setup Steps Setup is incredibly fast; you can deploy this in under 15 minutes. Here's what you'll do: Link WasenderAPI:** Connect your WasenderAPI webhooks directly to n8n. Set up Baserow:** Duplicate our pre-built 'Contacts' (link) and 'Messages' (link) Baserow table templates. Secure Your Data:** Input your API credentials (WasenderAPI and Baserow) directly into n8n. Every single step is fully detailed in the workflow's sticky notes – we've made it foolproof. Requirements What do you need to get started? An active n8n instance (self-hosted or cloud). A WasenderAPI.com subscription or trial. A Baserow account. Note: Keep the flow layout as is! This will ensure that the flow is running in the correct order.

How it works This workflow captures new leads from Typeform, instantly checks if their budget is above $5,000, and prioritizes them for faster sales follow-up. High-budget leads are enriched in HubSpot as contacts with detailed properties, and a priority task is created for the sales team. Leads are then routed based on their source (Facebook or SurveyMonkey), logged into Google Sheets for marketing or campaign tracking, and finally, a Slack notification is sent to alert the team in real time. Step-by-step Capture & Qualify Leads The workflow triggers on new Typeform submissions. It evaluates the budget field to identify high-priority leads (>$5,000). CRM Enrichment High-priority leads are automatically created or updated as contacts in HubSpot. A priority follow-up task is logged in HubSpot with the lead’s budget details. Source-Based Routing If the lead comes from Facebook or SurveyMonkey, their details are logged in a Google Sheet. This ensures marketing and campaign teams can analyze and track leads separately. Team Notifications Once logged, the workflow sends a Slack message to the sales/marketing channel. The message includes the lead’s name, email, phone, budget, and source, ensuring instant visibility for follow-up. Why use this? Automatically qualifies high-value leads based on budget. Syncs lead details seamlessly with HubSpot CRM. Routes leads by source for better campaign tracking. Keeps sales and marketing teams aligned with real-time Slack alerts. Cuts down manual effort, ensuring faster response times and higher conversion rates.

This workflow provides a powerful way to automatically document and maintain an inventory of all your n8n workflows in a Google Sheet. By running on a schedule or manually, it fetches details about every workflow on your instance, processes the key information, and then populates a spreadsheet. This creates a centralized, up-to-date dashboard for auditing, monitoring, and understanding your automation landscape. Who is this for? This workflow is ideal for n8n administrators, developers, and teams who manage multiple workflows. If you need a clear and simple way to track all your automations, their components, and their statuses without manually checking each one, this template is for you. It's particularly useful for maintaining technical documentation, auditing node usage across your instance, and quickly finding specific workflows. What problem is this workflow solving? As the number of workflows on an n8n instance grows, it becomes challenging to keep track of them all. Questions like "Which workflows use the HubSpot node?", "Which workflows are inactive?", or "When was this workflow last updated?" become difficult to answer. This workflow solves that problem by creating a single source of truth in a Google Sheet. It automates the process of cataloging your workflows, saving you time and ensuring your documentation is always current. What this workflow does Triggers Execution: The workflow can be initiated either on a set schedule (via the Scheduled Start node) or manually (via the Manual Start node). Fetches All Workflows: The Get All Workflows node connects to your n8n instance via the API to retrieve a complete list of your workflows and their associated data. Processes Workflows Individually: The Loop Through Each Workflow node iterates through each retrieved workflow one by one so they can be processed individually. Extracts Key Information: The Extract Workflow Details node uses custom code to process the data for each workflow, extracting essential details like its name, ID, tags, and a unique list of all node types it contains. Updates Google Sheet: The Add/Update Row in Google Sheet node then takes this information and appends or updates a row in your designated spreadsheet, using the workflow ID as a unique key to prevent duplicates. Waits and Repeats: The Pause to Avoid Rate Limits node adds a short delay to prevent issues with API limits before the loop continues to the next workflow. Setup Configure Get All Workflows Node: Select the Get All Workflows node. In the 'Credentials' section, provide your n8n API credentials to allow the workflow to access your instance's data. Prepare Your Google Sheet: Create a new Google Sheet. Set up the following headers in the first row: id, title, link, tags, nodes, CreatedAt, UpdatedAt, Active, Archived. Configure Add/Update Row in Google Sheet Node: Select the Add/Update Row in Google Sheet node. Authenticate your Google account in the 'Credentials' section. In the 'Document ID' field, enter the ID of your Google Sheet. You can find this in the sheet's URL (e.g., .../spreadsheets/d/THIS_IS_THE_ID/edit). Select your sheet from the 'Sheet Name' dropdown. Under 'Columns', ensure the id field is set as the 'Matching Columns' value. This is crucial for updating existing rows correctly. Activate the Workflow: Choose your preferred trigger. You can enable the Schedule Trigger to run the sync automatically at regular intervals. Save and activate the workflow. How to customize this workflow to your needs Track Different Data**: You can modify the Extract Workflow Details node to extract other pieces of information from the workflow JSON. For example, you could parse the settings object or count the total number of nodes. Remember to add a corresponding column in your Google Sheet and map it in the Google Sheets node. Add Notifications**: Add a notification node (like Slack, Discord, or Email) after the Loop Through Each Workflow node (in the second output) to be alerted when the sync is complete or if an error occurs. Filter Workflows**: You can add an IF node after the Loop Through Each Workflow node to filter which workflows get added to the sheet. For instance, you could choose to only log active workflows ({{ $('Loop Through Each Workflow').item.json.active }} is true) or workflows containing a specific tag. Adjust Wait Time**: The Pause to Avoid Rate Limits node is set to pause between each entry. You can adjust this time or remove it entirely if you have a small number of workflows and are not concerned about hitting API rate limits.

Customer Feedback Automation Workflow with Webhook, OpenAI, Jira & Slack This workflow collects customer feedback from a webhook, validates the incoming data, analyzes the sentiment using OpenAI and creates Jira tasks for negative or feature-request feedback. It also generates an automated weekly summary using OpenAI and delivers it to Slack. It helps teams stay informed, skip manual reviews and act quickly on customer issues. Quick Start – Implementation Steps Set up the Webhook URL in your application to send customer feedback. Configure Slack, Jira and OpenAI credentials in n8n. Adjust sentiment rules or Jira fields if needed. Activate the workflow — you’re ready to collect and process feedback automatically. What It Does This workflow automates the entire lifecycle of customer feedback handling. When someone submits feedback, the system checks if the required information (feedback text and sentiment) is present. If the payload is invalid or incomplete, the team immediately receives a Slack notification to take action. If the feedback is valid, OpenAI analyzes the content and identifies the sentiment as positive, negative, neutral or a feature suggestion. Based on this result, the system automatically creates a Jira issue for negative feedback or feature requests, ensuring nothing important is missed. Alongside real-time processing, the workflow also compiles a weekly summary. Every week, it gathers all Jira issues created through feedback and sends them to OpenAI for summarization. The summary is then posted to Slack so the team gets a clean, easy-to-read review of customer sentiment trends. Who’s It For This workflow is ideal for: Customer support teams Product managers QA and development teams Companies collecting user feedback Businesses wanting automated sentiment analysis and reporting Requirements to Use This Workflow To fully use this workflow, you need: An n8n instance (self-hosted or cloud) A Webhook endpoint to receive customer feedback A Slack workspace with API access A Jira Software Cloud account An OpenAI API key with access to GPT-4.1 or similar Basic understanding of JSON payloads How It Works Collect Feedback – Receives customer data through an n8n webhook. Validate Payload – Checks required fields; bad input triggers Slack alerts. Determine Sentiment – Sends feedback text to OpenAI for sentiment classification. Conditional Routing – Negative or feature-request items move forward; others are ignored. Create Jira Task – Automatically logs an issue for follow-up. Weekly Summary – A scheduled trigger collects all Jira issues created during the week. Generate Report – Sends all issues to OpenAI for a clean weekly summary. Delivered to Slack – The summary is posted for the team to review. Setup Steps Import the workflow JSON file into n8n. Configure your credentials: Slack Jira OpenAI Update the webhook URL in your application. Edit Jira project ID or fields if required. Customize Slack channel IDs. Enable the schedule trigger (weekly summary). Activate the workflow. How To Customize Nodes Customize Sentiment Rules Modify the IF node that checks OpenAI output: Add new sentiment labels (e.g., “bug”, “urgent”) Adjust rules for what should create a Jira issue Customize Jira Task Fields In the Create Jira Task node, you can change: Project ID Issue type Summary and description templates Labels or assignees Customize Slack Messages Update Slack node text blocks to: Format alerts Add more details Send messages to different channels Add-Ons (Optional Enhancements) You can extend this workflow with: Email notifications for high-priority feedback Auto-reply emails to customers acknowledging their feedback Google Sheets logging for historical data Dashboard creation using Airtable or Notion Multi-language sentiment detection Auto-tagging Jira issues with sentiment categories Use Case Examples Customer Complaint Handling – Automatically detect negative feedback and create a Jira issue. Feature Request Collection – Route suggestions to the product backlog. Weekly Sentiment Reporting – Keep managers updated on trends. Slack Alerts for Bad Payloads – Notify the team when someone sends incomplete or incorrect feedback. Automated Feedback Triage – Assign tasks to specific Jira users based on sentiment or keywords. You can extend to many more such similar use cases. Troubleshooting Guide | Issue | Possible Cause | Solution | |-----------------------------|-----------------------------------------------|---------------------------------------------------| | Slack alert not sent | Wrong API credentials or channel ID | Check Slack credentials and update channel ID | | Jira issue not created | Incorrect project ID or issue type | Verify Jira configuration in n8n | | OpenAI sentiment not reading| Wrong JSON path in IF node | Re-check $json.output[0].content[0].text | | Weekly summary not generated| Schedule trigger disabled | Enable the Schedule Trigger node | | Webhook not receiving data | Application not pointing to correct URL | Verify webhook URL in your app | Need Any Help? If you need any help setting up this workflow, troubleshooting or adding custom features, our n8n experts at WeblineIndia is always here to support. We can help you automate more processes, integrate external systems or build complete workflow solutions tailored to your business.

Automated multilingual article publishing from RSS feeds to WordPress using ACF Instalations Instructions Youtube Instalation Instructions # Who’s it for This workflow is built for news publishers, media organizations, and content aggregators who need to automatically: pull articles from RSS feeds rewrite them into original text translate them into multiple languages generate a featured image publish everything directly to WordPress. It is ideal for multilingual news portals, editorial teams with limited resources, and businesses that want to automate high-volume content production. How it works The workflow monitors a selected RSS feed at regular intervals and retrieves new article links. It scrapes each article’s HTML and uses AI to extract structured text: title full content and a short summary. The text is then rewritten into an original article tailored to your target audience’s language and country context. Next, the workflow translates the rewritten article into any number of additional languages while preserving the formatting. It also generates a unique AI-based featured image, uploads it to WordPress, assembles multilingual ACF fields, and publishes the final post with the correct metadata. How to set up Insert your RSS feed URL, add your OpenAI and Replicate API keys, configure your WordPress API credential, and ensure the ACF fields on your site match the workflow’s naming structure. Requirements WordPress with REST API enabled ACF WP Plugin installed OpenAI API key Replicate API key Firebase API Key How to customize the workflow Adjust the RSS source, modify the default language and list of translated languages, change the rewriting style or country context, refine the image generation prompt, or remap ACF fields to match your WordPress layout.

🚀 Google Drive Image Enhancement with Gemini nano banana This workflow automates image enhancement by integrating Google Drive with Google Gemini. It fetches unprocessed images from a source folder, applies AI-driven transformations based on a customizable prompt (e.g., clean and realistic product backgrounds), and uploads the enhanced results into a destination folder—streamlining e-commerce catalog preparation or creative pipelines. 🔑 Key Features Customizable Prompt Node** → Easily adjust the style/instructions for Gemini (e.g., backgrounds, lighting, focus). Google Drive Integration** → Automatically fetches images from a source folder and uploads results to a target folder. AI Processing via Gemini** → Converts original images to Base64, sends them with the prompt to Gemini, and returns enhanced versions. Image Filtering** → Processes only files whose mimeType contains "image". Loop Handling** → Iterates over all images in the source folder until all are processed. ⚙️ Setup Instructions Configure Prompt Open the promt node. Replace the text with your desired Gemini instructions (e.g., "Add a clean, realistic background for baby products"). Set Google Drive Folders In origin_folder → set Search Query to the name of the source folder (with unprocessed images). In destination_folder → set Search Query to the name of the target folder (to save results). Credentials Provide valid Google Drive OAuth2 credentials for both Drive nodes. Provide a Google Gemini API credential for the banana-request node. Run the Workflow Trigger from the init node. Workflow will download → convert → send to Gemini → reconvert → upload results automatically. 🛠 Customization Guidance Modify the prompt text to change how Gemini processes the images (background, style, product focus). Swap Search Query for folder IDs in Drive nodes if you need more precise targeting. Extend the workflow by chaining post-processing (e.g., watermarking, resizing, or tagging metadata). © 2025 Innovatex • Automation & AI Solutions • innovatexiot.carrd.co • LinkedIn

This workflow is a simple example of using n8n as an AI chat interface into Appian. It connects a local LLM, persistent memory, and API tools to demonstrate how an agent can interact with Appian tasks. What this workflow does Chat interface: Accepts user input through a webhook or chat trigger Local LLM (Ollama): Runs on qwen2.5:7b with an 8k context window Conversation memory: Stores chat history in Postgres, keyed by sessionId AI Agent node: Handles reasoning, follows system rules (helpful assistant persona, date formatting, iteration limits), and decides when to call tools Appian integration tools: List Tasks: Fetches a user’s tasks from Appian Create Task: Submits data for a new task in Appian (title, description, hours, cost) How it works A user sends a chat message The workflow normalizes fields such as text, username, and sessionId The AI Agent processes the message using Ollama and Postgres memory If the user asks about tasks, the agent calls the Appian APIs The result, either a task list or confirmation of a new task, is returned through the webhook Why this is useful Demonstrates how to build a basic Appian connector in n8n with an AI chat front end Shows how an LLM can decide when to call Appian APIs to list or create tasks Provides a pattern that can be extended with more Appian endpoints, different models, or custom system prompts