Sync Pipedrive Product Creation to Stripe - n8n Workflow

• Sales Operations teams requiring automatic product synchronization.


• SaaS businesses or e-commerce platforms using Pipedrive as their CRM and Stripe for billing.


• Operations specialists looking for ready-to-use n8n templates to streamline financial data consistency.


• Users seeking an efficient n8n workflow to eliminate manual data entry between systems.

Maintaining consistency between CRM records and payment gateway data is crucial but often time-consuming. This powerful n8n workflow solves the problem of manual synchronization by instantly pushing newly created Pipedrive products to Stripe. When your sales team creates a new product offering in Pipedrive, this automation ensures the corresponding product entry and associated price tiers are immediately available in Stripe for invoicing and subscription management. By deploying this n8n automation, you ensure accuracy, accelerate your sales cycle, and free up team resources previously spent on manual double-entry. This is one of the most practical n8n templates for integrating sales and finance systems.

This synchronization process begins with a specific n8n trigger listening for events in Pipedrive.

1. Pipedrive Trigger: The n8n workflow starts when the Pipedrive Trigger detects that a new product has been added.


2. Data Transformation: A Function Item n8n node cleans the incoming Pipedrive webhook data, ensuring only the current product details are passed forward.


3. Stripe Product Creation: An HTTP Request n8n node sends a POST request to the Stripe API, using the product name and description to create the primary product entry in Stripe.


4. ID Capture: A Set n8n node captures the newly generated unique Product ID from Stripe, which is essential for attaching prices later.


5. Data Merge: A Merge n8n node combines the original Pipedrive data with the new Stripe Product ID. This step is crucial as the price information (currency, amount) is typically in the original Pipedrive payload, but the price must reference the new Stripe ID.


6. Price Itemization: An Item Lists n8n node splits the price array (assuming a product can have multiple price points) into separate items, preparing them for individual price creation API calls.


7. Stripe Price Creation: Finally, another HTTP Request n8n node iterates through the itemized prices, creating the necessary price records in Stripe using the extracted currency, unit amount (multiplied by 100), and the linked Stripe Product ID. This complete n8n workflow ensures a seamless end-to-end sync.

To deploy this n8n workflow, follow these steps:

1. Import the n8n template: Copy the provided JSON and import it into your n8n instance.


2. Pipedrive Credentials: Locate the Pipedrive Trigger n8n node and ensure you have established a connection credential for your Pipedrive account.


3. Stripe Credentials: Provide your Stripe API Key credential. This is required for both HTTP Request n8n nodes responsible for creating products and prices.


4. Activate the Trigger: Ensure the Pipedrive Trigger n8n node is active and configured to receive webhooks from Pipedrive for 'product added' events.


5. Customization (Optional): If your Pipedrive fields for price, currency, or description differ, review the Query Parameters in the HTTP Request n8n nodes ('Create product in Stripe' and 'Create price records in Stripe') and update the expressions to match your data structure.


6. Activate the n8n workflow: Set the n8n workflow to active to begin automatic synchronization.

On product created (Pipedrive Trigger): This n8n trigger initiates the entire process whenever a 'product' is 'added' in Pipedrive. It is the starting point for this synchronization n8n workflow.
Set item to only current product data (Function Item n8n node): Cleans the data structure received from the Pipedrive webhook, focusing only on the item.current object to streamline subsequent operations.
Create product in Stripe (HTTP Request n8n node): Connects to the Stripe API using a predefined credential. It uses a POST request to define the new Stripe product, mapping the name and description from the Pipedrive data.
Keep only productId of created product (Set n8n node): Isolates the crucial Stripe ID ($json["id"]) returned after product creation and names it StripeCreatedProductId. This is vital for linking the prices correctly.
Add created product Id to data (Merge n8n node): Combines the original Pipedrive data (which contains price details) with the newly acquired Stripe Product ID, preparing the data for price record creation.
Split prices to seperate items (Item Lists n8n node): Takes the prices array from the Pipedrive data and splits each price entry into its own individual item. This allows the final Stripe API call to be executed once per price point.

• Create price records in Stripe (HTTP Request n8n node): The final n8n node. It sends POST requests to Stripe to create the price objects, dynamically mapping the currency, unit_amount (multiplied by 100), and referencing the StripeCreatedProductId provided earlier in the n8n workflow.