Pipedrive and Slack 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

This workflow enriches new Pipedrive organization's data by adding a note to the organization object in Pipedrive. It assumes there is a custom "website" field in your Pipedrive setup, as data will be scraped from this website to generate a note using OpenAI. Then, a notification is sent in Slack. ⚠️ Disclaimer This workflow uses a scraping API. Before using it, ensure you comply with the regulations regarding web scraping in your country or state. Important Notes The OpenAI model used is GPT-4o, chosen for its large input token capacity. However, it is not the cheapest model if cost is very important to you. The system prompt in the OpenAI Node generates output with relevant information, but feel free to improve or modify it according to your needs. How It Works Node 1: Pipedrive Trigger - An Organization is Created This is the trigger of the workflow. When an organization object is created in Pipedrive, this node is triggered and retrieves the data. Make sure you have a "website" custom field in Pipedrive (the name of the field in the n8n node will appear as a random ID and not with the Pipedrive custom field name). Node 2: ScrapingBee - Get Organization's Website's Homepage Content This node scrapes the content from the URL of the website associated with the Pipedrive Organization created in Node 1. The workflow uses the ScrapingBee API, but you can use any preferred API or simply the HTTP request node in n8n. Node 3: OpenAI - Message GPT-4o with Scraped Data This node sends HTML-scraped data from the previous node to the OpenAI GPT-4o model. The system prompt instructs the model to extract company data, such as products or services offered and competitors (if known by the model), and format it as HTML for optimal use in a Pipedrive Note. Node 4: Pipedrive - Create a Note with OpenAI Output This node adds a Note to the Organization created in Pipedrive using the OpenAI node output. The Note will include the company description, target market, selling products, and competitors (if GPT-4o was able to determine them). Node 5 & 6: HTML To Markdown & Code - Markdown to Slack Markdown These two nodes format the HTML output to Slack Markdown. The Note created in Pipedrive is in HTML format, as specified by the System Prompt of the OpenAI Node. To send it to Slack, it needs to be converted to Markdown and then to Slack Markdown. Node 7: Slack - Notify This node sends a message in Slack containing the Pipedrive Organization Note created with this workflow.

Use Case This workflow is beneficial when you're automatically adding new leads to your Pipedrive CRM. Usually, you'd have to manually review each lead to determine if they're a good fit. This process is time-consuming and increases the chances of missing important leads. This workflow ensures every new lead is promptly evaluated upon addition. What this workflow does The workflow runs every 5 minutes. On every run, it checks your new Pipedrive leads and enriches them with Clearbit. It then marks items as enriched and checks if the company of the new lead matches certain criteria (in this case if they are B2B and have more than 100 employees) and sends a Slack alert to a channel for every match. Pre Conditions You must have Pipedrive, Clearbit, and Slack accounts. You also need to set up the custom fields Domain and Enriched at in Pipedrive. Setup Go to Company Settings -> Data fields -> Organization and add Domain as a custom field Go to Company Settings -> Data fields -> Leads and add Enriched at as a custom date field Add your Pipedrive, Clearbit and Slack credentials. Fill the setup node below. To get the ID of your custom domain fields, simply run the Show only custom organization fields and Show only custom lead fields nodes below and copy the keys of your domain, and enriched at fields. How to adjust this workflow to your needs Modify the criteria to suit your definition of an interesting lead. If you only want to focus on interesting leads in Pipedrive, add a node that archives all others. This workflow was built using n8n version 1.29.1

This workflow is triggered when a meeting is scheduled via Calendly. Then, an activity is automatically created in Pipedrive and 15 minutes after the end of the meeting, a message is sent to the interviewer in Slack, reminding them to write down their notes and insights from the meeting.