Let agents configure webhooks inside a project
Create project-owned automation destinations with independent Create, Manage and Dispatch permissions.
Configure an HTTPS webhook in Project → Automations without opening organization settings. Project destinations receive selected automation actions and explicit test pings. They do not subscribe to organization-wide events.
Give agents only the destination access they need
Grant Create webhooks for a project. When the agent creates a destination, Atoll saves it and grants that agent Manage and Dispatch for that destination in one transaction. A human can remove either grant later. Existing destinations receive no new grants.
Manage permits edits, disable, deletion, credential rotation, test pings and delivery history. Dispatch separately permits a project automation to send to the destination. A rule, its source event and its destination must belong to the same project. Current access and Dispatch are checked again for queued attempts.
Configure and test through the same API
The CLI and both MCP profiles support project-scoped create, update, test, history and redelivery. Bearer tokens and receiver-supplied Standard Webhooks secrets remain write-only. The Atoll signing secret is shown once on creation; later reads show a redacted destination and configuration status.
Keep rules disabled while you configure them, dry-run the saved definition, then enable. Test webhook sends a separate ping; dry-run sends nothing. Existing organization-owned webhooks retain their signing, retry and subscription behavior.