Case Study
Make.com Pipedrive Disconnected Signal Handler
A Make.com scenario that responds to disconnected call signals, checks Pipedrive contact status, updates CRM records, creates notes, and alerts Slack channels.
Book a Systems ConsultationBusiness Context
CRM Operations Automation
This workflow handles disconnected call events by routing the webhook payload through Pipedrive lookup and update paths. It checks whether the person exists, updates phone status, creates CRM notes, and sends Slack messages to the correct channel so missed or disconnected call activity does not sit unnoticed.
The Workflow Problem
• Disconnected call activity needed to trigger an operational response
• Pipedrive records had to be checked before updating person status
• The team needed Slack visibility without manually inspecting every call event
System Built
Webhook Intake
Make.com receives the call disconnect event and starts the routing workflow.
Pipedrive Lookup
The scenario searches Pipedrive for the matching person record before applying updates.
CRM Update
Person phone status and CRM notes are updated depending on the route outcome.
Slack Alert
Slack messages notify the correct channel when call events need attention.
Operational Outcomes
• Disconnected call signals are captured from a Make.com webhook
• Pipedrive person records are searched and updated based on routing logic
• CRM notes and Slack alerts are created from the same operational path