Workflow Templates

Short Description Automatically exports customer records from NetSuite and syncs them into Salesforce — creating or updating Accounts and Contacts depending on whether the NetSuite record represents a company or an individual. Who is this for / Use case This template is designed for businesses and integration developers who: Use NetSuite as their ERP or CRM system. Need to automatically sync customer data (both companies and individuals) into Salesforce. Want a reliable, scalable solution that supports pagination and upserts. Prefer a ready-to-use, easily customizable workflow built on n8n. How it works Initialize pagination offset. Fetch customer records from NetSuite in batches via REST API. Split the retrieved array into individual items. Check record type — company or individual. Upsert to Salesforce: For companies → creates/updates Account records. For individuals → creates/updates both Account and Contact (linked to the Account). Merge results from both branches. Update pagination offset for the next batch. Repeat until all records are processed, then end the workflow. Setup / Configuration Import the workflow into your n8n instance. Set your NetSuite and Salesforce credentials. Ensure your Salesforce Account/Contact objects have a matching External ID field. (Optional) Adjust mapping fields or filters to your data needs. Execute manually or trigger on a schedule (e.g., daily sync).

🗂️ Auto-Create Airtable CRM Records for Zoom Attendees This workflow automatically logs every Zoom meeting attendee into an Airtable CRM — capturing their details for sales follow-up, reporting, or onboarding. ⚙️ How It Works Zoom Webhook → Captures participant join event. Normalize Data → Extracts attendee name, email, join/leave times. Airtable → Saves/updates record with meeting + contact info. 🛠️ Setup Steps 1. Zoom Create a Zoom App with meeting.participant_joined event. Paste workflow webhook URL. 2. Airtable Create a base called CRM. Table: Attendees. Columns: Meeting ID Topic Name Email Join Time Leave Time Duration Tag 3. n8n Replace YOUR_AIRTABLE_BASE_ID + YOUR_AIRTABLE_TABLE_ID in the workflow. Connect Airtable API key. 📊 Example Airtable Row | Meeting ID | Topic | Name | Email | Join Time | Duration | Tag | |------------|--------------|----------|--------------------|----------------------|----------|----------| | 999-123-456 | Sales Demo | Sarah L. | sarah@email.com | 2025-08-30T10:02:00Z | 45 min | New Lead | ⚡ With this workflow, every Zoom attendee becomes a structured CRM record automatically.

This workflow allows you to create, update, and get an object from Bubble. Bubble node: This node will create a new object of the type Doc in Bubble. If you want to create an object with a different type, use that type instead. Bubble1 node: This node will update the object that we created using the previous node. Bubble2 node: This node will retrieve the information of the object that we created earlier.

Quick overview Host and deploy custom HTML lead forms for any CRM instantly with CustomJS. This workflow generates responsive Tailwind CSS webforms, hosts them on custom domains, and routes submissions via an n8n webhook directly into HubSpot, Salesforce, Pipedrive, or databases. How it works Trigger & Content Prep: The workflow triggers to compile your custom HTML form structure and any dynamic CRM fields or tracking tokens. Instant Deployment: The HTML (styled with Tailwind CSS) is sent to the CustomJS node, which instantly deploys and hosts the live page. Lead Capture: When a user submits the form, the data is securely sent to the built-in n8n Webhook node. CRM Syncing: n8n processes the payload and maps the fields directly into your preferred CRM, creating or updating contacts automatically. Setup Customize the Form: Open the CustomJS HTML template node and adjust the input fields to match your CRM properties (e.g., First Name, Email). Link the Webhook: Ensure the n8n Webhook URL is set as the submission action in your form HTML. Connect Your CRM: Add your CRM node (e.g., HubSpot, Pipedrive, or Airtable) directly after the Webhook node to automatically map and save incoming leads. Go Live: Run the workflow to host the form on CustomJS, and optionally connect your custom brand domain. Requirements A CustomJS account to host the static HTML page and manage domains. A CRM account (like HubSpot, Pipedrive, Salesforce) or a database connected to your n8n instance to store form submissions. Customization Tailwind & Alpine.js: The template includes a ready-to-use modern layout, but you can paste any custom HTML/CSS framework into the CustomJS node. Dynamic Content: You can inject dynamic data from previous n8n nodes directly into the HTML code before it gets deployed. Additional info Custom Domains: CustomJS allows you to mask the hosted form URL with your own branded domain (e.g., forms.yourcompany.com) with just a single click. Security: Since submissions go straight from the client browser to your private n8n webhook, no lead data is stored on third-party form servers.

