-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Description
Describe the event source. What app is this for, and what event does the trigger correspond to?
This request is for the Belco integration.
Currently, the Belco trigger(s) relies on polling-based triggers (e.g. polling for new conversations). However, Belco does support webhooks, even though creation of them is not clearly documented in their public API docs.
We would like the Belco integration to be updated to support subscription-based (webhook) triggers, enabling real-time event delivery instead of polling.
Specifically we would like triggers to be added for the following events:
- conversation.created
- conversation.replied
- conversation.note.added
- conversation.assigned
- conversation.closed
- conversation.reopened
Please provide a link to the relevant API docs for the specific service / operation this trigger is tied to
Belco’s webhook functionality is partially undocumented, but fully functional. Part of the documentation can be found here. The two additional undocumented routes, I have added below.
Create webhook (subscription)
POST https://api.belco.io/v1/webhooks
Authorization: Bearer
Content-Type: application/json
Request body:
{
"shopId": "<shop_id>",
"url": "<pipedream_webhook_url>",
"events": ["<event_string>"]
}
All possible events:
- call.created
- call.queued
- call.answered
- call.closed
- conversation.created
- conversation.replied
- conversation.note.added
- conversation.assigned
- conversation.closed
- conversation.reopened
- contact.created
- contact.updated
- contact.deleted
Multiple events can be subscribed to in a single webhook by passing multiple values in the events array.
Delete webhook (unsubscribe)
DELETE https://api.belco.io/v1/webhooks/{webhookId}
Authorization: Bearer
Additional notes
Although Belco does not officially document webhooks, they are stable and actively used in production.
New Actions
Metadata
Metadata
Assignees
Labels
Type
Projects
Status