Webhooks send your call, text, appointment and task details to another app the moment something happens in SkipCalls. Use them to post call summaries to Slack, get Telegram alerts, feed Zapier or Make.com, or send data to your own system.
Before you start
A SkipCalls Growth, Business or Enterprise plan. Webhooks are not included on Starter.
Where you want the data to go: a web address (URL) for your own system, Zapier or Make.com, a Slack or Discord webhook URL, or a Telegram bot token and chat ID.
Create a webhook
In the SkipCalls dashboard, open Integrations in the left menu and go to the Notifications (Webhooks) tab.
Click Create Webhook.
Integration: choose where to send notifications:
HTTP Webhook: send data to your own web address. You can pick the method (POST, GET, PUT or PATCH) and add custom headers.
Zapier: send data to a Zapier webhook URL. (You can also use the SkipCalls app in Zapier; see the Zapier article linked below.)
Make.com: send data to a Make custom webhook. You can add an optional signing secret.
Telegram: send calls, texts, appointments and customer file links to a Telegram chat.
Slack: post messages to a Slack channel.
Discord: post messages to a Discord channel.
Shopmonkey: create Shopmonkey appointments when your receptionist books one.
Endpoint: give the webhook a name and enter the destination details (URL, or bot token and chat ID for Telegram).
Events: pick what should trigger it (see the list below).
Delivery: optionally adjust:
Timeout and Retry Count (how many times to try again if your system doesn't respond; default 3, up to 10).
Agents: send events for all your receptionists (All agents, the default) or only the ones you choose.
Smart filter: describe in plain English which calls to send, and SkipCalls skips the ones that don't match. For example: "Only send calls where the caller wants a quote. Skip spam and wrong numbers."
Click Create Webhook.
Events you can choose
Outbound Calls
Started: your receptionist begins an outgoing call.
Achieved: an outgoing call ended and its goal was met.
Not Achieved: an outgoing call ended without reaching its goal.
Incoming Calls
Started: an incoming call connects to your receptionist.
Completed: an incoming call ended normally.
Error: an incoming call dropped or failed.
SMS
Received: a text message came in.
Sent: a text message went out.
Failed: a text message couldn't be delivered.
Tasks & Appointments
Booked: your receptionist scheduled an appointment.
Task Created: a follow-up task was created from a call.
Customer Files
Files Uploaded: a customer finished uploading files through a SkipCalls upload link. This event covers your whole account, not one receptionist.
What's included
Call events include the call details (status, length, times), the receptionist, the phone numbers, the summary, the full transcript, the recording link, any information your receptionist collected (Data Extraction), quality checks and follow-up tasks. Text, appointment and file events include the matching details.
For the exact data format of each event, open the Webhook Docs tab on the Integrations page.
Manage your webhooks
On the Notifications (Webhooks) tab you can see each webhook's status, events and when it last ran. From there you can:
Send a sample with Test webhook.
Turn a webhook on or off.
Edit or delete it.
Delivery and retries
If the receiving system is down or returns an error, SkipCalls tries again, waiting a little longer between each try. Your system should reply with a success response (status 200-299) within the timeout, which is 10 seconds by default. If processing takes longer, reply first and do the work afterwards.
Troubleshooting
Nothing arrives: make sure the webhook is turned on, the right events are selected, and the URL is reachable from the internet. Use Test webhook to check.
Some calls are missing: check whether the webhook is limited to certain receptionists, or whether Smart filter skipped them.
Testing your own endpoint: a free tool like webhook.site shows exactly what SkipCalls sends, without writing code.
Can't create a webhook: webhooks need the Growth plan or higher.