Gmail and Pipedrive integration

Description This workflow is designed for B2B/SaaS teams who want to secure renewals before it’s too late. It runs every day, identifies all accounts whose licenses are up for renewal in J–30, enriches them with CRM, product usage and support data, computes an internal churn risk level, and then triggers the appropriate playbook: HIGH risk** → full escalation (tasks, alerts, emails) MEDIUM risk** → proactive follow-up by Customer Success LOW risk** → light renewal touchpoint / monitoring Everything is logged into a database table so that you can build dashboards, run analysis, or plug additional automations on top. How it works Daily detection (J–30 renewals) A scheduled trigger runs every morning and queries your database (Postgres / Supabase) to fetch all active subscriptions expiring in 30 days. Each row includes the account identifier, name, renewal date and basic commercial data. Data enrichment across tools For each account, the workflow calls several business systems to collect context: HubSpot → engagement history Salesforce → account profile and segment Pipedrive → deal activities and associated products Analytics API → product feature usage and activity trends Zendesk → recent support tickets and potential friction signals All of this is merged into a single, unified item. Churn scoring & routing An internal scoring step evaluates the risk for each account based on multiple signals (engagement, usage, support, timing). The workflow then categorizes each account into one of three risk levels: HIGH – strong churn signals → needs immediate attention MEDIUM – some warning signs → needs proactive follow-up LOW – looks healthy → light renewal reminder A Switch node routes each account to the relevant playbook. Automated playbooks 🔴 HIGH risk Create a Trello card on a dedicated “High-Risk Renewals” board/list Create a Jira ticket for the CS / AM team Send a Slack alert in a designated channel Send a detailed email to the CSM and/or account manager 🟠 MEDIUM risk Create a Trello card in a “Renewals – Follow-up” list Send a contextual email to the CSM to recommend a proactive check-in 🟢 LOW risk Send a soft renewal email / internal note to keep the account on the radar Logging & daily reporting For every processed account, the workflow prepares a structured log record (account, renewal date, risk level, basic context). A Postgres node is used to insert the data into a churn_logs table. At the end of each run, all processed accounts are aggregated and a daily summary email is sent (for example to the Customer Success leadership team), listing the renewals and their risk levels. Requirements Database A table named churn_logs (or equivalent) to store workflow decisions and history. Example fields: account_id, account_name, end_date, riskScore, riskLevel, playbook, trello_link, jira_link, timestamp. External APIs HubSpot (engagement data) Salesforce (account profile) Pipedrive (deals & products) Zendesk (support tickets) Optional: product analytics API for usage metrics Communication & task tools Gmail (emails to CSM / AM / summary recipients) Slack (alert channel for high-risk cases) Trello (task creation for CS follow-up) Jira (escalation tickets for high-risk renewals) Configuration variables Thresholds are configured in the Init config & thresholds node: days_before_renewal churn_threshold_high churn_threshold_medium These parameters let you adapt the detection window and risk sensitivity to your own business rules. Typical use cases Customer Success teams who want a daily churn watchlist without exporting spreadsheets. RevOps teams looking to standardize renewal playbooks across tools. SaaS companies who need to prioritize renewals based on real risk signals rather than gut feeling. Product-led organizations that want to combine usage data + CRM + support into one automated process. Tutorial video Watch the Youtube Tutorial video About me : I’m Yassin a Project & Product Manager Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin

Categories CRM Automation, Revenue Operations, Sales Operations, Meeting Automation Build a Revenue Ops Meeting Pipeline with Pipedrive, Calendar, Slack This workflow creates a CRM-driven revenue operations meeting pipeline that automatically coordinates meetings once a deal reaches a specific stage in Pipedrive. When a deal moves into the Meeting Booking stage, the workflow waits for the SDR to complete the meeting details, creates the event in Google Calendar, sends a confirmation email to the client, and notifies the internal team in Slack. The result is a reliable, no-manual-work system that ensures meetings are scheduled, confirmed, and communicated without human follow-up. Benefits CRM as the Single Source of Truth** All automation is triggered directly from deal stage changes. Reduced No-Shows** Clients receive timely meeting confirmations with correct links and times. Zero Manual Coordination** No copying links, sending reminders, or checking calendars. Internal Visibility** Sales teams receive Slack reminders automatically. Time-Zone Safe Scheduling** Meeting times are calculated and normalized automatically. How It Works Deal Stage Trigger (Pipedrive) Listens for deal updates in Pipedrive Runs only when the deal enters the Meeting Booking stage Prevents execution on irrelevant pipeline changes Controlled Wait Logic Pauses execution to allow the SDR to: Add the meeting link Set date, time, and duration Ensures data completeness before scheduling Data Extraction & Enrichment Fetches full deal details Extracts: Client name and email Company name Meeting link Meeting date and time Calculates ISO start and end times with time-zone handling Calendar Event Creation (Google Calendar) Creates a calendar event automatically Adds the client as an attendee Inserts the meeting link as the event location Client Email Confirmation Sends a personalized confirmation email Includes meeting date, time, and context Reduces rescheduling and confusion Internal Slack Notification Sends a reminder to a selected Slack channel Notifies SDRs and sales managers of upcoming meetings Keeps teams aligned without CRM checking Required Setup Pipedrive Deal pipeline with a defined Meeting Booking stage Meeting details stored in deal activities Google Calendar OAuth access enabled Permission to create events Gmail OAuth access enabled Email sending permissions Slack OAuth access enabled Target channel selected Business Use Cases Sales Teams Eliminate missed meetings and manual reminders Reduce admin work for SDRs Revenue Operations Standardize meeting execution across pipelines Improve forecasting reliability Founders & Managers Increase meeting attendance without micromanagement Agencies & Consultants Deliver CRM-based RevOps automation to clients Difficulty Level Intermediate Estimated Build Time 45–60 minutes Monthly Operating Cost Pipedrive: Existing plan Google Calendar: Free Gmail: Free Slack: Free or paid workspace n8n: Self-hosted or cloud Typical range: $0–20/month Why This Workflow Works Deal stage changes represent real sales intent Waiting logic prevents broken automations Calendar-first execution ensures reliability Multi-channel notifications reduce human error Possible Extensions Add SMS or WhatsApp reminders Auto-cancel meetings on stage rollback Log meeting outcomes back to Pipedrive Trigger post-meeting follow-ups Add AI-generated meeting summaries

About the workflow The workflow reads every reply that is received from a cold email campaign and qualifies if the lead is interested in a meeting. If the lead is interested, a deal is made in pipedrive. You can add as many email inboxes as you need! Setup: Add credentials to the Gmail, OpenAI and Pipedrive Nodes. Add a in_campaign field in Pipedrive for persons. In Pipedrive click on your credentials at the top right, go to company settings > Data fields > Person and click on add custom field. Single option [TRUE/FALSE]. If you have only one email inbox, you can delete one of the Gmail nodes. If you have more than two email inboxes, you can duplicate a Gmail node as many times as you like. Just connect it to the Get email node, and you are good to go! In the Gmail inbox nodes, select Inbox under label names and uncheck Simplify.