HTTP Request 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

Community Node Disclaimer This workflow uses KlickTipp community nodes, available for self-hosted n8n instances only. Who’s it for Sales and marketing teams using Pipedrive (Persons) and KlickTipp who want a reliable two-way sync for: Contact profiles (name, email, phone, birthday) Consent/marketing status (subscribed / no consent / unsubscribed) Segmentation (KlickTipp Tags ↔ Pipedrive Labels) This workflow is ideal if you want to avoid CSV imports, prevent manual updates, and ensure that changes in either platform are reflected in the other — including deletes and consent changes. How it works This workflow creates a complete two-way synchronization between KlickTipp and Pipedrive (Persons). Whenever a Person is created, updated, unsubscribed, segmented, or deleted in either system, the workflow mirrors these changes across both platforms — so your CRM and email marketing database always stay aligned. It is designed for near real-time syncing of contact data, consent state, and segmentation (Tags ↔ Labels), without manual work. KlickTipp → Pipedrive Triggered by KlickTipp webhooks / activation tag events via “Contact tagged in KlickTipp”: Fetch contact details in KlickTipp (Get contact data for tagging) to access tags and custom fields. Route by contact state (Check subscription): Person does not exist (no stored Pipedrive ID in KlickTipp) and contact is not Unsubscribed → Create a person in Pipedrive. Person exists and contact is not Unsubscribed → Update a person in Pipedrive. Person exists → unsubscribe → Update a person and set marketing_status = unsubscribed. Write the Pipedrive Person ID back to KlickTipp (Add Pipedrive Person ID to KlickTipp contact) to permanently link both records. Sync consent status: KlickTipp status = Subscribed → Pipedrive marketing_status = subscribed Otherwise → marketing_status = no_consent Sync birthday safely (timezone-aware): KlickTipp birthday is stored as Unix seconds and converted to YYYY-MM-DD using Europe/Berlin timezone to avoid CET/CEST shifts. Segmentation: KlickTipp Tags → Pipedrive Labels: Reads KlickTipp tags (Check relevant segment) and assigns Pipedrive label IDs via PATCH: Tag 14054258 → Label 14 (Customer) Tag 14054294 → Label 27 (ABC) Pipedrive → KlickTipp Triggered by the Pipedrive Person webhook via “Changes in Pipedrive”: Fetch the current marketing status (Get marketing status) to decide which consent action to apply in KlickTipp. Route by sync scenario (Check subscription1): Single Opt-In If no linked KlickTipp ID exists yet and status is not unsubscribed → create contact in KlickTipp via SOI (Create contact with SOI). Form submission → DOI If change_source = api → create contact in KlickTipp via DOI (Create contact with DOI). Update only If linked KlickTipp ID exists and status is not unsubscribed → update the existing KlickTipp subscriber (Update contact changes in KlickTipp). Unsubscribe and update If linked KlickTipp ID exists and status is unsubscribed → unsubscribe the contact (Unsubscribe contact) and then update core fields (Update contact changes in KlickTipp1). Contact deletion If action is delete → delete the KlickTipp contact using the previous email (Delete contact) to remain safe even if the email changed before deletion. UI-only filtering for SOI path Filter non UI events and deletions ensures the SOI create path processes only UI-driven events (change_source = app) and ignores deletions. Sync birthday safely (no day shifting) Reads Pipedrive birthday as YYYY-MM-DD from a custom field and converts it to Unix seconds using "T00:00:00Z" to prevent timezone-related day shifts. Segmentation: Pipedrive Labels → KlickTipp Tags Reads label_ids from Pipedrive (supports array or comma-separated string), normalizes them, then applies tags in KlickTipp (Check relevant segment2): Label 14 (Customer) → Tag 14054258 Label 27 (ABC) → Tag 14054294 GDPR Deletion Requests (KlickTipp → Pipedrive) Triggered by “Contact deletion request triggered” (when a recipient clicks the data deletion link in an email): Immediately deletes the subscriber in KlickTipp. If a linked Pipedrive Person ID exists (field227685), the workflow: Deletes the corresponding Person in Pipedrive. If no Pipedrive ID exists, only the KlickTipp record is removed. This ensures full GDPR-compliant data removal across both systems. How to set up Install the KlickTipp community node in your self-hosted n8n instance. Create credentials in n8n for: KlickTipp API Pipedrive API (token or OAuth) In KlickTipp, create a custom field to store the Pipedrive reference: Example used here: Pipedrive | Person ID (mapped as field227685) In Pipedrive (Person), create custom fields to store: KlickTipp Contact ID (stored via Pipedrive custom properties) Birthday (optional, if you want birthday sync) Configure your segmentation mapping: Ensure Pipedrive Labels exist and note their IDs (e.g. 14 = Customer, 27 = ABC) Ensure KlickTipp Tags exist and note their IDs (e.g. 14054258, 14054294) Test both directions: Add a tag in KlickTipp → confirm the Person is created/updated in Pipedrive and labels are assigned. Update a Person in Pipedrive → confirm the subscriber is created/updated/unsubscribed in KlickTipp accordingly. Activate the workflow. 💡 Pro Tip: Start testing with a single contact and one label/tag mapping first, then expand to more fields and segments. Requirements Self-hosted n8n instance (community nodes supported) KlickTipp** account with API access Pipedrive** account with API access Pipedrive Person webhook enabled (create/update/delete events) KlickTipp webhook/activation tag configured to trigger the KlickTipp side How to customize Add more field mappings (organization, address, custom properties, owner). Extend segmentation rules (more labels/tags, deal-based logic, pipeline-specific tags). Adjust SOI/DOI routing (e.g., force DOI for certain sources or segments). Add audit logging (Google Sheets, database, or Slack alerts on errors). Add safeguards (e.g., skip contacts without email, handle duplicates with additional lookup logic).

