Event triggers

Event triggers start a run in response to an external or platform event instead of a direct call. The event’s payload reaches the agent as the run’s input, and the trigger is governed and audited like any other way of starting a run.

Under construction

This page is planned and not yet written, because the capability it describes is not yet generally available. The structure is here so you can see where it fits; the notice comes off when it ships.

What this page will cover

• Trigger sources: webhooks, queues, and platform events such as a run completing.
• Verifying and shaping the incoming payload before it reaches the agent.
• Mapping an event to a session: new session per event or continue an existing one.
• Retries, deduplication, and how triggered runs appear in evidence.

Meanwhile

• Invoke from your application shows how to start a run from your own webhook receiver today.
• Stream and replay events covers the events a run emits, which a trigger could react to.
• Delegate work to another agent is the governed way one agent starts work in another today.