Webhooks

AgentStack supports the event types contact.created, contact.updated, conversation.note_created, and form.submitted. Retrieve the public event-type endpoint when an integration needs a current capability list, then configure delivery through the agent-specific portal URL. Creating that portal URL requires an admin-scoped REST key, so generate it only from a trusted backend or administrative tool.

Delivery is provisioned lazily through the agent's webhook application and is fire-and-forget with respect to the source operation. A contact or form submission can succeed even if a downstream endpoint later fails, so monitor delivery in the portal and make receiving endpoints independently retry-safe. Event payloads use a { type, timestamp, data } envelope, but contact data varies by source; inspect actual test deliveries rather than assuming one universal contact schema.

A form.submitted payload includes the form name, submission time, values, and a user verification indicator. Treat the verified flag as server-side webhook information, not as proof from a browser callback. Verify requests with the delivery provider's supported mechanism before changing downstream records.