Workflow Templates

What this does This automation will create tables in your Airtable base and send Webflow form submissions as records in those tables. It keeps track of your Webflow forms with a Form Index table to ensure that form content does not get sent to the wrong table if you have Webflow forms with identical names. This is useful for Enhancing your Webflow form submission management. By sending structured data to your Airtable base you can do more with your Webflow forms. Usage guide Full written and video guide This automation is made to be as low effort as possible to start enhancing your Webflow forms. Simply create credentials for Webflow and a Personal Access Token for your Airtable base and connect them to the relevant nodes. The guide demonstrates a realworld example using a Webflow template and breaksdown the flow and logic for all the nodes.

Workflow Description* Automate your candidate interview pipeline with precision. This powerful integration pulls booking data from Cal.com, extracts interview details (name, email, date & time), and syncs them directly into your Google Sheets tracker. It matches applicants using email, formats the date in the Asia/Riyadh timezone, and appends only relevant entries. But it doesn’t stop there — it cleans your sheet automatically by removing unmatched or empty records, ensuring your data stays clean, reliable, and ready for HR decisions. What it does: Fetches interview bookings from Cal.com Converts time to readable format (e.g. 30 June, 09:00 AM) Matches booking emails with existing applicant records Auto-updates interview date in your sheet Detects and deletes irrelevant or blank entries Use Cases: Resume screening workflows that require automated interview sync HR dashboards needing real-time calendar updates Applicant pipelines where only valid interviews should remain Ideal for: Recruiters • HR teams • Automation architects • Remote hiring pipelines

Use case If you have a form where potential leads reach out, then you probably want to analyze those leads and send a notification if certain requirements are met, e.g. employee number is high enough. MadKudu is built exactly to solve this problem. We use it along with Hunter and Gmail to get an email alert for high quality leads. How to setup Add you MadKudu, Hunter, and Gmail credentials Set the email to send to Click the Test Workflow button, enter your email and check your email Activate the workflow and use the form trigger production URL to collect your leads in a smart way How to adjust this template You may want to raise or lower the threshold for your leads, as you see fit.

This n8n workflow provides a comprehensive automation solution for processing email attachments, specifically targeting enhanced security protocols for organizations that use platforms like Outlook. It starts with the IMAP node, which is set to ingest emails and identify those with .eml attachments. Once an email with an attachment is ingested, the workflow progresses to a conditional operation where it checks for the presence of attachments. If an attachment is found, the binary data is moved and converted to JSON format, preparing it for further analysis. This meticulous approach to detecting attachments is crucial for maintaining a robust security posture, allowing for the proactive identification and handling of potentially malicious content. In the subsequent stage, the workflow leverages the capabilities of Sublime Security by analyzing the email attachment. The binary file is scrutinized for threats, and upon detection, the information is split to matched and unmatched data. This process not only speeds up the threat detection mechanism but also ensures compatibility with other systems, such as Slack, resulting in a smooth and efficient workflow. This automation emphasizes operational efficiency with minimal user involvement, enhancing the organization's defense against cyber threats. The final phase of the workflow involves preparing the output for a Slack report. Whether a threat is detected or not, n8n ensures that stakeholders are immediately informed by dispatching comprehensive reports or notifications to Slack channels. This promotes a culture of transparency and prompt action within the team.

🚫 Email Unsubscribe Handler for Outlook Description This n8n workflow automatically scans recent email replies from your Outlook inbox and identifies unsubscribe requests. If a contact replies with any variation of "unsubscribe" within the past 7 days, the system performs two key actions: Saves the contact’s email address in a BigQuery unsubscribes table (for compliance and tracking). Deletes that contact from the active leads table in BigQuery (to stop future outreach). This flow can be triggered on a schedule (e.g. every 4 hours) or run manually as needed. Key Features 📥 Email Parsing from Outlook: Automatically monitors for replies that contain unsubscribe language. 🧠 Smart Filtering: Captures unsubscribes based on message content, not just subject lines. 🔄 BigQuery Integration: Logs unsubscribed emails and removes them from your leads dataset. 🤝 Connect with Me Description I’m Robert Breen, founder of Ynteractive — a consulting firm that helps businesses automate operations using n8n, AI agents, and custom workflows. I’ve helped clients build everything from intelligent chatbots to complex sales automations, and I’m always excited to collaborate or support new projects. If you found this workflow helpful or want to talk through an idea, I’d love to hear from you. Links 🌐 Website: https://www.ynteractive.com 📺 YouTube: @ynteractivetraining 💼 LinkedIn: https://www.linkedin.com/in/robert-breen 📬 Email: rbreen@ynteractive.com

