Routing and destinations

Grouping and timing

Control when matching events ring, so related messages can arrive together and notifications respect your schedule.

When to use it

Use grouping when an agent should receive a short collection of matching events rather than a separate interruption for each message.

Wait 30 seconds after the first matching event, ring sooner when three events match, and hold notifications during your local overnight quiet period.

Edit the named agent's notification settings, or pass notifications to save_agent_address with the current expectedRevision.
Choose grouping.wait from the first matching event. Optionally set eventCount to ring sooner, quiet periods with the customer's IANA time zone, and cooldown after successful handoff.
For each enabled control, choose keep or drop for blocked matches or leftovers. Overnight quiet periods are allowed; periods must not overlap.
Choose pageSize from 1 to 20 and overflowMode pull or drain. Review the full returned draft and explicitly approve activation.

Email, webhook, Slack, and Teams events use the agent's grouping policy. MCP publications notify independently without moving grouped-source windows.
Quiet periods block grouped wakeups during a local-time interval. Cooldown blocks them after a successful grouped wakeup. Neither is the initial wait.
Event count counts matching events, not source instances. An event-count ring still respects quiet periods and cooldown.
Keep preserves blocked matches or event-count leftovers for a later notification; drop removes them from the notification group, not the retained inbox.
Defaults are a 30-second wait, pageSize 5, and overflowMode pull. Drain sends later pages one at a time after the preceding handoff. Reaching pageSize alone does not ring early.
Omitting notifications on an edit preserves it. Supplying notifications replaces that block, with defaults for omitted members. Inspect the whole returned block before activation.
Activation applies prospectively; accepted work keeps its pinned revision. Pausing or replacing a receiver can cancel unsent work. In-flight requests may finish.

For a held match, use peek_mcp_waiting or get_notifier_diagnostics with IDs from list_agent_addresses to inspect timing.
If the expected local time is wrong, check the saved time zone and overnight quiet periods.
If fewer events arrive than expected, check drop settings, deduplication, and whether details span several signals.