CRM Contact Sync with Mailchimp and Pipedrive This workflow keeps your contact records perfectly aligned between your CRM (e.g. HubSpot / Salesforce / Pipedrive) and Mailchimp. Whenever a contact is created or updated in one system, the automation propagates the change to the other platform, ensuring every email address, phone number and custom field stays in sync. Pre-conditions/Requirements Prerequisites n8n instance (self-hosted or cloud) Community nodes: Pipedrive, Mailchimp A dedicated service account in each platform with permission to read & write contacts Basic understanding of how webhooks work (for CRM → n8n triggers) Required Credentials Pipedrive API Token** – Used for creating, updating and searching contacts in Pipedrive Mailchimp API Key** – Grants access to lists/audiences and contact operations CRM Webhook Secret** (optional) – If your CRM supports signing webhook payloads Specific Setup Requirements | Environment Variable | Description | Example | |----------------------|--------------------------------------|---------------------------------| | PIPEDRIVE_API_KEY | Stored in n8n credential manager | 123abc456def | | MAILCHIMP_API_KEY | Stored in n8n credential manager | us-1:abcd1234efgh5678 | | MAILCHIMP_DC | Mailchimp Datacenter (sub-domain) | us-1 | | CRM_WEBHOOK_URL | Generated by the Webhook node | https://n8n.myserver/webhook/... | How it works This workflow keeps your contact records perfectly aligned between your CRM (e.g. HubSpot / Salesforce / Pipedrive) and Mailchimp. Whenever a contact is created or updated in one system, the automation propagates the change to the other platform, ensuring every email address, phone number and custom field stays in sync. Key Steps: Inbound Webhook**: Receives contact-change events from the CRM. Split in Batches**: Processes contacts in chunks to stay within API rate limits. Mailchimp Upsert**: Adds or updates each contact in the specified Mailchimp audience. Pipedrive Upsert**: Mirrors the same change in Pipedrive (or vice-versa). Merge & IF nodes**: Decide whether to create or update a contact by checking existence. Error Trigger**: Captures any API failures and posts them to the configured alert channel. Set up steps Setup Time: 15-25 minutes Create credentials • In n8n, add new credentials for Pipedrive and Mailchimp using your API keys. • Name them clearly (e.g. “Pipedrive Main”, “Mailchimp Main”). Import the workflow • Download or paste the JSON template into n8n. • Save the workflow. Configure the Webhook node • Set HTTP Method to POST. • Copy the generated URL and register it as a webhook in your CRM’s contact-update events. Map CRM fields • Open the first Set node and match CRM field names (firstName, lastName, email, etc.) to the standard keys used later in the flow. Select Mailchimp Audience • In the Mailchimp node, choose the audience/list that should receive the contacts. Define Pipedrive Person Fields • If you have custom fields, add them in the Pipedrive node’s Additional Fields section. Enable the workflow • Turn the workflow from “Inactive” to “Active”. • Send a test update from the CRM to verify that contacts appear in both Mailchimp and Pipedrive. Node Descriptions Core Workflow Nodes: Webhook** – Accepts contact-change payloads from the CRM. Set** – Normalises field names to a common schema. SplitInBatches** – Loops through contacts in controllable group sizes. HTTP Request** – Generic calls (e.g. HubSpot/Salesforce look-ups when required). Pipedrive** – Searches for existing persons; creates or updates accordingly. Mailchimp** – Performs contact upsert into an audience. If** – Branches logic on “contact exists?”. Merge** – Re-assembles branch data back into a single execution line. Code** – Small JS snippets for complex field transformations. Error Trigger** – Listens for any node failure and routes it to alerts. StickyNote** – Documentation hints inside the workflow. Data Flow: Webhook → Set (Normalise) → SplitInBatches SplitInBatches → Mailchimp (Get) → If (Exists?) → Mailchimp (Upsert) SplitInBatches → Pipedrive (Search) → If (Exists?) → Pipedrive (Upsert) Merge → End / Success Customization Examples Add a Tag to Mailchimp contacts // Place inside a Code node before the Mailchimp Upsert item.tags = ['Synced from CRM', 'High-Value']; return item; Apply a Deal Stage in Pipedrive // Pipedrive node → Additional Fields "deal": { "title": "New Lead from Mailchimp", "stage_id": 2 } Data Output Format The workflow outputs structured JSON data: { "id": 1472, "status": "updated", "email": "[email protected]", "source": "CRM", "synced": { "pipedrive": "success", "mailchimp": "success" }, "timestamp": "2024-04-27T10:15:00Z" } Troubleshooting Common Issues HTTP 401 Unauthorized – Verify that the API keys are still valid and have not been revoked. Webhook receives no data – Double-check that the CRM webhook URL matches exactly and that the event is enabled. Performance Tips Batch contacts in groups of 50-100 to respect Mailchimp & Pipedrive rate limits. Use Continue On Fail in non-critical nodes to prevent the entire run from stopping. Pro Tips: Map your CRM’s custom fields once in the Set node to avoid touching each downstream node. Use Merge+If pattern to keep “create vs update” logic tidy. Enable workflow execution logs only in development to reduce storage usage. *Community Template Disclaimer: This workflow is provided by the n8n community “as is”. n8n GmbH makes no warranties regarding its performance, security or compliance. Always review and test in a development environment before using it in production.*