Automated Email Verification for Google Sheets This n8n template demonstrates how to automatically validate email addresses from your Google Sheets using a reliable email verification API. Perfect for cleaning contact lists, validating leads, and ensuring email deliverability before marketing campaigns. Use cases are many: Lead qualification for sales teams, contact list cleaning for marketing, subscriber validation for newsletters, or CRM data hygiene maintenance! Good to know The rapid-email-verifier API is free for up to 1,000 verifications per month Each email verification typically takes less than 500ms to complete The workflow runs automatically every hour, checking for new entries Only processes emails that haven't been verified yet, preventing duplicate API calls How it works Monitor Google Sheets: The trigger watches your spreadsheet for new email entries every hour Smart Filtering: Only emails with empty "Email Verified" columns are processed to avoid duplicates Batch Processing: Emails are processed one by one to respect API rate limits and ensure reliability API Verification: Each email is sent to the rapid-email-verifier service which returns validation status Results Update: The original sheet is updated with verification results (valid/invalid/unknown) using the Serial Number as a match key The verification accuracy is consistently above 95% and shows excellent detection of invalid, disposable, and risky email addresses! How to use The Google Sheets trigger monitors your spreadsheet automatically, but you can also test manually Simply add new rows with email addresses to your connected Google Sheet Leave the "Email Verified" column empty for new entries The workflow will automatically process and update the verification status Technically, you can process unlimited emails, but consider API rate limits and costs for large batches. Requirements Google Sheets account** with a spreadsheet containing columns: SrNo, Name, Email, Email Verified Google Sheets credentials** configured in n8n for both trigger and update operations Internet connection** for API access (no additional API key required for rapid-email-verifier) Customising this workflow Email verification can be enhanced for many use-cases: Add webhook trigger** for real-time verification when leads are captured Connect to CRM systems** like HubSpot or Salesforce for direct integration Add email categorization** to separate personal vs business emails Include bounce detection** by connecting to your email service provider Set up notifications** to alert when invalid emails are detected in important lists This template is perfect for marketing managers, sales professionals, data analysts, and anyone managing contact databases who needs reliable email validation!

Quick Overview This workflow runs weekly (or manually) to pull HubSpot companies, search Coresignal job ads via Elasticsearch for customer support roles by company domain, maintain job snapshot and job tables in n8n Data Tables, and update HubSpot company properties with job-signal metrics. How it works Runs on a Monday 9am schedule (or manual start) and generates a unique run ID for the execution. Fetches all companies from HubSpot, removes duplicates, and keeps only companies that have a website domain. Batches company domains and queries Coresignal’s Elasticsearch job index for active customer-support-related job ads matching those domains. Stores the found job IDs as a “current snapshot” in an n8n Data Table and compares it to the previous snapshot to identify new and disappeared job ads. For newly found job IDs, fetches full job details from Coresignal and upserts them into a “job_data_table” Data Table, while updating the “previous snapshot” with the active IDs. For job IDs no longer present, deletes them from the snapshot and removes the corresponding rows from the job table. Aggregates active jobs per company domain (counts, recent-posting metrics, and a “top job” pick) into a “company_data” Data Table and compares it with the prior company list. Updates matching HubSpot company records to reflect new/updated/ended job-signal fields such as active listings, jobs in the last 7/30 days, and top job details. Setup Add HubSpot OAuth2 credentials and ensure your HubSpot companies have a populated website/domain property and the custom properties used for updates (for example job_active_listings_total, jobs_last_7_days, and top_job_url). Add Coresignal credentials and confirm your account supports the job Elasticsearch DSL search and job detail lookups. Create (or relink) the n8n Data Tables used by the workflow: previous snapshot, current snapshot, job_data_table, and company_data. Review and adjust the Coresignal Elasticsearch query terms (job titles and filters) to match the roles you want to track. Set the schedule trigger to your preferred cadence or use the manual trigger for ad-hoc runs.

