Skip to main content

Webhooks

What you'll learn
  • What webhooks are and how they work in AutoTalk
  • How to create and manage webhook endpoints
  • Common use cases for outgoing webhooks

Webhooks send real-time notifications to external services when events happen in AutoTalk. Instead of repeatedly checking AutoTalk's API for new data, your external system receives an automatic notification the moment something happens, such as a new message arriving or a contact being updated.

You manage webhooks from the Webhooks page under Integrações in the sidebar.

How webhooks work

  1. You provide a target URL (an endpoint on your server or a third-party service that can receive HTTP requests).
  2. You select which events should trigger the webhook.
  3. When one of those events occurs in AutoTalk, the platform sends an HTTP POST request to your target URL with the event data in JSON format.

Your external system receives the data and can act on it however you need, whether that means updating a database, sending a notification, or triggering a workflow.

Managing webhooks

Viewing existing webhooks

Navigate to Integrações > Webhooks. The page displays a list titled Webhooks with all of your configured endpoints. The list follows AutoTalk's standard CRUD format with options to filter, view, edit, and delete entries.

Creating a new webhook

  1. On the Webhooks page, click the Add new webhooks button.
  2. Fill in the required fields:
    • Target URL — The endpoint where AutoTalk should send event data
    • Events — Select which events should trigger this webhook
    • Any additional configuration fields such as headers or authentication details
  3. Save the webhook.

AutoTalk will now send an HTTP POST request to your target URL every time one of the selected events occurs.

Editing or deleting a webhook

  • Click on any webhook in the list to view its details and modify its configuration.
  • To stop notifications to a specific endpoint, delete the webhook from the list.

Common use cases

  • CRM synchronization — Automatically update your CRM when a new contact is created or a conversation status changes in AutoTalk.
  • Slack or Teams notifications — Send alerts to a team channel when specific events happen, such as a high-priority message arriving or a conversation being escalated.
  • External analytics — Forward event data to an analytics platform to track message volumes, response times, or agent performance.
  • Automation workflows — Trigger actions in automation platforms like Zapier, Make (Integromat), or n8n based on AutoTalk events.
  • Discord notifications — Send event alerts to a Discord channel using a Discord webhook URL as the target.
  • Custom business logic — Execute any server-side logic when events occur, such as generating invoices, scheduling follow-ups, or updating inventory.

Testing your webhooks

Before connecting a webhook to a production system, test it with a temporary endpoint:

  1. Go to a service like webhook.site and copy the unique URL it provides.
  2. Create a webhook in AutoTalk with that URL as the target.
  3. Trigger the event (for example, send a test message through a connected channel).
  4. Check the webhook.site dashboard to see the data AutoTalk sent.

Once you confirm the payload format and content, replace the test URL with your production endpoint.

tip

If your webhook endpoint returns an error or is unreachable, AutoTalk may retry the delivery. Make sure your endpoint is reliable and returns a 200 OK response to acknowledge receipt.

Next steps