> For the complete documentation index, see [llms.txt](https://docs.voiceb.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voiceb.ai/webhook-call-outcome-integration.md).
# Webhook β Call Outcome Integration
## VoiceB.ai Webhook β Call Outcome Integration
Webhooks let you receive structured call outcomes, transcripts, and lead data after every call. Use this to:
* Save conversations to your database
* Trigger follow-ups or automations
***
### π How it Works
1. Configure your webhook URL in **Settings β Integrations**
2. Optionally enable **signature signing** for secure verification
3. VoiceB will POST call result data in real-time
***
### How to Add a Webhook Integration
1. **In your VoiceB account**, go to **Campaigns**.
2. Select the **Agent** you want to configure.
3. Once inside the **Agent Config** (Name, AI Provider, Goal, Scriptβ¦), scroll down to **Integrations**.
4. Click on the **β+β** button.
5. Choose **Webhook** from the list.
6. You will now see the configuration screen with instructions and examples.
***
### π¬ Sample Webhook Payload
```json
{
"agent": "AgentName",
"from": "+1234567890",
"to": "+0987654321",
"status": "SOLD",
"transcript": [...],
"collectedData": {
"name": "John Doe",
"email": "john.doe@example.com",
"address": "Calle Ejemplo 123, 45678, Ciudad"
}
}
```
***
### π‘οΈ Signature Verification (Optional)
Header:
```ini
Authorization=Bearer XXXXXXXXXXXXXXXXXX
x-webhook-signature=YYYYYYYYYYYYYYYYYYY
```
Use your **signature secret** to verify the authenticity of the payload.
***
### Trigger Conditions
By setting trigger conditions, you can define specific outcomes that will determine if the integration runs for that call or not. Allowing you to determine which ones ends in your system/CRM
### π§° Error Codes (Same as API)
***
If you need help setting this up, reach out to
Would you like a diagram to visualize the full API/webhook data flow?
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.voiceb.ai/webhook-call-outcome-integration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.