How it works: This flow checks the user's Google calender of events from Sunday to Saturday of current week, to determine how many hours have been booked each day. If a day has over 6 hours booked, it blocks out the remaining work hours for dedicated focus time. The flow assumes 8 work hours per day. For example, if the Monday of this week has 6.5 hours booked (for meetings, tasks etc.), it automatically blocks off the remaining 1.5 hours for dedicated focus time, so external users can see and not book new events for those hours. Benefit: Prevents users from being overloaded with meetings and gives time for dedicated deep work/focus time. Set up steps: Update start time of the "Schedule Trigger," this is the time the flow will run daily. Note: the workflow assumes a 9AM-5PM work schedule so it's recommended to schedule the flow to trigger before 9AM. Update the credentials for the "Get Full Weeks Events" and "Create Focus Time Event" nodes. Use your Google credentials so the workflow can connect to your Google calendar.

Description Automatically track Stripe invoices and create Google Calendar reminders for upcoming due dates. This workflow ensures you never miss a payment deadline by running daily checks, filtering invoices due within the next 7 days, and adding them to your calendar with invoice details. ⏰💳📅 What This Template Does Runs daily at 8:00 AM using a scheduled trigger. ⏰ Fetches draft invoices from Stripe. 💳 Splits invoice data into individual records for processing. 🔎 Filters invoices due within the next 7 days. 📆 Prevents duplicates by checking against existing calendar events. 🔄 Creates Google Calendar events for valid invoices with details (ID, customer, amount). 📅 Key Benefits Automated invoice due date reminders with no manual effort. ⚡ Avoids duplicate entries in Google Calendar. 🛡️ Provides a clear overview of pending payments. 👀 Saves time for freelancers, agencies, and finance teams. ⏱️ Keeps all payment reminders in one central place. 📲 Features Daily schedule with cron expression (0 8 * * *). Stripe API integration to fetch draft invoices. Smart filtering: only invoices with due dates within 7 days are selected. Google Calendar integration to check existing events and avoid duplicates. Detailed calendar events with invoice ID, amount due, and customer email. Customizable reminders — add customer name, invoice link, or change times. Requirements n8n instance (cloud or self-hosted). Stripe API credentials with invoice read access. Google Calendar OAuth2 credentials with event write permissions. Access to the target Google Calendar (replace placeholder with your own). Target Audience Freelancers and solopreneurs managing invoices. 👩‍💻 Agencies tracking multiple client invoices. 🏢 Finance and accounting teams requiring automated reminders. 📊 Businesses wanting to automate payment follow-ups. 💼 Remote teams centralizing billing schedules. 🌍 Step-by-Step Setup Instructions Configure Stripe API credentials in n8n. Add Google Calendar OAuth2 credentials with access to your target calendar. Replace the placeholder calendar ID (your-calendar@gmail.com) with your actual calendar. Import this workflow into n8n. Test the workflow by creating a test draft invoice in Stripe with a due date in the next 7 days. Verify the Google Calendar event is created with the invoice details. Enable the workflow to run daily and enjoy hands-free invoice tracking. ✅

