Pipedrive connects through Edesy workflow integrations. After each call, a workflow CRM update step writes the outcome, summary and extracted fields to Pipedrive. A CRM webhook trigger can start calls from Pipedrive events. There is no Pipedrive Marketplace app.
CRM update
Webhook trigger
Fields
Functions
Built with Edesy workflow integrations
A workflow step pushes the call outcome, summary and extracted fields to Pipedrive.
A CRM webhook trigger starts a workflow, and its voice call step calls the person.
Log the call with its summary and transcript link through the workflow.
Use workflow conditions on the call outcome to decide the next step for the deal.
Add SMS, WhatsApp, email or a callback after the call in the same workflow.
Add a custom HTTP function to the Pipedrive API if the agent needs live deal data.
What workflow integrations can do with Pipedrive
Better together
Auto-Logged Calls
Every call in activity feed
Deal Automation
Updated by workflows
Full Context
AI knows lead history
Less Admin
Focus on closing deals
Complete Visibility
All calls logged
Accurate Forecasts
Outcomes logged after each call
Team Efficiency
More calls, less admin
Quality Insights
Call transcripts available
Through Edesy workflow integrations
Add it from the CRM integrations catalog
Trigger on call ended or data extracted
Choose which call data goes to Pipedrive
Run a test call and check the record
What is real today, in one table
| Item | Details |
|---|---|
| Connection type | Edesy workflow integrations (CRM update step, CRM webhook trigger) |
| After the call | Outcome, summary and extracted fields pushed to Pipedrive |
| Starting calls | CRM webhook trigger, REST API, Zapier or n8n |
| During the call | Optional custom HTTP function to the Pipedrive API |
| Marketplace app | None |
Common questions about connecting Pipedrive
Through Edesy workflow integrations. A workflow CRM update step writes call results to Pipedrive, and a CRM webhook trigger can start calls. Mid-call lookups need a custom HTTP function.
Yes, if Pipedrive sends a webhook on the stage change. The CRM webhook trigger starts an Edesy workflow that places the call.
No. Calls run on Edesy telephony (Twilio, Exotel, Plivo, Vobiz, SIP trunk or Edesy-managed numbers).
Yes, by mapping an extracted field to the deal in the workflow CRM update step.
Extracted fields can be mapped to the Pipedrive fields your workflow integration exposes.
No. Pipedrive is connected from the Edesy dashboard through workflow integrations, not a Marketplace app.
Other CRMs Edesy connects with
Send call results to Pipedrive with Edesy workflow integrations.
Real demo calls showcasing low latency and natural conversations in multiple Indian languages
AI voice agent qualifying B2B leads for corporate gifting. Ultra-low latency with 1-2 second response time. Bilingual conversation in Hindi and English.
Audio player powered by Google Drive
Open in DriveAI voice agent handling admission inquiries and appointment booking for educational institutes in Malayalam language.
Audio player powered by Google Drive
Open in DriveAI voice agent handling admission inquiries and appointment booking for educational institutes in Tamil language.
Audio player powered by Google Drive
Open in DriveAI voice agent qualifying leads for solar installation company in Assamese language. Natural conversation flow with product inquiry handling.
Audio player powered by Google Drive
Open in DriveAI voice bot helping patients book hospital appointments in Bengali. Natural conversation with availability checking and confirmation.
Audio player powered by Google Drive
Open in DriveAI voice bot helping patients book hospital appointments in Hindi. Handles doctor selection, time slot booking, and confirmation.
Audio player powered by Google Drive
Open in DriveAI voice bot helping patients book hospital appointments in Telugu. Natural conversation flow for healthcare scheduling.
Audio player powered by Google Drive
Open in DriveBest AI voice agent pricing worldwide - from ₹4/min ($0.04) | 40% more affordable than US alternatives