Webhooks
Ask your AI assistant to set up webhooks that send call results, transfers, bookings and opt-outs to your CRM, Zapier or any other system.
What a webhook is, creating one for completed calls with a bearer token, choosing which intro it applies to, mapping a value from the response back onto the contact, and checking the last response.
A webhook sends data from Bigly to another system the moment something happens: a call completes, a call is transferred, a meeting is booked, or a contact opts out. Use webhooks to push results into your CRM, a Zapier zap, or your own server.
These are the webhooks on AI › Webhooks in the app. Your assistant can list them, read one in full, create new ones, edit them and delete them.
List our webhooks and show me the last response from each. Create a webhook that posts completed calls to https://hooks.example.com/bigly with a bearer token. Turn off the Zapier transfer webhook. When our CRM replies with data.crm_id, save it on the contact's Website field.
Before you start
- Connect your AI assistant to Bigly.
- You need permission to read webhooks to see them, and permission to update webhooks to create, change or delete one. Account owners and admins have both by default.
- Have the address (URL) you're sending to, and any username, password or token it needs.
What the assistant reads
- List: every webhook with its number (ID), name, type, status and URL, newest first.
- Read one: every setting of a single webhook, plus the last response your server sent back. This is useful for checking that it works.
Passwords, tokens and secret header values come back masked as ***. The assistant can see that one is set, but not what it is.
Create or change a webhook
- Describe the webhook or the change. To edit, name the webhook. Without a name, the assistant creates a new one.
- The assistant shows a preview. It says whether this will create or update a webhook and lists each field with its current value and its new value.
- Confirm in the chat.
When editing, the assistant sends the webhook's full setup, not just the field you changed. It reads the webhook first so nothing else changes. To keep a password or token as it is, it sends back ***, and the saved secret is kept. That only works while the auth type stays the same: if you switch auth type, give the new credentials.
A Claude conversation previewing a new Bigly webhook named CRM call results: type Call Completed, status Active, method POST, auth type Bearer with the token masked, and the target URL, with a request to confirm.
Settings explained
| Setting | On screen | Accepted values |
|---|---|---|
Name (name) | Name | Required. Up to 255 characters. |
URL (url) | URL | Required. A public http or https address. |
Type (type) | Type | Call Completed, Call transferred, Meeting Booked, Contact Opt Out or On Demand |
Intro (ai_intro_id) | Intro | Optional. Limits a call webhook to calls using one of your intros. |
Status (status) | Status | Active or inactive |
Auth type (auth_type) | Auth Type | None, basic, bearer or custom |
| Username and password | Username, Password | Required for basic auth |
| Bearer token | Bearer Token | Required for bearer auth |
| Header name and value | Header Key, Header Value | Required for custom auth |
Custom headers (custom_headers) | Custom Headers | Extra headers sent on every call. Header names can't contain spaces. |
Method (method) | Method | POST or GET |
Query and body (query, body) | Query, Body | Optional. Must be valid JSON. |
Required fields (required_fields) | Required Fields Before Post | Comma-separated fields. If one is missing, Bigly doesn't send the webhook. |
Response mapping (response_mapping) | Response Mapping | Up to 50 rules that copy a value from your server's JSON reply onto the contact |
Response mapping
Each rule has a path into your server's reply and a contact field to save it to:
- The path uses dots, like
data.crm_id. For lists, give the position, likedata.0.call.id. A path that points at a whole list is ignored. - The field must be a contact field you can write to, such as First Name, Email or Website, or one of your custom attributes.
- Mapping only runs when your server answers with success and JSON.
Limits and rules
- The URL must reach a public address. Private or internal network addresses are rejected.
- Name, URL, type, status, auth type and method are required every time.
- An intro must be one of your own intros.
- Query and body must be valid JSON, or the preview shows an error.
Delete a webhook
Ask the assistant to delete a webhook by name. It asks you to confirm first. If an AI agent tool sends to this webhook during calls, update Tools configuration too.
What you can't do here
- Trigger a webhook by hand. On Demand webhooks are sent through the Bigly API or by the agent during a call, not from the MCP. See API keys and Tools configuration.
- Clone a webhook. Cloning is in the app. To copy one here, ask the assistant to read it and create a new one with the same settings.
- Receive leads. Webhooks send data out. To send leads into Bigly, see Lead webhooks.