Trigger agents from real-time events

Triggers let Metorial listen for events from your providers, like new messages or tickets, and start agent actions in response.

Get startedBook a demo

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.

  1. 01

    Respond to real-time events.

    Act on things like new Slack messages, Jira tickets, or Gmail emails as they happen.

  2. 02

    Keep reactive agents governed.

    Event-driven actions run under the same access control and policies as any other agent activity.

  3. 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.

Listen

Catch the event

Metorial receives events from providers. An incoming message or ticket can start a workflow.
Govern

Apply the rules

Triggered actions respect policies and access control. An agent only does what it's allowed to.
Record

Keep the trail

Trigger events and the actions they start appear in audit logs. Reactive behavior is reviewable.
Recent updates to TriggersView all
Introducing Metorial Callbacks

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.

  1. 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.
  2. Events from your providers, such as new Slack messages, Jira tickets, or Gmail emails.
  3. Yes. They respect the same policies and access control as any other agent activity.
  4. Yes. Trigger events and the actions they start appear in audit logs. You can review what an agent did and why.
  5. No. Triggers build on the providers already connected in Metorial.
  6. Yes. You control which events start actions and what those actions can do, with parameters, authentication, and access control policies.

Build agents that respond the moment something happens

See how triggers let agents react to real-time events with governance in place. Book a demo, or get started and connect your first provider.

Book a demoGet started