Agent Doorbell

Troubleshooting and access

Testing and activation

Check the rules and receiver before sending real events to your agent.

When to use it

Test before going live or after changing your receiver's URL or key.

Example

A connection test reaches your agent, but an invoice email does not. Check the email rule and timing before changing a working receiver.

Set it up

  1. Save your draft. Preview a sample that should match and one that should not.
  2. Approve and send a test from the Test step. A webhook test may run your workflow. The receiver must treat it as a test, not a real task.
  3. For MCP, ask your agent to receive and acknowledge the test. Check test status until it passes. A test waiting in an inbox has not passed.
  4. Review the saved receiver, rules, shared fields, and storage changes. Approve the settings and choose Activate.
  5. Send a new matching event and check delivery. Compare the message and notification IDs with your receiver. Also check that an event outside your rules does not arrive.

Important limits

  • Previews do not store samples or notify your receiver. Sending a test does invoke the receiver, but it does not activate your setup.
  • Approval applies to the settings you reviewed. If the settings, source fields, storage permissions, or receiver credentials change, review and approve them again.
  • Receiving and acknowledging a test does not invalidate your activation approval.
  • Activation applies to future events. A passed test or delivered event does not mean your agent finished a task.

Troubleshooting

  • If activation is blocked, check the receiver's connection test. If the review expired or settings changed, refresh the review and approve it again. An expired review alone does not require another test.
  • If a test passes but real events do not arrive, check the source connection, rule values, active settings, notification timing, and agent polling.
Technical reference

save_agent_address returns sample previews, the saved address, confirmation, expiresAt, and blockers. It requires configuration:write. Keep the confirmation while testing.

test_agent_receiver requires approved: true. For MCP, call receive_agent_message with receiver: draft, check synthetic, and call ack_mcp_wakeup with the returned leaseId. Do not start real tasks or reply to a test.

activate_agent_address requires name, the confirmation from save, and approved: true. No revision argument is needed. Doorbell checks the reviewed settings and requires a passed test for the current receiver credentials.

The confirmation covers the draft, source policies and schemas, and receiver credential version. If it expires or becomes stale, save again and obtain approval of the returned settings. Test acknowledgment does not invalidate it.

Source dry runs inspect source extraction and active routing only. Use save_agent_address samples to preview the proposed draft and test_agent_receiver to test its receiver.

Open Agent Doorbell