Send a templated outreach email to new leads in a Google Sheet on a daily schedule, then mark each lead as contacted so they won’t be emailed twice. Built with: Schedule Trigger → Google Sheets → Filter → Outlook Send Email → Google Sheets (append/update). Who’s it for Teams that collect leads in Sheets and want automatic, once-per-lead outreach Solo founders/consultants running simple top-of-funnel follow-ups Anyone prototyping CRM-lite flows in n8n How it works / What it does Schedule Trigger runs daily (e.g., 09:00). Get rows (Google Sheets) pulls leads from your sheet. Filter keeps only rows where Contacted is empty. Outlook – Send a message emails each remaining lead (to = {{$json.Email}}). Google Sheets (appendOrUpdate) writes back Contacted = Yes (match on Email) to prevent re-sending. How to set up 1) Google Sheets (OAuth2) In n8n → Credentials → New → Google Sheets (OAuth2), sign in and grant access. In Get rows: select your Lead Source sheet (e.g., “New Leads”). In Append/Update: select the sheet you want to mark as contacted (can be the same sheet or a CRM sheet). Make sure your sheet has at least: Email, Contacted (blank for new). 2) Outlook (Microsoft Graph) OAuth2 n8n Cloud (quick connect):** In Credentials → New → Microsoft Outlook OAuth2, choose Connect, sign in with your Microsoft account, and accept permissions. Self-hosted (Azure App Registration):** 1) Azure Portal → App registrations → New registration. 2) Add redirect URL: https://YOUR_N8N_URL/rest/oauth2-credential/callback. 3) API permissions (Delegated): offline_access, Mail.Send, User.Read. Grant admin consent if required. 4) Create a Client secret; copy Application (client) ID and Directory (tenant) ID. 5) In n8n, create Microsoft Outlook OAuth2 credential with those values and scopes: offline_access Mail.Send openid email profile. In the Send a message node, select that credential and keep To mapped to {{$json.Email}}. Customize Subject and Body to your brand (default provided). Requirements A Google Sheet of leads with an Email column (and an optional Contacted column). A Microsoft account with permission to send mail via Microsoft Graph (Outlook). How to customize the workflow Email content:** Edit subject/body (add variables like {{$json.FirstName}}). Send window:** Change Schedule Trigger time/interval. Idempotency:** Use the same sheet for read+write (match on Email) or separate source/CRM sheets. Logging:** Add a Sheet or Notion append step after send for an audit trail. Security & best practices No hardcoded secrets:* Always use *OAuth2 credentials** (Sheets & Outlook). Sanitize PII:* If publishing, *remove real spreadsheet IDs/URLs** and personal emails/phone numbers. Sticky notes are mandatory:* Add a *yellow sticky note** in the workflow with this description and a short setup checklist. Use neutral sticky notes for per-node tips. Troubleshooting No emails sent:** Ensure Contacted is blank for new rows and the Filter checks “is empty.” Auth errors (Outlook):** Reconnect credential; confirm Graph scopes and tenant consent. Sheets errors:** Re-select spreadsheet/tab; verify headers (Email, Contacted). Duplicates:* Confirm *Append/Update* uses *matching column = Email**. Tags & category Category: Sales & CRM Tags: outreach, follow-up, google-sheets, outlook, schedule, dedupe, cold-email Changelog v1.0.0 — Initial release: scheduled outreach, Outlook email, de-dupe via Contacted = Yes. Contact Need help customizing (personalization, rate-limits, CRM sync, bounce checks)? 📧 rbreen@ynteractive.com 🔗 Robert Breen — https://www.linkedin.com/in/robert-breen-29429625/ 🌐 ynteractive.com — https://ynteractive.com

