How to Create and Manage Webhooks in BoldDesk Tickets
Webhooks are user-defined HTTP callbacks that allow BoldDesk to send real-time data to external applications when specific events occur. They enable seamless integration with third-party APIs, automation platforms, and internal systems. When a ticket is created in BoldDesk, the ticket data is sent to a configured URL via an HTTP POST request.
Check out this video tutorial to learn more.
How to Create a Webhook
To create a webhook, follow these steps:
-
Go to Admin → Webhooks.
-
Click Add Webhook.
-
Fill in the following details:
-
Name & Description: Provide a clear identifier and purpose.
-
Module & Event: Choose the module (e.g., Tickets) and the event (e.g., Ticket Created).
-
Webhook Endpoint: Enter the target URL to receive data.
-
Request Type: Select from POST, PUT, PATCH, or DELETE based on the target API.
-
Authentication (optional): Enable to verify the sender.
-
Signing (optional): Enable to verify payload integrity.
-
Condition (optional): Define conditions for triggering the webhook.
-
Payload: Select the module data to include in the webhook.
-
-
Click Add to save the webhook.
- If the request type does not match the endpoint’s expected method, the webhook will fail. These failures are logged in Webhook Failure Logs under Audit Logs.
- BoldDesk webhooks support conditional triggering. You can use system fields and supported custom fields as webhook conditions to fire webhooks only when the specified field criteria are met.
- BoldDesk webhooks require an acknowledgment response within 10 seconds, and this timeout cannot currently be extended. To ensure reliable webhook delivery, store the webhook payload in a queue or database and immediately return an HTTP 200 OK response. The payload can then be processed asynchronously through a background job, allowing API calls, database updates, and other business logic to run without the 10-second time constraint. This is the recommended best practice for handling long-running webhook processes and preventing delivery failures.
How to Edit a Webhook
To update an existing webhook, follow these steps:
- Go to Admin → Webhooks.
- Locate the webhook in the list.
- Click the Edit icon.
- Update the necessary fields.
- Click Save.
Deleting a Webhook
If a webhook is no longer used, you can delete it from the webhook list page. To delete a webhook, follow these steps:
-
Click Admin > Webhooks.
-
Find the webhook on the webhook list page.
-
Click the Kebab icon (⁝) and select Delete.
-
Click the Yes, Delete button in the confirmation dialog to delete the webhook.
Deactivating a Webhook
If you don’t want to delete the webhook permanently or want to stop the webhook temporarily, you can deactivate the webhook from the active list. To deactivate the webhook, follow these steps:
-
Click Admin > Webhooks.
-
Select the Active tab on the webhook list page.
-
Find the webhook to deactivate.
-
Click the Kebab icon (⁝) and select Deactivate.
Activating a Webhook
You can activate a webhook that is deactivated from the inactive list.
To activate the webhook, follow these steps:
-
Click Admin → Webhooks.
-
Select the Inactive tab on the webhook list page.
-
Find the webhook to activate.
-
Click the Kebab icon (⁝) and select Activate.
How to Add Multiple Webhooks to a Single Brand
When a single Brand must send events to multiple destinations, create one webhook per destination and apply a Condition (Optional) on each webhook to scope it to that brand and the intended event pattern—so each webhook fires only for that brand. Manage creation and lifecycle in Admin > Webhooks (use Add Webhook to create; use the Active/Inactive tabs to enable, pause, or retire endpoints). To update an existing webhook, click its Edit (pencil) icon on the list and add the brand‑scoped Condition.
Use the following procedure when a single brand must deliver events to multiple destinations:
-
Go to Admin > Webhooks, then click Add Webhook or click the edit (pencil) icon to modify an existing webhook.
-
Scroll to Condition (Optional) and set the dropdowns to:
Brand > Is ><Your Brand>
-
After you’ve filled the other necessary/required sections, click Add or Update if you’re editing an existing webhook.
For the selected brand to deliver events to multiple destinations, perform steps 1–3 for each webhook you want to assign to this brand. Create/edit one webhook per destination and ensure the Brand condition is set on every webhook.
Plan‑Based Limits & Multibrand Availability
| Plan | Webhook Limit (per Organization) | Multi-brand Help Desk |
|---|---|---|
| Enterprise AI | Up to 10 webhooks | ✅ Available |
| Enterprise (Legacy) | Up to 10 webhooks | ✅ Available |
| Enterprise Non-AI | Up to 10 webhooks | ✅ Available |
| Momentum AI | Up to 5 webhooks | ❌ Not Available |
| Momentum (Legacy) | Up to 5 webhooks | ❌ Not Available |
| Scale AI | Up to 5 webhooks | ❌ Not Available |
| Scale (Legacy) | Up to 5 webhooks | ❌ Not Available |
Webhook limits are applied per organization, not per brand. Multi-brand Help Desk is available only on the Enterprise plan variants (Enterprise AI, Enterprise Legacy, and Enterprise Non-AI). Organizations requiring multiple brands and per-brand ticket routing must use an Enterprise plan.
Troubleshooting webhooks
Webhook is not triggering
- Confirm the webhook is Active (not listed under the Inactive tab).
- Confirm the webhook Module and Event match the action being performed (example: Tickets + Ticket Created).
- If Condition (Optional) is configured, confirm the event data matches the condition (example: the ticket Brand equals the configured brand).
Webhook is failing to deliver
- Confirm the Request Type matches what the destination endpoint accepts.
- Check Audit Logs > Webhook Failure Logs for the recorded failure.
- Confirm the destination endpoint returns an acknowledgment within 10 seconds.
- If processing is slow, implement the queue/database + immediate HTTP 200 OK pattern and process asynchronously.
Frequently Asked Questions
-
What is a webhook in BoldDesk used for?
A BoldDesk webhook sends event data to an external application when a configured event occurs, such as sending ticket data when Ticket Created occurs. -
Which HTTP methods can a BoldDesk webhook use?
BoldDesk webhooks support POST, PUT, PATCH, and DELETE. -
Where can administrators find webhook delivery failures?
Webhook failures are logged in Audit Logs → Webhook Failure Logs. -
Can a BoldDesk webhook trigger only for certain tickets?
Yes. Use Condition (Optional) to trigger only when field criteria match, including supported system fields and supported custom fields. -
Can a webhook condition use a ticket custom field?
Yes. BoldDesk supports using supported custom fields as webhook conditions. -
How long does the webhook endpoint have to respond?
The endpoint must acknowledge within 10 seconds, and the timeout cannot currently be extended. -
What is the recommended pattern for endpoints that need more than 10 seconds to process?
Store the webhook payload in a queue or database, immediately return HTTP 200 OK, and process the payload asynchronously in a background job. -
Are BoldDesk webhook events counted toward BoldDesk API hourly rate limits?
No. Webhooks sent by BoldDesk are not counted toward API hourly rate limits. Rate limits apply to API requests initiated by your side to BoldDesk REST APIs.