Routing and destinations
Webhook destinations
Push Inbox references and explicitly selected context to a public HTTPS endpoint.
When to use it
Choose a webhook when the receiving platform exposes a URL and key and can use selected context or separately fetch mail.
Example
One Ops arrival notifies Amp and Grok through separate triggers. Grok can accept its notice even if Amp's endpoint fails. Neither handoff proves that work started.
Set it up
- Choose a webhook workflow that accepts flat v2 notices and verifies the configured Bearer key. Support v3 before selecting context. Fetch-first agents need separately approved mailbox access.
- Open Integrations > Destinations. Enter the public HTTPS URL and key in secure fields, not in chat or a prompt. Open Destinations.
- Send a destination test and correlate deliveryId in the receiver. The receiver accepts destination_test without business effects. Require HTTP 200 and a current tested version.
- Review source-specific context defaults. This save leaves credentials and tested state unchanged. In Configure > Triggers, explicitly inherit or override each source. Send fresh matching mail and inspect handoff and the receiving workflow's work separately.
Important limits
- The URL must be public HTTPS without embedded credentials, query strings, fragments, or nonstandard ports. Private addresses and redirects are refused. Doorbell sends the saved key as Authorization: Bearer.
- A source receives mail into Doorbell; a destination accepts outgoing notices. A notice contains references and optionally selected context, never mailbox credentials or action authority.
- Each destination has independent attempts and outcomes. HTTP 200 proves acceptance, not execution. Retries can produce duplicate effects, so preserve delivery IDs and deduplicate business effects by canonical message ID.
- Before replacing credentials, preview the change and pause every attached trigger. Preserve the previously active trigger IDs, confirm the fresh preview, test the new version, and resume only those triggers with approval.
- Ordinary readers see related recipient names and delivery states through mailbox_delivery_status, not URLs, keys, or unrelated mailboxes. Receiving a reference never grants access.
- Review disclosure and mailbox access separately. Generic webhook tests do not prove live Grok Bot or Dots compatibility. If the client exposes no URL and key, use direct Inbox polling instead.
Troubleshooting
- If a test fails, check the active workflow, exact notice parser, URL, and Bearer key through secure settings.
- If Doorbell reports delivery but no work occurs, inspect the receiver's logs, task instructions, and mailbox authorization using deliveryId.
- Before deleting a destination, remove or repoint every attached trigger. Confirm the fresh deletion preview rather than assuming the destination is unused.