Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Webhooks

Receive transcripts and agent outputs automatically in your own tool through webhooks.

A webhook sends a call's data to the address of your choice as soon as it is ready. Use it to feed a tool Praiz does not integrate with, or an automation (Make, Zapier, n8n).

Before you start

  • Be a Praiz admin.

  • A URL that can receive HTTP requests: a Make or Zapier scenario, an n8n workflow, your own server.

Praiz does not expose a public API. Webhooks and the MCP server are the two ways to access the data.

Create a webhook

  1. Open "Settings", "Webhooks" tab.

  2. In "Webhook URL", paste the address that will receive the data.

  3. Choose the "Webhook type": "Agent" or "Transcript".

  4. Click "Add webhook".

What to expect: the webhook appears in the list with its type and a token. Click "Show" to display the full token. Click "Delete" to remove the webhook.

Webhooks tab in Settings

The two webhook types

Type
What is sent
When

"Agent"

The fields your agents extracted on the call, with the call's metadata

When the agents have finished

"Transcript"

The raw transcript and the call's metadata

When the transcript is available

To send structured data to another tool, choose the "Agent" type. This type requires configured agents. An "Agent" webhook can be limited to certain agents: only the outputs of those agents then trigger the request.

Check where requests come from

Every request Praiz sends carries the HTTP header Authorization: Bearer <token>. The token is generated once, when the webhook is created, and shown in the list ("Show"). To check that a request really comes from Praiz, compare the token received in the header with the one shown in the interface. The request body is not signed.

Special case: if your URL already contains a sig= parameter (Power Automate, Logic Apps), Praiz does not send the Authorization header, to avoid an authentication conflict.

What Praiz sends

Every request contains a request identifier (request_id, different for each request), the date, and a video object: id, title, duration, user email, source, transcript link, call link, creation date, and the list of participants with their CRM identifiers if any. The "Agent" type adds a template object with the extracted fields.

Example of an "Agent" request:

Good to know about this format:

  • extracted_value is a string, a list (multi-option or bullet-point fields) or a boolean, depending on the field's format.

  • A field with no extracted value does not appear in the request.

  • A participant's crm_* fields are empty when the participant is not found in the CRM.

  • A "Transcript" request contains the same video object, without the template object.

The request arrives a few seconds to a few minutes after the end of the call.

Test a webhook

Create a webhook to a test address (for example webhook.site). Record a short call, then read the request received.

Troubleshooting

  • No request arrives: check the URL in the webhook list and test it with a test address.

  • The "Agent" webhook sends nothing: no agent applied to the call, or the webhook is limited to agents that did not apply. Check your agents' automation rules.

  • The request arrives without the expected fields: the webhook type is "Transcript". Create an "Agent" webhook.

Was this helpful?