Automatically detect when your scheduled or polling-trigger workflows stop running. Unlike error handlers that catch failures when workflows execute, this catches the silent killer: workflows that simply never trigger at all — broken schedules, accidental deactivation, or trigger node bugs. No hardcoded workflow list needed. It auto-discovers every active scheduled workflow and infers the expected run frequency from their trigger configuration. How it works Fetches all active workflows via the n8n API Filters to those with a Schedule Trigger or polling trigger (Outlook, Gmail, Google Sheets, IMAP, etc.) Parses cron expressions and interval settings to calculate the maximum allowed time since last execution Fetches the latest execution for each discovered workflow Raises an error listing any workflows that are overdue — pair with an Error Workflow for Slack, email, or other alerts The max age calculation adds safety margins automatically: daily workflows get 48 hours (to survive weekends), weekly gets 8 days, monthly gets 35 days, and so on. Setup Import the workflow and add your n8n API credential to the two n8n nodes ("Fetch All Active Workflows" and "Get Latest Execution") Tag this workflow with skip-monitoring so it doesn't try to monitor itself Optionally set PROJECT_ID in the "Discover Scheduled Workflows" code node to limit monitoring to a specific n8n project Set an Error Workflow in the workflow settings to receive alerts (e.g. a workflow that sends Slack messages or emails on error) Activate the workflow Customization Schedule**: Default is daily at 9am. Adjust the Schedule Trigger to your preference. Project scope**: Set PROJECT_ID to monitor only one project, or leave empty to monitor all. Exclude workflows**: Tag any workflow with skip-monitoring to opt it out. Sensitivity**: The cron parser handles minutes, hours, days, weeks, months, weekday-only schedules, and every-N-day patterns. Adjust the parseCronMaxAge function if you need different thresholds.

WhatsApp number checker Verify phone numbers from Google Sheets and check whether they are registered on WhatsApp using WasenderAPI. This workflow is useful for lead validation, contact cleanup, and pre-qualification before outreach. It uses the Wasender community node instead of a generic HTTP Request flow It includes basic phone-format validation before lookup Who is this for This workflow is useful for marketers, sales teams, freelancers, and small businesses that manage lead lists and want to validate WhatsApp availability before sending messages. It also fits broader lead-cleaning or contact-verification workflows in n8n. How it works Loads phone numbers from Google Sheets. Processes the list one row at a time to avoid sending all requests at once. Normalizes each phone number and performs basic international format validation before lookup. Checks valid numbers with WasenderAPI to see whether they are registered on WhatsApp. Writes the result back to Google Sheets for each row. Why use this workflow Uses the WasenderAPI community node instead of building the request manually with HTTP Request. Filters out obviously invalid phone numbers before calling the verification step. Can be used as a standalone checker or reused as a module inside a larger lead validation workflow. Requirements Google Sheets access and OAuth2 credentials in n8n. A WasenderAPI account and the n8n-nodes-wasenderapi community node installed. A Google Sheet containing phone numbers in the Mobile Number column. Setup Duplicate the sample Google Sheet and fill in your phone numbers under Mobile Number. Install the n8n‑nodes‑wasenderapi community nodes. Configure your Google Sheets OAuth2 and WasenderAPI credentials. Adjust the Wait node delay if needed to avoid rate limits.

Short Description Automatically exports inventory items records from NetSuite and syncs them into Salesforce — creating or updating Products. Who is this for / Use case This template is designed for businesses and integration developers who: Use NetSuite as their ERP or CRM system. Need to automatically sync products data into Salesforce. Want a reliable, scalable solution that supports pagination and upserts. Prefer a ready-to-use, easily customizable workflow built on n8n. How it works Initialize pagination offset. Fetch Salesforce Pricebook values data. Initialize pagination offset. Fetch NetSuite list of Inventory Items. Split the retrieved array into individual items. Get details for each Inventory Item from NetSuite. Find certain price value fetched from NetSuite Upserts Product into Salesforce Repeat until all records are processed, then end the workflow. Setup / Configuration Import the workflow into your n8n instance. Set your NetSuite and Salesforce credentials. Ensure your Salesforce Account/Contact objects have a matching External ID field. (Optional) Adjust mapping fields or filters to your data needs. Execute manually or trigger on a schedule (e.g., daily sync).