Sync payment and customer data between Stripe and Pipedrive
Needs changesNeeds changes. This template uses 3 thing(s) that n8n 3.0 removes: Function Item (legacy), Item Lists (legacy), Cron. 3 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 11 nodes and runs on a schedule (legacy Cron node). Along the way it connects Stripe and Pipedrive. It also calls api.stripe.com over HTTP.
How it runs
Trigger: On a schedule (legacy Cron node).
- Get last execution timestamp (Function Item): runs custom JavaScript per item (legacy Function Item node)
- Search for charges in Stripe (HTTP Request): calls api.stripe.com
- Split array of charges to items (Item Lists): reshapes item lists (legacy Item Lists node)
- Add customer name to charge data (Merge): merges the data from its input branches
- Search organisation (Pipedrive): search (organization)
- Add organisation Information to charge data (Merge): merges the data from its input branches
- Create note with charge information (Pipedrive): work with note
- Set new last execution timestamp (Function Item): runs custom JavaScript per item (legacy Function Item node)
- Get customers (Stripe): get many (customer)
- Rename fields and keep only needed fields (Edit Fields (Set)): sets or maps fields
Services it uses
HTTP calls to: api.stripe.com
Before you upgrade to n8n 3.0
3 things in this workflow are removed in n8n 3.0. Fix them before you upgrade:
- Function Item (legacy) in Get last execution timestamp, Set new last execution timestamp: replace with Code node, mode 'Run Once for Each Item'.
- Item Lists (legacy) in Split array of charges to items: replace with Split Out, Aggregate, Sort, Limit, Remove Duplicates or Summarize (match the operation used).
- Cron in Every day at 8 am: replace with Schedule Trigger.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Function Item (legacy) Get last execution timestamp, Set new last execution timestamp | Code node, mode 'Run Once for Each Item' |
| Item Lists (legacy) Split array of charges to items | Split Out, Aggregate, Sort, Limit, Remove Duplicates or Summarize (match the operation used) |
| Cron Every day at 8 am | Schedule Trigger |
Nodes used (8)
- Stripe
n8n-nodes-base.stripe - Edit Fields (Set)
n8n-nodes-base.set - Merge
n8n-nodes-base.merge - Pipedrive
n8n-nodes-base.pipedrive - Function Item
n8n-nodes-base.functionItem - Item Lists
n8n-nodes-base.itemLists - HTTP Request
n8n-nodes-base.httpRequest - Cron
n8n-nodes-base.cron
From the author
This workflow combines customers' details with their payment data and passes the input to Pipedrive as a note to the organization. Prerequisites - Stripe account and Stripe credentials - Pipedrive account and Pipedrive credentials How it works 1. Cron node…