Webhook and Pipedrive integration

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.*

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.

How it Works: Capture Contact Requests:** This template efficiently handles contact requests coming through a WordPress website using the Contact Form 7 (CF7) plugin with a webhook extension. Contact Management:** It automatically creates or updates contacts in Pipedrive upon receiving a new request. Lead Management:** Each contact request is securely stored in the lead inbox of Pipedrive, ensuring no opportunity is missed. Task Creation:** For each new contact or update, the workflow triggers the creation of a related task, streamlining follow-up actions. Note Attachment:** A comprehensive note containing all details from the contact request is attached to the corresponding lead, ensuring that all information is readily accessible. Step-by-Step Guide: Estimated Setup Time: The setup process is straightforward and can be completed quickly. Specific time may vary depending on your familiarity with n8n and the systems involved. Detailed setup instructions are provided within the workflow via sticky notes. These notes offer in-depth guidance for configuring each component of the template to suit your specific needs.