Synova Connect

Custom webhooks

Send post-call data to any URL with a webhook so you can push call summaries and caller details into your own systems.

Send post-call data to any URL after your AI receptionist finishes a call. Use webhooks to push call summaries, caller details, and other data to your own systems or third-party tools.

Plan availability. Custom webhooks require Professional ($299/mo) or Enterprise ($599/mo); they are not included with Starter ($99/mo).

Prerequisites

  • A Synova Connect account with an active receptionist
  • A server or service that can receive HTTP requests at a publicly accessible URL

How it works

After every call, Synova sends an HTTP request to the endpoint you configure. The request contains structured data about the call, including the caller's information, call summary, and any data collected during the conversation.

Adding a webhook

  • Open your Synova Connect dashboard and navigate to the Overview page.
  • Scroll to the Post-Call Webhook section.
  • Click the Add button to open the webhook form.
  • Set Method — choose the HTTP method for the request: POST, PUT, or PATCH.
  • Set Endpoint — enter the full URL where Synova should send the data (e.g., `https://example.com/webhook`).
  • Click Save to activate your webhook.

The endpoint must be a valid URL.

Viewing your webhook

Once saved, the webhook card displays the Method (the HTTP method you selected) and the Endpoint (the URL receiving the data).

Editing a webhook

  • Click the Edit button on the webhook card.
  • Update the Method or Endpoint as needed.
  • Save your changes.

Deleting a webhook

  • Click the Delete button on the webhook card.
  • Confirm the deletion when prompted.

A success message confirms: "Webhook deleted successfully!"

Use cases

  • Push call data to a CRM that is not natively supported
  • Log calls in a custom database or spreadsheet
  • Trigger internal workflows in tools like n8n, Make, or your own backend
  • Feed call summaries into a reporting dashboard

Troubleshooting

  • Invalid endpoint URL — make sure the URL starts with `https://` and is publicly accessible.
  • No data received — verify your server is listening on the correct path and returns a 200-level status code. Check your server logs for incoming requests.
  • Webhook not firing — ensure the webhook is active (visible on the card). If you recently added it, try making a test call to trigger the delivery.