Skip to content
Supportqutee.aiOpen app

Send call data via webhook after every call

Set up a webhook for an agent so qutee sends the call data as JSON to your system after every call, for example to n8n, Make or Zapier.

With a webhook, qutee sends the call data to an address you choose after every call of an agent. That way tools like n8n, Make or Zapier, or your own system, can react to new calls automatically, for example by creating a record or sending a message.

  • You need the Company Admin role. Other roles don’t see the Webhook tab.
  • Webhooks are part of the integrations and are available depending on your plan. If the webhook isn’t included in your plan, you can set it up, but it only sends after an upgrade. The app then shows the note “Your plan does not include integrations. The webhook only sends after an upgrade.”
  • You need a receiving address (URL) that is publicly reachable over HTTPS, for example the webhook trigger of an n8n, Make or Zapier workflow.
  • A webhook applies to one agent. If several agents should send, set it up for each agent.
  1. Open Agents and select the agent at the top.
  2. Open the Webhook tab.
  3. Under Webhook URL, enter your receiver’s address. It must start with https:// and point to a public address. Redirects are not followed.
  4. Leave Webhook active checked.
  5. Decide whether Include the transcript stays checked. If it does, every message also contains the transcript of the conversation. The transcript is only sent if it is unlocked for your company, depending on your plan.
  6. Click Set up webhook.
  7. The app shows your Signing secret. Click Copy secret and store it in your receiver. The secret is shown only this one time.
  8. Click Done.

From now on, after every call of this agent, qutee sends a message to your URL as soon as the summary, tags and captured information are ready. This usually takes a short moment after the call ends.

Each message is an HTTP POST with a JSON body. It contains the call’s data, including the Summary, the tags, the Captured information and, if switched on, the transcript.

The easiest way to see the exact structure is Send test (see below): the test message has the same structure as a real one, but contains sample data and is marked as a test.

  1. In the Webhook tab, click Send test. If you changed something before, save first with Save.
  2. The app shows the result, for example “Test delivered: your server answered with HTTP 200” or “Test not delivered” with the reason.

In n8n, Make or Zapier you can use the test message to map the fields for your workflow.

So your receiver can be sure a message really comes from qutee, every message is signed. The signature follows the open Standard Webhooks specification, for which ready-made libraries exist in many programming languages. Every message carries three headers:

Header Meaning
webhook-id Unique ID of the event. It stays the same across retries, so you can detect duplicate deliveries.
webhook-timestamp Send time in Unix seconds. Reject messages that are older than five minutes.
webhook-signature v1, followed by the Base64-encoded HMAC-SHA256 signature of id.timestamp.body. The key is the Base64-decoded part of the secret after whsec_.

You also find this information in the app in the Webhook tab under Verify the signature, and retries.

If you lost the secret or suspect someone knows it, click Renew secret. The current secret then stops working immediately. Until you have stored the new secret in your receiver, your receiver rejects the messages.

Your receiver must answer with a 2xx status within 10 seconds. Otherwise qutee tries up to five more times: after 1 minute, 5 minutes, 30 minutes, 2 hours and 8 hours. As a result, a message can arrive more than once. Detect duplicates by the webhook-id.

In the Webhook tab you see:

  • Last successful delivery and Last failure for real calls (test messages don’t count here),
  • the Delivery log of the last 30 days with Time, Event, Status, Attempts and Response. With Send again you send an event once more, with the current call data and the same ID.

qutee switches the webhook off itself if several calls in a row could not be delivered or your server answers with HTTP 410. The app then shows the reason. Check your receiver and check Webhook active again afterwards.

  • Pause: Uncheck Webhook active and click Save. qutee doesn’t send anything later for calls during this time.
  • Remove: Click Remove webhook and confirm. qutee no longer sends calls of this agent, and open retries are cancelled.

“The URL must start with https://.”: Unencrypted http:// addresses are not allowed.

“The URL must point to a public address. Internal addresses are not allowed.”: qutee only sends to addresses that are reachable from the internet. A server in your company network needs a public address, for example through a reverse proxy.

“Your server answered with a redirect.”: Enter the final address your server redirects to.

The test arrives, real calls don’t: Check whether Webhook active is checked and whether your plan includes integrations. The Delivery log shows the reason for events that weren’t sent.

Was this page helpful?