Agent Doorbell

Routing and destinations

Details to include

Choose the optional source data your agent receives after an event matches.

When to use it

Include enough context for your agent to identify the event and decide its next step, without sending every available field.

Example

For invoice mail, include the sender and subject so your agent recognizes the request. The message ID and connected account identify which email its own mailbox tool should open.

Set it up

  1. Open the named agent's inputs. Review which fields the source may retain before choosing fields to share.
  2. Select source-relative paths in include: from or subject for email, order.id for a webhook, text or topic for custom MCP messages, and permitted message context for Slack or Teams.
  3. Save and inspect sample projections. Test the receiver, review the settings, and activate. Inspect a fresh live message separately.

Important limits

  • Email always carries message and connected-account identity. Optional fields are internalDate, from, to, cc, and subject.
  • Doorbell never includes email bodies, previews, or attachments. Your agent retrieves mail through its own separately authorized tools.
  • Declared webhook scalars and explicitly approved bounded JSON capture are not raw-request archives. Teams attachment descriptors can be incomplete; file contents are not supported. Slack source settings decide whether text exists to share.
  • Selecting shared fields does not change matching. A condition can use a captured field without including it in the notification. Direct named messages carry their message text.
  • Every wakeup has an events list. A page contains 1–20 events according to notifications.pageSize, default 5. An omitted count identifies remaining details; pull them or use automatic drain.

Troubleshooting

  • If a field is absent, check the source schema, capture choices, supplied value and type, and the agent's include list.
  • Read body.events[] independently and inspect unavailable content reasons rather than treating missing content as an empty task.
Technical reference

Every event has source, data, and metadata. The envelope includes signalId and synthetic; notifier-produced signals also include notifier identity. A standalone destination connectivity test has no notifier identity.

Read each event independently. Signal and event IDs remain stable across retries; the receiver should avoid repeating already-handled work. Synthetic events must not trigger real tasks.

Open Agent Doorbell