Question:
Is it possible to re-trigger or request a previously transmitted webhook transmission?
Answer:
Currently, it’s not possible to resend or re-trigger a webhook transmission once it has been executed. A webhook is only sent after all analyses on a specific conversation are completed. If you have a specific use case that requires multiple transmissions, please let us know — we’re happy to explore a potential solution.
Question:
Can we limit which meetings trigger a webhook transmission (e.g., only selected or filtered meetings)?
Answer:
At the moment, webhook transmissions can only be turned on or off for the entire organization. However, we’re actively working on adding filtering options that will allow you to define which meetings trigger a webhook. This feature is planned to be available by the end of the year.
Question:
Can meetings or transmissions be classified and this classification included in the webhook JSON?
Answer:
Yes. You can add a new AI analysis of type "Picklist" to classify your meetings. This classification can then be included in the webhook payload. Our team can support you in setting this up — please contact us if you’d like assistance.
Question:
Why is there a difference between the summary shown in the app and the content sent in the webhook?
Can we access the summary content via the API?
Answer:
The summary displayed in the Bliro app is included in the webhook payload under callData.summaries. Each entry contains a sections array, where every section has a label, a value array of strings, and a format (e.g. bullet_points, check_list). Currently, there is no separate API endpoint for summaries — they are accessible through the transmitted webhook payload.