Connect Pipedrive and Airtable
Close the deal in Pipedrive, run the work in Airtable, and keep both honest.
Connecting Pipedrive to Airtable automates the handoff from a won deal to delivery, and reports progress back into the CRM. The awkward part is Pipedrive’s custom fields: they are addressed by generated hash keys rather than names, so integrations built against field labels break the moment a field is edited.
Why the obvious approach breaks
A one-step zap will connect Pipedrive and Airtable in an afternoon. Here is what tends to go wrong once real volume and real edge cases arrive.
Custom fields are hash keys, not names
Pipedrive exposes custom fields as generated hash identifiers. Integrations mapped against display names break silently when a field is renamed or recreated, and the failure looks like empty data rather than an error.
Pipeline stages are IDs that get reordered
Stage IDs are stable but the pipeline they belong to is not. Teams reorder and rename stages regularly, so logic keyed to stage position rather than ID misfires after any pipeline edit.
Deal, person and organisation are separate objects
A handoff needs all three plus their relationships. Fetching only the deal produces a delivery record missing the contact details the delivery team actually needs.
Won is not always the right trigger
Deals get marked won prematurely, then reopened. Firing delivery setup on the status change alone creates projects that should not exist, so a confirmation step or delay is usually warranted.
The actual data flows
Deal marked won in Pipedrive
Create the delivery project in Airtable with contact, organisation and deal value
Delivery status updated in Airtable
Write a note or custom field back to the Pipedrive deal
Person or organisation updated in Pipedrive
Sync to the linked Airtable records, matched on Pipedrive object ID
Project completed
Log the activity and create the renewal opportunity
Common Use Cases
- Automatic delivery setup on deal close
- Sales visibility into delivery without CRM seats for the delivery team
- Reporting joined across pipeline and delivery
- Renewal opportunities created from delivery milestones
Typical Stack
- Pipedrive API
- Pipedrive webhooks
- Airtable API
- Make.com
- n8n
Pipedrive and Airtable, answered
How do you handle Pipedrive custom fields safely?
We resolve field hash keys at build time and store the mapping explicitly, rather than matching on labels. We also validate the mapping on each run, so a renamed or deleted field raises an alert instead of quietly syncing blanks.
Can we trigger on something other than deal won?
Yes. Any stage change, activity, or custom field update can be the trigger. In practice a short delay or an explicit confirmation field is safer than firing on won, because deals do get reopened.
Is this different from Pipedrive’s own automations?
Pipedrive automations work well inside Pipedrive. They cannot create structured, linked records in Airtable or handle retries across systems, which is where a dedicated integration layer earns its place.
Related integrations
Need a different pair?
These are the integrations we are asked for most, but the approach is the same for anything with an API. Tell us what you are trying to connect and we will tell you honestly whether it needs a custom build or an off-the-shelf tool will do.
Claim a Free Workflow Audit