Agent inputs and matching

When to use it

Give each agent the inputs it needs. Reuse one source across agents with different conditions, shared fields, timing, or receivers.

Set it up

1. Open Agents & outputs and set up or edit an agent. Choose its receiver and source inputs.
2. For each input, approve captured fields, then add conditions using source-relative paths such as subject, order.status, or text. All conditions must match.
3. Choose the fields to share. Use the same path convention for conditions and shared fields.
4. Save a matching and nonmatching sample for each input. Inspect the projected fields as well as the match result.
5. Review notification settings, test the receiver, and explicitly approve activation of the saved settings.

Important limits

• An input's conditions apply only to its selected source instance. An empty condition list admits every permitted event from that source.
• Matching is case-sensitive for every source family. Operators include equals, not_equals, contains, not_contains, in, not_in, starts_with, not_starts_with, within_last_seconds, and not_within_last_seconds. Missing fields fail conditions, including negative conditions.
• Capture limits what matching can inspect. Sharing fewer fields does not change matching; a condition may use a captured field without sharing it.
• Rules route events, not authorize agents. Customer-wide grants still allow authorized agents to read other retained content.
• Saving a draft leaves live settings unchanged. Activation changes future arrivals; accepted notification work keeps its pinned settings. Pause and receiver replacement can cancel unsent work. In-flight requests cannot be recalled.

Troubleshooting

• If a preview differs from a live result, compare source capture permissions, exact field values, and active rather than draft settings.
• If unrelated events match, inspect the conditions for that source input. A condition on another input does not filter it.