What this workflow does
This workflow updates Stripe customer records automatically when a deal is won in Pipedrive.
It stops users from doing manual work and making mistakes.
When a deal’s “won time” changes, it creates a customer in Stripe if one does not exist.
The result is faster billing and fewer errors.
Who should use this workflow
This workflow fits sales managers or teams who use Pipedrive to track deals and Stripe for billing.
It helps those who want to reduce manual data entry and prevent duplicate customer records.
Tools and services used
- Pipedrive API: For deal updates and organization data.
- Stripe API: To search and create customers.
- n8n automation platform: To build and run the workflow.
- Optional hosting: self-host n8n can be used for control over automation.
Input, processing, and output
Inputs
- Deal update event from Pipedrive when any deal changes.
- Fields “won time” and organization ID from the deal data.
Processing steps
- Check if the deal’s “won time” changed using an If node.
- Retrieve organization info from Pipedrive using the organization ID.
- Search Stripe customers by organization name with an HTTP Request node.
- Use another If node to verify if the customer exists.
- If no customer exists, merge organization data and create a new Stripe customer with name and complete address.
Output
A new customer is created in Stripe matching the Pipedrive organization.
Duplicate customers are avoided.
Address and contact info are copied to Stripe.
Beginner step-by-step: How to use this workflow in n8n
Step 1: Import the workflow
- Download the workflow file using the Download button on this page.
- Inside the n8n editor, click “Import from File” and select the downloaded file.
Step 2: Add credentials
- Add your Pipedrive API Key in n8n credentials.
- Set up your Stripe API Key in n8n credentials.
Step 3: Update workflow settings
- Check the Pipedrive Trigger node is connected to your Pipedrive account.
- If necessary, update organization or pipeline IDs in expression fields.
- Verify the Stripe HTTP Request node and Stripe node use your Stripe credentials.
Step 4: Test the workflow
- In Pipedrive, change the “won time” of a deal.
- Check that the workflow runs in n8n and creates or finds a customer in Stripe.
Step 5: Activate for production
- Toggle the workflow on using n8n’s activation button.
- Monitor execution logs for errors.
- Option to set retry rules for failure handling.
Using the workflow import is easier than building from scratch.
For hosting needs, use self-host n8n.
Common customization ideas
- Add phone number from Pipedrive organization to Stripe customer.
- Send Slack message to sales team after new customer creation.
- Filter deals by a certain pipeline ID before running customer creation.
- Log created customer details with a Code node using JavaScript.
Handling errors and edge cases
- If the Pipedrive Trigger node never gets data, check if the webhook is active.
- If Stripe API returns 401 Unauthorized, double-check Stripe API Key and permissions.
- If the If node comparing won times acts wrong, verify JSON path and expression syntax.
- Be careful with address mapping. Missing street or city can cause Stripe creation to fail.
Summary of results
✓ Avoid manual customer creation in Stripe.
✓ Stop duplicate customers in billing.
✓ Keep Pipedrive and Stripe data in sync.
✓ Faster and accurate invoice processing.
➔ More time for sales and less billing errors.
