Triggers
Agents that act when something happens
A lot of useful work starts with an event: a message arrives, a ticket is created, an alert fires. Triggers let Metorial listen for those events from your providers and start an agent action in response. Agents handle work as it comes in instead of only when a person prompts them.
- 01
Respond to real-time events.
Act on things like new Slack messages, Jira tickets, or Gmail emails as they happen.
- 02
Keep reactive agents governed.
Event-driven actions run under the same access control and policies as any other agent activity.
- 03
Use the connections you already have.
Triggers build on the providers already set up in Metorial, with no extra plumbing.
How triggers work
From event to governed action
Triggers connect the events your providers emit to the actions your agents take, with Metorial's controls in between.
Catch the event
Apply the rules
Keep the trail
Listen for an event. Start an agent action. Keep it governed. Log what happened.
FAQ
Answers to common questions about triggers and how they fit into governed AI agent infrastructure.
What are triggers in Metorial?
Triggers let Metorial listen for events from your tools and start agent actions in response. Agents react to things happening instead of only responding to prompts.What kinds of events can trigger an action?
Events from your providers, such as new Slack messages, Jira tickets, or Gmail emails.Are triggered actions governed?
Yes. They respect the same policies and access control as any other agent activity.Are trigger events logged?
Yes. Trigger events and the actions they start appear in audit logs. You can review what an agent did and why.Do I need a separate integration to use triggers?
No. Triggers build on the providers already connected in Metorial.Can triggers be configured and restricted?
Yes. You control which events start actions and what those actions can do, with parameters, authentication, and access control policies.