Configure webhooks
Use the agent’s managed webhook portal to deliver supported events to your own endpoint.
Open Settings → Webhooks to configure real-time outbound notifications for one agent. The page opens a managed Svix App Portal after AgentStack obtains a portal URL for that agent. Administration is required because an endpoint can receive customer contact information.
Create endpoints in the portal
Use the embedded portal to create and manage webhook endpoints. The current event types are contact.created and contact.updated for lead or contact creation and resubmission, conversation.note_created for an operator note, and form.submitted for a client-side custom-form submission. Choose only events your receiver can safely process.
Delivered events use an envelope with a type, timestamp, and data payload. Build your endpoint to validate and route events by type, and make processing idempotent: a customer action should not be duplicated if your own endpoint receives the same business event more than once.
Treat delivery as asynchronous
AgentStack dispatches webhooks without making the original contact, form, or note operation wait for a delivery result. A delivery failure is logged and does not undo that originating customer action. Test a non-production endpoint first, then confirm that it can handle missing optional data and its own transient failures.
The managed portal is the source of truth for endpoint authentication, signing details, delivery logs, retention, and retry behavior. Those details are not configured in the dashboard code, so verify them in the portal before making a contractual claim to your integration team.
For event-triggered product work beyond notifications, see Integrations and actions.