by BHSoft
Email Contacts Sync from Sent Mailbox to Odoo This workflow automatically extracts recipient email addresses from previously sent emails, validates and cleans the data, and synchronizes only deliverable contacts into the internal Odoo Mailing List. It also monitors replies and bounce signals to support follow-up and engagement tracking. πWho is this for? Marketing team (Email campaigns) CRM / Odoo administrators Sales team (follow-up & customer engagement) Operations / Automation engineers (n8n workflows) πThe problem Customer emails are scattered across sent mail history instead of a centralized list. Manually copying recipients into Odoo is slow and error-prone. Sent emails may include invalid or bounced addresses. Duplicate contacts appear frequently. Hard to know which recipients have replied or not for follow-up. This leads to: messy contact database high bounce rate missed follow-ups inefficient manual work πHow it works The system calculates the target date and queries the Gmail API to retrieve emails sent within the last X days. For each sent email: Extract recipients from the To/Cc fields Normalize data (trim, lowercase, remove duplicates) Check the email thread to detect replies or bounce/system responses Each recipient is then classified into one of the following lists: deliverableEmails repliedEmails bounceEmails autoReplies noResponse Push the list of deliverable emails to the internal Odoo system as Mailing List Contacts. Add emails from the bounce list to Blacklisted Email Addresses in Odoo to prevent future sending. (Optional) Log all processing results into Google Sheets for tracking and auditing. πQuick setup Required information: N8n Version 2.4.6 Gmail OAuth2 API Odoo API-KEY Google Sheets will be used to log all notified events. πResults Automatically build contact list from real sent emails No manual data entry Only valid emails stored in Odoo Reduced bounce rate No duplicates Easy follow-up tracking Better CRM hygiene and campaign performance πTake it further Auto follow-up if no reply after X days Auto-remove hard bounces Engagement scoring Reply analytics dashboard Sync with Loyalty/CRM systems Scheduled daily sync πNeed help customizing? Contact me for consulting and support: Linkedin / Website
by Trung Tran
Automated Slack Channel Audit Workflow with Chatbot and GPT-4.1 > Automatically scans all public Slack channels weekly to detect those with no activity in the past 30 days, then generates and sends a detailed inactivity report to admins for review and action. Helps keep your Slack workspace clean, relevant, and clutter-free. π§βπΌ Whoβs it for This workflow is built for: Slack Workspace Admins** IT or Ops Managers** HR/Compliance Teams** β¦who want to maintain a clean and active Slack workspace by regularly reviewing inactive channels. βοΈ How it works / What it does This automated n8n workflow: Runs weekly via a scheduled trigger. Fetches all public Slack channels in the workspace. Checks message history of each channel for activity. Filters channels that have had no discussion in the past 30 days. Generates a Slack-friendly report with key metadata (name, member count, purpose, etc.). Sends the report to a Slack channel for admin review and possible action (e.g., archive, engage, repurpose). π οΈ How to set up Configure your Slack App Go to https://api.slack.com/apps β Create App Add the following OAuth scopes to your Bot Token: channels:read β to get list of public channels channels:history β to fetch message history users:read β to personalize report (optional) chat:write β to post the report to a Slack channel Install the app in your workspace Copy the Bot User OAuth Token Add it to your n8n Slack credentials under "Slack API" Customize the schedule in the "Weekly Schedule Trigger" node to control report frequency. Connect your Slack workspace to the workflow using your credentials. β Requirements n8n (self-hosted or cloud) Slack App with: channels:read channels:history chat:write Active channels and member data A designated Slack channel to receive the report π§ How to customize the workflow | Component | Customization Options | |----------|------------------------| | β±οΈ Schedule Trigger | Change to daily, monthly, etc. | | π Inactivity Threshold | Modify Filter channel with last discussion 30 days ago to 60/90 days | | π Report Formatting | Tweak the Consume slack report node to change formatting or summary | | π¬ Output Channel | Change target channel in Send Channel Inactivity Report | | π« Auto-archiving | Add logic to archive channels with 0 members or activity (using Slack API) | π Slack Permissions Reference | Action | Slack Scope Required | |--------|-----------------------| | Get all public channels | channels:read | | Get message history of a channel | channels:history | | Post message to Slack | chat:write | | Get user info (optional) | users:read |
by Harshil Agrawal
This workflow allows you to create a quote and a transfer, execute the transfer and get the information of the transfer using the Wise node. Wise node: This node will create a new quote in Wise. Wise1 node: This node will create a new transfer for the quote that we created in the previous node. Wise2 node: This node will execute the transfer that we created in the previous node. Wise3 node: This node will return the information of the transfer that we executed in the previous node.
by Oneclick AI Squad
This automated n8n workflow enables intelligent auto-replies to LinkedIn comments by sending personalized direct messages (DMs) with relevant resources. When users comment on your posts, the workflow monitors engagement, filters valid interactions, analyzes comment content using keyword matching, and delivers tailored responses via LinkedIn messaging. It ensures duplicate prevention, tracks all message deliveries, and maintains logs for monitoring and compliance. Fundamental Aspects Monitor posts: Every 5 minutes, the workflow fetches your 10 most recent LinkedIn posts Collect comments: Retrieves all comments from each post (up to 20 per post) Filter engagement: Removes your own comments and tracks previously contacted users Smart matching: Analyzes comment text using keyword matching to determine the most relevant resource (eBook, webinar, template, tool, or checklist) Personalize message: Creates a custom DM with the commenter's name and selected resource Send and track: Delivers the message via LinkedIn and logs the interaction Setup steps Connect LinkedIn: Add your LinkedIn OAuth2 credentials to these nodes: Fetch Recent Posts Fetch Post Comments Send DM via LinkedIn Update resource URLs: Open the "Match Resource to Comment" node and replace all https://yourwebsite.com/... URLs with your actual resource links Customize message (optional): Edit the "Build Personalized Message" node to adjust the DM template and tone Test first: Click "Execute Workflow" to test before activating. Check the execution log to verify it works correctly Activate: Once tested, toggle the workflow to "Active" to run automatically every 5 minutes Technical Dependencies LinkedIn API**: For fetching recent posts, retrieving comments, and sending direct messages through OAuth2 authentication. n8n Platform**: For workflow orchestration, scheduled execution, conditional logic, data merging, and static data persistence. JavaScript Runtime**: For custom code execution in analysis, message generation, deduplication logic, and success logging nodes. Workflow Static Data**: For persistent storage of processed comment tracking across workflow executions without external databases. Customization Possibilities Adjust Monitoring Frequency**: Change the Schedule Trigger interval from 5 minutes to hourly, daily, or based on your posting frequency to optimize resource usage. Expand Resource Categories**: Add new resource types like case studies, white papers, free trials, or consultation bookings with corresponding keywords and URLs. Enhance Keyword Matching**: Implement weighted scoring, multi-word phrase matching, or semantic similarity analysis for more accurate resource selection. Add Sentiment Analysis**: Filter comments by sentiment to prioritize enthusiastic or question-asking commenters for resource delivery. Multi-Language Support**: Detect comment language and send localized resources and message templates for global audiences. A/B Test Messages**: Create multiple message variations and randomly assign them to track which messaging performs best. Integration with CRM**: Add nodes to log commenter information in your CRM (HubSpot, Salesforce) for lead tracking and follow-up. Advanced Analytics**: Connect to Google Sheets or databases to track delivery rates, response times, and resource click-through rates over time. Rate Limit Protection**: Add conditional logic to pause workflow if daily message limits are reached to prevent LinkedIn restrictions. Post-Specific Resources**: Map different resources to specific posts based on post topic or hashtags for more contextual recommendations. Explore More LinkedIn & Social Automation: Contact us to design AI-powered lead nurturing, content engagement, and multi-platform reply workflows tailored to your growth strategy.
by Entech Solutions
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).
by David Olusola
ποΈ 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.
by Harshil Agrawal
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.
by Gaurav
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!
by Moe Ahad
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.
by Rahul Joshi
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. β
by Robert Breen
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
by Julian Kaiser
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.