Automated Stripe Payment Sync to Pipedrive CRM - n8n Workflow

Ideal Users for this Automation

Sales Operations Teams needing visibility into customer payments within their CRM.
Finance Managers who use Pipedrive to track sales history.
n8n Automation Specialists looking for sophisticated n8n templates involving state management (using Function nodes).
Anyone needing a reliable n8n trigger to run scheduled data synchronization between Stripe and Pipedrive.

Keeping CRM data current with financial transactions is crucial for sales visibility and account management. This n8n workflow solves the problem of manual data entry by automatically detecting successful payments in Stripe and logging them as notes in the corresponding Pipedrive organization record.

This specific n8n workflow demonstrates advanced techniques, including state persistence (using the Function n8n node to track the last execution time) and complex merging operations. By using an n8n trigger that runs daily, your Pipedrive records remain updated with the latest payment activities, ensuring that account managers have a complete picture of their clients' financial standing without leaving the CRM.

This n8n workflow executes through a precise, scheduled sequence:

1. Scheduled Execution: The automation starts via the 'Every day at 8 am' n8n trigger (Cron node).


2. State Retrieval: The 'Get last execution timestamp' Function n8n node retrieves the timestamp of the last successful run from the workflow's static data. If this is the first run, it defaults to the current time.


3. Retrieve Charges: An HTTP Request n8n node searches Stripe for all 'succeeded' charges created since the retrieved last execution timestamp.


4. Charge Itemization: The 'Split array of charges to items' n8n node splits the resulting charge array into individual items for parallel processing.


5. Retrieve Customers: Simultaneously, the Stripe n8n node fetches a complete list of all Stripe customers.


6. Customer Cleanup: A Set n8n node cleans the customer data, keeping only the Stripe customer ID and the customer name.


7. Data Merge (Stripe): The first Merge n8n node combines the individual charge items with the corresponding customer name using the customer ID as the merge key.


8. Pipedrive Search: The Pipedrive n8n node searches for the corresponding organization in Pipedrive using the customer name retrieved from Stripe.


9. Data Merge (Pipedrive): A second Merge n8n node combines the payment and customer data with the Pipedrive organization ID.


10. Action (Pipedrive): The final Pipedrive n8n node, 'Create note with charge information', uses the merged data to create a detailed note (including charge description, amount, and currency) attached to the correct Pipedrive organization.


11. State Update: Finally, the 'Set new last execution timestamp' Function n8n node updates the workflow's static data with the current execution time, setting up the foundation for the next run of this n8n workflow.

To deploy this synchronization n8n workflow, follow these steps:

1. Import: Copy the provided n8n workflow JSON data and paste it into your n8n instance via the 'New' menu -> 'Import from JSON'.


2. Stripe Credentials: Locate the 'Search for charges in Stripe' n8n node and the 'Get customers' n8n node. You must set up or select your existing Stripe API credentials.


3. Pipedrive Credentials: Locate the 'Search organisation' and 'Create note with charge information' n8n nodes. You must set up or select your existing Pipedrive API credentials.


4. Review Trigger: The 'Every day at 8 am' n8n trigger is set to run daily. Modify the schedule if needed.


5. Activate: Save and activate the n8n workflow to begin automatic synchronization.

This synchronization n8n workflow utilizes several key n8n nodes:

Every day at 8 am (Cron n8n trigger): This node schedules the execution of the n8n workflow daily at 8:00 AM.
Get last execution timestamp / Set new last execution timestamp (Function Item n8n node): These custom code nodes are critical for state management. They store and retrieve the lastExecution time in the workflow's static data, ensuring the next run only pulls newly created Stripe charges.
Search for charges in Stripe (HTTP Request n8n node): Connects to the Stripe API search endpoint, filtering for succeeded charges created after the timestamp stored by the Function n8n node.
Get customers (Stripe n8n node): Retrieves a complete list of customer records from Stripe, necessary to match charges back to a customer name.
Add customer name to charge data (Merge n8n node): Merges the stream of individual charges with the list of Stripe customers using the customer ID field.
Search organisation / Create note with charge information (Pipedrive n8n node): The first Pipedrive n8n node searches for the organization based on the customer name. The final Pipedrive n8n node creates the detailed payment note, linking it to the retrieved organization ID.