This guide details the setup and functionality of an automated workflow designed to monitor the health, uptime, and SLA compliance of travel supplier APIs, specifically the Amadeus Flight API and Booking.com Hotel API. The workflow runs every 10 minutes, processes health and SLA data, and sends alerts or logs based on the status. What It Monitors API Health**: UP/DOWN status with health indicators. Uptime Tracking**: Real-time availability percentage. SLA Compliance**: Automatic breach detection and alerts. Performance Rating**: Classified as EXCELLENT, GOOD, AVERAGE, or POOR. Features Runs every 10 minutes automatically. Monitors the Amadeus Flight API with a 99.5% SLA target. Monitors the Booking.com Hotel API with a 99.0% SLA target. Smart Alerts that notify via WhatsApp only on SLA breaches. Logging of results for both breaches and normal status. Workflow Steps Monitor Schedule**: Triggers the workflow every 10 minutes automatically. Amadeus Flight API**: Tests the Amadeus Flight API (GET: https://api.amadeus.com) simultaneously. Booking Hotel API**: Tests the Booking.com Hotel API (GET: https://distribution-xml.booking.com) simultaneously. Calculate Health & SLA**: Processes health, uptime, and SLA data. Alert Check**: Routes to appropriate responses based on breach status. SLA Breach Alert**: Sends an alert with throwError if an SLA breach occurs. Normal Status Log**: Records results with throwError for healthy status. Send Message**: Sends a WhatsApp message for breach alerts. How to Use Copy the JSON configuration of the workflow. Import it into your n8n workspace. Activate the workflow. Monitor results in the execution logs and WhatsApp notifications. The workflow will automatically start tracking your travel suppliers and alert you via WhatsApp only when SLA thresholds are breached. Please double-check responses to ensure accuracy. Requirements n8n account and instance setup. API credentials for Amadeus Flight API (e.g., https://api.amadeus.com). API credentials for Booking.com Hotel API (e.g., https://distribution-xml.booking.com). WhatsApp integration for sending alerts. Customizing this Workflow Adjust the Monitor Schedule interval to change the frequency (e.g., every 5 or 15 minutes). Modify SLA targets in the Calculate Health & SLA node to align with your service agreements (e.g., 99.9% for Amadeus). Update API endpoints or credentials in the Amadeus Flight API and Booking Hotel API nodes for different suppliers. Customize the Send Message node to integrate with other messaging platforms (e.g., Slack, email). Enhance the Normal Status Log to include additional metrics or export logs to a database.

For every release on GitHub this workflow will create an issue on GitLab. Copy workflow to your n8n Fill in missing fields (credentials & repo names) Based on Cron node to be able to track github repos you're not a member of (as you won't be able to create a webhook). If you do own the repo, you could replace Cron & GH node with a GitHub Trigger.

Description Boost your productivity and keep your Asana workspace clutter-free with this n8n workflow. It automatically scans for tasks whose due dates have passed and reschedules them to the current date, ensuring no important to-dos slip through the cracks. Additionally, any completed tasks in Asana with an overdue date are removed, maintaining a clear, organized task list. Key Benefits Streamline Task Management**: No more manual updates—let the workflow reschedule overdue tasks for you. Optimize Workspace Organization**: Eliminate finished tasks to focus on active priorities and reduce clutter. Save Time and Effort**: Automate repetitive maintenance, freeing you to concentrate on what truly matters. Configuration Steps Add your Asana credentials Schedule the workflow to run at desired intervals (e.g., daily or weekly). Select your Workspace Name and your Assignee Name (user) in the Get user tasks node (Optional) Tailor filtering conditions to match your preferred due-date rules and removal criteria. Activate the workflow and watch your Asana workspace stay up to date and clutter-free.

