Send Call Details to Your Own Workflow
Send completed-call, lead, or appointment-request data to a public HTTPS endpoint your team controls, with an optional signature and tracked delivery attempts.
A saved endpoint is not proof of receipt. Verify the optional signature, handle duplicate attempts safely, and confirm a real event end to end.
- Call details
- Signed delivery
- Your endpoint
Structured call event
Example route
Call outcome
Lead captured
Booking requested
Summary complete
What this connection helps your team do
Start with the useful outcome. The setup steps and call trigger are explained below.
Send completed-call, captured-lead, or appointment-request events to a public HTTPS URL
Include available caller, lead, appointment, and call-summary data
Add an HMAC signature header when you set a signing secret
Send test deliveries and inspect tracked automation attempts
See Webhooks in a real workflow
These examples show the trigger, the action, and what your team can check afterward.
Operations intake
- Trigger: Lead Captured
- Action: POST the payload to the operations endpoint you chose
- Result: Your receiving system decides whether and how to assign the work
Custom CRM
- Trigger: Lead captured
- Action: Create/update a lead in your internal database
- Result: The receiving system records the lead if it accepts the request
Ops reporting
- Trigger: Call completed
- Action: Send the available summary and fields to a public ingestion endpoint
- Result: The receiving system can store the event under its own retention rules
Setup
HTTPS endpoint + test
- 1Add an endpoint URL and choose events
- 2Store the signing secret securely and verify the timestamped signature when it is set
- 3Send a test, confirm idempotent handling, then verify a real event
What data is included
Available fields for the selected event.
- Event envelope, timestamp, and related record identifiers
- Caller/contact fields
- Captured answers
- Available summary, captured urgency, and next-step fields
Connection control
Protect credentials and plan for failures.
- HTTPS is required and local or private-network destinations are rejected
- Optional HMAC signatures cover the timestamp and raw body
- Delivery attempts are tracked; receivers should tolerate duplicate retries
FAQ
Answers for this connection.
How do I verify events are real?
When you set a signing secret, verify the AnswerCheap signature over the timestamp and raw request body before processing the event.
Can I subscribe to multiple events?
Yes. A destination can select from the available call events, and you may use separate endpoints when isolation is easier to operate.
Do you retry failures?
Automation attempts are tracked and failed runs can be retried by the worker. Your endpoint must be idempotent because duplicate attempts can occur.
What if I’m not technical?
Use the Slack, Google Calendar, or HubSpot setup where it matches your need, or connect the webhook to Zapier or Make and test the mapping there.
The phone will ring
Make one connection useful first.
Choose the call event, captured fields, destination, and fallback. Then test the full route before adding another.
Prefer to explore? See all integrations or learn about features.