Configure webhooks

Open Settings → Webhooks to configure real-time outbound notifications for one agent.

AgentStack obtains a portal URL for the agent. Then the page opens a managed Svix App Portal.

You must have administrator access to this page. An endpoint can receive customer contact information.

The managed portal is unavailable while the agent is scheduled for deletion. Cancel the deletion before you create or change webhook endpoints.

Create endpoints in the portalCopy Anchor Link

Use the embedded portal to create and manage webhook endpoints. The portal offers these event types:

• contact.created and contact.updated — a lead or contact is created, or a contact is resubmitted
• conversation.note_created — an operator adds a note
• form.submitted — a client submits a custom form

Choose only events that your receiver can safely process.

Delivered events use an envelope with a type, a timestamp, and a data payload. Build your endpoint to validate events and route them by type. Check that processing is idempotent. If your endpoint receives the same business event more than once, do not duplicate the customer action.

Treat delivery as asynchronousCopy Anchor Link

AgentStack sends webhook events asynchronously. The original contact, form, or note operation does not wait for the delivery result. If delivery fails, AgentStack logs the failure. The failure does not undo the original customer action.

First, test a non-production endpoint. Then check that it can handle missing optional data and its own temporary failures.

The managed portal is the source of truth for endpoint authentication, signing details, delivery logs, retention, and retry behavior. The dashboard code does not configure these details. Before you make a contractual claim to your integration team, check these details in the portal.

For event-triggered product work beyond notifications, see Integrations and actions.