Medical Research Tracker with Email and Pipedrive ⚠️ COMMUNITY TEMPLATE DISCLAIMER: This is a community-contributed template that uses ScrapeGraphAI (a community node). Please ensure you have the ScrapeGraphAI community node installed in your n8n instance before using this template. This workflow automatically scans authoritative healthcare policy websites for new research, bills, or regulatory changes, stores relevant findings in Pipedrive, and immediately notifies key stakeholders via email. It is ideal for healthcare administrators and policy analysts who need to stay ahead of emerging legislation or guidance that could impact clinical operations, compliance, and strategy. Pre-conditions/Requirements Prerequisites n8n instance (self-hosted or n8n cloud) ScrapeGraphAI community node installed Pipedrive account and API token SMTP credentials (or native n8n Email credentials) for sending alerts List of target URLs or RSS feeds from government or healthcare policy organizations Basic familiarity with n8n credential setup Required Credentials | Service | Credential Name | Purpose | |--------------------|-----------------|-----------------------------------| | ScrapeGraphAI | API Key | Perform web scraping | | Pipedrive | API Token | Create / update deals & notes | | Email (SMTP/Nodemailer) | SMTP creds | Send alert emails | Environment Variables (optional) | Variable | Example Value | Description | |-------------------------|------------------------------|-----------------------------------------------| | N8N_DEFAULT_EMAIL_FROM | [email protected] | Default sender for Email Send node | | POLICY_KEYWORDS | telehealth, Medicare, HIPAA | Comma-separated keywords for filtering | How it works This workflow automatically scans authoritative healthcare policy websites for new research, bills, or regulatory changes, stores relevant findings in Pipedrive, and immediately notifies key stakeholders via email. It is ideal for healthcare administrators and policy analysts who need to stay ahead of emerging legislation or guidance that could impact clinical operations, compliance, and strategy. Key Steps: Manual Trigger**: Kick-starts the workflow or schedules it via cron. Set → URL List**: Defines the list of healthcare policy pages or RSS feeds to scrape. Split In Batches**: Iterates through each URL so scraping happens sequentially. ScrapeGraphAI**: Extracts headlines, publication dates, and links. Code (Filter & Normalize)**: Removes duplicates, standardizes JSON structure, and applies keyword filters. HTTP Request**: Optionally enriches data with summary content using external APIs (e.g., OpenAI, SummarizeBot). If Node**: Checks if the policy item is new (not already logged in Pipedrive). Pipedrive**: Creates a new deal or note for tracking and collaboration. Email Send**: Sends an alert to compliance or leadership teams with the policy summary. Sticky Note**: Provides inline documentation inside the workflow. Set up steps Setup Time: 15–20 minutes Install ScrapeGraphAI: In n8n, go to “Settings → Community Nodes” and install n8n-nodes-scrapegraphai. Create Credentials: a. Pipedrive → “API Token” from your Pipedrive settings → add in n8n. b. ScrapeGraphAI → obtain API key → add as credential. c. Email SMTP → configure sender details in n8n. Import Workflow: Copy the JSON template into n8n (“Import from clipboard”). Update URL List: Open the initial Set node and replace placeholder URLs with the sites you monitor (e.g., cms.gov, nih.gov, who.int, state health departments). Define Keywords (optional): a. Open the Code node “Filter & Normalize”. b. Adjust the const keywords = [...] array to match topics you care about. Test Run: Trigger manually; verify that: Scraped items appear in the execution logs. New deals/notes show up in Pipedrive. Alert email lands in your inbox. Schedule: Add a Cron node (e.g., every 6 hours) in place of Manual Trigger for automated execution. Node Descriptions Core Workflow Nodes: Manual Trigger** – Launches the workflow on demand. Set – URL List** – Holds an array of target policy URLs/RSS feeds. Split In Batches** – Processes each URL one at a time to avoid rate limiting. ScrapeGraphAI** – Scrapes page content and parses structured data. Code – Filter & Normalize** – Cleans results, removes duplicates, applies keyword filter. HTTP Request – Summarize** – Calls a summarization API (optional). If – Duplicate Check** – Queries Pipedrive to see if the policy item already exists. Pipedrive (Deal/Note)** – Logs a new deal or adds a note with policy details. Email Send – Alert** – Notifies subscribed stakeholders. Sticky Note** – Embedded instructions inside the canvas. Data Flow: Manual Trigger → Set (URLs) → Split In Batches → ScrapeGraphAI → Code (Filter) → If (Duplicate?) → Pipedrive → Email Send Customization Examples Add Slack notifications // Insert after Email Send { "node": "Slack", "parameters": { "channel": "#policy-alerts", "text": New policy update: ${$json["title"]} - ${$json["url"]} } } Use different CRM (HubSpot) // Replace Pipedrive node config { "resource": "deal", "operation": "create", "title": $json["title"], "properties": { "dealstage": "appointmentscheduled", "description": $json["summary"] } } Data Output Format The workflow outputs structured JSON data: { "title": "Telehealth Expansion Act of 2024", "date": "2024-05-30", "url": "https://www.congress.gov/bill/118th-congress-house-bill/1234", "summary": "This bill proposes expanding Medicare reimbursement for telehealth services...", "source": "congress.gov", "status": "new" } Troubleshooting Common Issues Empty Scrape Results – Check if the target site uses JavaScript rendering; ScrapeGraphAI may need a headless browser option enabled. Duplicate Deals in Pipedrive – Ensure the “If Duplicate?” node compares a unique field (e.g., URL or title) before creating a new deal. Performance Tips Limit batch size to avoid API rate limits. Cache or store the last scraped timestamp to skip unchanged pages. Pro Tips: Combine this workflow with an n8n “Cron” or “Webhook” trigger for fully automated monitoring. Use environment variables for keywords and email recipients to avoid editing nodes each time. Leverage Pipedrive’s automations to notify additional teams (e.g., legal) when high-priority items are logged.

