Troubleshooting and access
Testing and going live
Check routes, triggers, and destinations before relying on real events.
When to use it
Test before going live, after changing a route or trigger, or after changing a destination's URL or key.
Example
A webhook test reaches your routine, but an invoice email does not. Check the route's condition and the trigger's timing before changing a working destination.
Set it up
- Preview source extraction with a dry run for webhook and MCP sources. Dry runs store nothing and do not evaluate route or trigger matching.
- For push notices, open Integrations > Destinations and send a test after approval to contact the workflow. The receiver must recognize destination_test and stop without business effects or replies. Open Destinations.
- Enable an Inbox trigger only after its destination passes a test at its current version. Separately approve mailbox access for its receiving agent. Polling agents need no destination or trigger.
- Send a fresh message that the source captures and a nonmatching control to verify routing. Check the mailbox in Mail. If you use a trigger, verify each destination's handoff. Check the receiving workflow's actual work separately.
Important limits
- Dry runs do not store samples or notify anyone. Sending a test does invoke the destination.
- Replacing a destination's URL or key clears its test. Pause its triggers before replacing it, test again, then re-enable them.
- Routes and triggers apply to future events. A passed test or delivered event does not mean your agent finished a task.
Troubleshooting
- If a trigger cannot be enabled, test its destination first. If its receiver cannot read mail, check that agent's grant and connection capability.
- If a test passes but real events do not arrive, check the source connection, capture, route conditions, trusted trigger match, timing, and receiver logs.
Technical reference
dry_run_webhook_endpoint and dry_run_mcp_message preview extraction for a source without storing a receipt. They do not evaluate route or trigger matching. Use a fresh captured message to verify routing and notifications.
test_webhook_destination requires acknowledgeWakeup: true. Only HTTP 200 marks the current version tested.
save_mailbox_trigger returns the trigger's notifierId and whether it is active. Pass notifierId as id to get_notifier_diagnostics for matching and delivery evidence.