Callingtap Logo
Callingtap

Integrations · Automation

MakeMakeAvailable via Webhooks + API

Call started, completed, failed, appointment booked — every event fires your Make scenarios.

Make connects to Callingtap through webhooks — the mechanism that already powers Callingtap's automation layer. When a call starts, completes or fails, or an appointment is booked, Callingtap POSTs a signed JSON event to your Make scenario's custom webhook URL, and your scenario can then update a CRM, send a message, write to a sheet or anything else Make can do.

There is no native Make connector inside Callingtap, and we won't pretend otherwise: the webhook path is the integration. It is also genuinely powerful — payloads are HMAC-SHA256 signed so your scenario can verify they came from Callingtap, follow-up automations can fire webhooks after calls, and Make can call back into Callingtap's API to trigger new calls from other systems.

What you can do

  • Call events delivered to a Make custom webhook: call.started, call.completed, call.failed and appointment.booked
  • Follow-up automations that fire a webhook when a call outcome matches your rules
  • Signed payloads (HMAC-SHA256) with a per-endpoint secret for verification
  • Every webhook delivery logged in your dashboard, so failed deliveries are visible, not silent
  • Two-way flows: Make scenarios can call the Callingtap API to launch calls from external triggers

Ready to connect it?

Create a workspace and connect Make from your dashboard — integrations run on your own accounts and keys, encrypted at rest.