📌 Overview Description: This powerful workflow automates your sales quotation process by connecting Pipedrive with DottedSign. When a deal is moved to a specific stage in Pipedrive, this template automatically generates a professional PDF quotation, uploads it back to the deal, and sends it out for e-signature via DottedSign service, saving your sales team valuable time and eliminating manual work. What it does When a Pipedrive deal moves to a designated stage (e.g., "Quotation Stage"), this workflow triggers and performs the following actions: Gathers Data: It collects all relevant information, including deal details, client contacts, organization info, and associated products from Pipedrive. Generates PDF Quote: It populates a customizable HTML template with the collected data and uses a PDF generation service (Gotenberg) to create a polished PDF document. Uploads to Pipedrive: The generated PDF quote is automatically uploaded to the "Files" section of the corresponding Pipedrive deal for record-keeping. Sends for E-Signature: It creates a new signing task in DottedSign, sending the quotation to the client for their electronic signature. Requirements A Pipedrive account with admin permissions. A DottedSign developer account to obtain API credentials. A self-hosted instance of Gotenberg for HTML to PDF conversion. How to set up Pipedrive Trigger Stage: In the If node, change the stage ID 7 to the ID of the pipeline stage you want to use as the trigger. PDF Conversion Service: In the Gotenberg to PDF (HTTP Request) node, replace the placeholder URL with the endpoint of your running Gotenberg instance. DottedSign Credentials: In the Get DottedSign Access Token node, enter your client_id and client_secret in the request body. DottedSign Signature Field: In the Create DottedSign Task node, you must adjust the page and coord values under field_settings to match the desired signature location on your PDF template. How to customize the workflow Quotation Template:** Edit the Generate Quotation HTML node to modify the quote's appearance, text, company logo, and terms. The {{ ... }} expressions are placeholders that are filled with Pipedrive data. Trigger:** Replace the Pipedrive Trigger with another trigger, such as a webhook or a form submission, to adapt the workflow to different needs. Notifications:** Add a Slack or email node at the end of the workflow to notify the sales team once the quotation has been sent.