Task: Conditional filtering and branching items Why: Filtering and branching data based on conditions allows you to build complex workflows that work with more than one data flow scenario Main use cases: Filter out data that is not relevant for the rest of the workflow Split data to several branches of the workflow, where we want the data to be treated differently in the rest of the workflow

Use case If you have a form where potential leads reach out, then you probably want to analyze those leads and send a notification if certain requirements are met, e.g. employee number is high enough. MadKudu is built exactly to solve this problem. We use it along with Hunter to alert on Slack for high quality leads. How to setup Add you MadKudu, Hunter, and Slack credentials Set the Slack channel Click the Test Workflow button, enter your email and check the Slack channel Activate the workflow and use the form trigger production URL to collect your leads in a smart way How to adjust this template You may want to raise or lower the threshold for your leads, as you see fit.

Make your n8n instance faster, cleaner, and more efficient by deleting old workflow executions — while keeping only the most recent ones you actually need. Whether you're using n8n Cloud or self-hosted, this lightweight workflow helps reduce database/storage usage and improves UI responsiveness, using only official n8n nodes. 🔍 Description Automatically clean up old executions in your n8n instance using only official nodes — no external database queries required. Whether you're on the Cloud version or running self-hosted, this workflow helps you optimize performance and keep your instance tidy by maintaining only the most recent executions per workflow. Ideal for users managing dozens or hundreds of workflows, this solution reduces storage usage and improves the responsiveness of the n8n UI, especially in environments where execution logs can accumulate quickly. ✅ What It Does Retrieves up to 250 recent executions across all workflows Groups executions by workflow Keeps only the most recent N executions per workflow (value is configurable) Deletes all older executions (regardless of their status: success, error, etc.) Works entirely with native n8n nodes — no external database access required Optionally: set the number of executions to keep as 0 to delete all past executions from your instance in a single run 🛠️ How to Set Up 🔑 Create a Personal API Key in your n8n instance: Go to Settings → API Keys → Create a new key 🔧 Create a new n8n API Credential (used by both nodes): In your n8n credentials panel: Name: anything you like (e.g., “Internal API Access”) API Key: paste the Personal API Key you just created Base URL: your full n8n instance URL with the /api/v1 path, e.g. https://your-n8n-instance.com/api/v1 ✅ Use this credential in both: The Get Many Executions node (to fetch recent executions) The Delete Many Executions node (to remove outdated executions) 🧩 In the “Set Executions to Keep” node: Edit the variable executionsToKeep and set the number of most recent executions to retain per workflow (e.g. 10) Tip: Set it to 0 to delete all executions 📦 Note: The “Get Many Executions” node will retrieve up to 250 executions per run — this is the maximum allowed by the n8n API. 🧠 No further setup is required — the filtering and grouping logic is handled inside the Code Node automatically. 🧪 Included Nodes Overview 🕒 Schedule Trigger → Set to run daily, weekly, etc. 📥 Get Many Executions → Fetches past executions via n8n API 🛠️ Set Executions to Keep → Set how many recent ones to keep 🧠 Code Node → Filters out executions to delete per workflow 🗑️ Delete Executions → Deletes outdated executions 💡 Why Use This? Reduce clutter and improve performance in your n8n instance Maintain execution logs only when they’re useful Avoid bloating your storage or database with obsolete data Compatible with both n8n Cloud and self-hosted setups Uses only official, supported n8n nodes — no SQL, no extra setup 🔒 This workflow modifies and deletes execution data. Always review and test it first on a staging instance or on a limited set of workflows before using it in production.

This template is a simple AI Agent that acts as a Google Calendar Assistant. It is designed for beginners to have their "first AI Agent" performing common tasks and to help them understand how it works. For new users of n8n, AI Agents, and OpenAI: This template involves using an OpenAI API Key. If you are new to AI Agents, make sure to research and understand key concepts such as: "Tokens"** (used for API requests), "Tool calling"** (how the AI interacts with external tools), OpenAI's usage costs** (how you will be billed for API usage). Functionality It has two main functionalities: Create events** in a calendar Retrieve events** from a calendar How you can use it Everything is explained with sticky notes in the workflow. It is ready-to-use: all you need to do is connect your OpenAI credentials, and you can start using the workflow.