Pipedrive
Your customer connects their Pipedrive account once and Askel handles the rest. Deals, contacts, organizations, and activity history flow between Pipedrive and your product without any custom sync code on your side.
What you can do
Sync deals into your product automatically
When a deal moves to a target stage in Pipedrive, Askel creates or updates the matching record in your product. No polling scripts, no fragile webhooks you own.
Read custom fields and pipeline stages
Every Pipedrive account has its own field layout. Askel discovers the customer's custom fields and pipeline stages at connect time and presents them for mapping.
Write data back to Pipedrive records
Push status updates, invoice amounts, or onboarding milestones back to a deal or contact in Pipedrive so the sales team always sees current state.
Create activities and notes on trigger
Log a Pipedrive activity or attach a note to a deal when something meaningful happens in your product, keeping the CRM timeline accurate.
Handle multiple pipelines per customer
Customers with separate sales and renewal pipelines can wire each one independently. Askel keeps the mappings distinct and routes data to the right pipeline.
Audit every operation end to end
Every Pipedrive API call Askel makes is logged with the input, the resolved mapping, the response status, and the workflow that triggered it.
Onboarding a customer whose sales team tracks deals in Pipedrive
You sell project-management software to creative agencies. Westwind Creative, a new customer, closes all their client engagements as deals in Pipedrive. When a deal moves to the Won stage, your product needs to create a new project and send the client a kickoff email. Any project status changes your product records should also appear as a note on the originating deal.
- 1
Connect once
Westwind's admin clicks Connect Pipedrive inside your product. The OAuth consent screen opens on Pipedrive's site, they approve the requested scopes, and Askel stores the token. Nothing touches your servers.
- 2
Discover the pipeline
Askel pulls Westwind's deal stages, custom fields (Client Budget, Service Type, and Kickoff Date are visible immediately), and organization records. A mapping draft appears for your team within a few minutes.
- 3
Map custom fields
Your customer-success rep confirms that Client Budget maps to your project budget field and Kickoff Date maps to your project start date. One unlabeled field gets flagged and Westwind's ops lead clarifies it on a quick call.
- 4
Dry-run with recent deals
Askel replays the last 20 Won deals in read-only mode, showing which projects would have been created and which fields would have been populated. Westwind confirms the output looks right.
- 5
Go live
The workflow turns on. Won deals now create projects in your product automatically, and project status updates write back to the deal in Pipedrive as a timestamped note.
OAuth 2.0
Customer's admin clicks Connect inside Askel and approves scopes on Pipedrive's consent screen, or pastes a Pipedrive API token from the personal preferences page. Askel stores credentials securely and never exposes them to your servers.
How Askel sits between your product and the customer's system
FAQ for Pipedrive
Does Askel support multiple Pipedrive pipelines from one customer?+
What happens if the customer renames a deal stage or adds a custom field after go-live?+
Can we use an API token instead of OAuth?+
Which Pipedrive plans are supported?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.