Stripe → Pipedrive (Automatic Person + Deal Creation) Prerequisites / Requirements n8n instance (cloud or self-hosted) with HTTPS reachable webhook endpoint Stripe account and secret API key Pipedrive account with API access and custom fields defined Users should create custom fields in Pipedrive and copy their field IDs (e.g. amount, payment method, status, Stripe Event ID) How it works (Step-by-Step) Stripe Webhook: n8n triggers on payment events from Stripe via an HTTP POST. Edit / Set node: Extracts eventId, eventType, and payload. HTTP Request: Confirms Stripe event via Stripe API (adds security). Search Person: Looks up Pipedrive contact by email from the Stripe payload. IF: Checks whether the person exists. If exists → skip to deal creation. If node - Check if Event id is not the same If same - Skip the deal creation If different - Create a deal linked to that person with the payment amount If not → create new Person. Create Person: Adds new Pipedrive contact, populates custom fields (amount, payment method, status, source). Create Deal: Creates a deal linked to that person with the payment amount. Description **This workflow connects Stripe to Pipedrive. Whenever a new payment (or checkout success) occurs in Stripe, this automation will: Fetch the full Stripe event data Find or create a customer (“Person”) in Pipedrive Create a “Deal” record corresponding to that payment Log custom fields like amount, source, payment method, status It’s ideal for SaaS Subscription businesses Agencies, or Teams who want payments mirrored inside their CRM without manual work. Modification Notes / Extensions You can extend this workflow by: Adding Slack or Gmail notifications after deal creation. Logging every event in Google Sheets or Notion for audit. Enriching the customer using OpenAI / CRM data. Handling refunds, subscription cancellations, etc.