Webhooks in Atlas

Last updated October 14, 2026

Who can use this feature?
Admins only.

Overview

A webhook is an automatic notification that Atlas sends to another system when an event happens, such as a conversation's tags changing or a new customer being created. Atlas sends the event data (the payload) to an endpoint URL you provide, so your systems don't need to keep checking Atlas for changes.

Related articles:
• Webhook events: Supported events, payload format and signature verification.
• API keys in Atlas: Send requests to Atlas from your own applications.

Key Features

Real-time notifications: Atlas pushes event data to your endpoint as soon as the event happens.
Event-based subscriptions: Subscribe each endpoint to a specific event, such as "Account Created" or "Conversation tags Changed".
Secret key verification: Each subscription has its own "Secret Key" to confirm that requests come from Atlas.
Works with your tools: Connect Atlas to your own server or to tools like Zapier, Make, Google Sheets or Twilio.
Editable endpoints: Update the destination URL when your infrastructure changes.

What you can do with webhooks

When something happens in Atlas, Atlas notifies your server. Your server, or a connector tool such as Zapier or Make, then takes the action. Some examples:

Keep a customer list up to date: When a customer is created in Atlas, your server adds their name and email to a Google Sheet or your database.
Alert an on-call manager: When a ticket's priority changes to High, your server texts the manager through an SMS service such as Twilio.
Grow a VIP mailing list: When an agent adds a VIP tag to a conversation, your server adds the customer to a VIP list in your email marketing tool, such as Mailchimp.

How to create a webhook

Requirements:
An endpoint URL on your server or connector tool that accepts incoming requests.

Go to "App Configuration > Data > API & webhooks" and click "Add webhook".
Select an event from the "Trigger event" dropdown, for example "Account Created".
In "Endpoint", enter the URL where your application receives requests.
Click "Create Subscription".
Click the copy icon next to the "Secret Key" and store it on your server. Use it to verify that incoming requests come from Atlas.

Important:
See "Webhook events" for the full list of events, the payload format and how to verify the signature.

How to edit a webhook

Go to "App Configuration > Data > API & webhooks" .
Click the webhook row, or click the ellipsis icon and select "Edit".
Update the "Endpoint" and click "Edit Subscription".

Important:
You can't change the "Trigger event". To use a different event, create a new webhook.

How to delete a webhook

Go to "App Configuration > Data > API & webhooks" .
Click the ellipsis icon on the webhook row and select "Delete".

Warning:
Deleted webhooks can't be restored. Atlas stops sending notifications to that endpoint immediately.

FAQs & Troubleshooting

What can I do with webhooks?

Atlas sends the event; your server or a tool like Zapier or Make takes the action. For example:

New customer created: Add the customer's name and email to a Google Sheet or database.
Ticket priority changed to high: Send an SMS to the on-call manager through a service like Twilio.
VIP tag added to a conversation: Add the customer to a VIP list in your email marketing tool.

What's the difference between API keys and webhooks?

API keys let your applications send requests to Atlas to read or update data. Webhooks let Atlas send data to your systems automatically when an event happens.

What is the Secret Key for?

Your server uses it to check that each payload really comes from Atlas and not from someone else.

Was this article helpful?

Table of contents