What Is a Trigger on Macha? AI Agents That Start Themselves
A trigger is the thing that turns an agent from "something you talk to" into "something that works on its own." The definition is simple: a trigger is an event in a connected app that automatically starts one of your agents. When the event happens, the agent springs into action — no one has to ask it.
The 30-second version
How a trigger works
It's the simplest idea on the platform: an event happens somewhere, and your agent starts. That's it. When you add a trigger to an agent, you're saying "when this happens, run."
The triggers available come from your connected apps. A few common ones:
- A new Zendesk ticket. When a ticket is created, the agent reads it and processes it automatically — the bread-and-butter of support automation.
- A Slack mention. When someone mentions your agent in Slack, that mention kicks it into action.
- A ticket status or priority change, a new comment, an assignment — any of these can start an agent.
- A custom webhook. Got a system that isn't a built-in connector? A custom webhook lets any external event send data straight to your agent.
Trigger vs. no trigger
An agent without a trigger only runs when you chat with it. Add a trigger and it runs on its own when the event fires. That's the entire difference between an agent you operate by hand and one that works in the background:
- No trigger → interactive: you start it (chat).
- Trigger → autonomous: the event starts it.
(For the full comparison, see autonomous mode vs. interactive chat.)
Why triggers matter
Triggers are what make automation automation. Instructions tell an agent what to do and tools let it act, but a trigger decides when — and "when a new ticket arrives, automatically" is the whole point of putting an AI agent on your helpdesk. Without a trigger you have a very capable assistant you have to summon; with one you have a teammate that's always on.
Frequently asked questions
What is a trigger in Macha? An event in a connected app (a new ticket, a Slack mention, a webhook) that automatically starts one of your agents.
Do I need a trigger to use an agent? No — without one, the agent runs when you chat with it. A trigger makes it run automatically.
What can trigger an agent? Events from your connected apps — Zendesk ticket created/updated, Slack mentions, and custom webhooks for anything else.
Can one agent have more than one trigger? Yes — you can send several different events to the same agent.
What happens when a trigger fires? The agent runs autonomously: it reads the event's data and acts according to its instructions, with no confirmation step.
The bottom line
A trigger is just an event that starts an agent — a new ticket, a Slack mention, a webhook. It's the small piece that turns a capable agent into an autonomous one, working in the background the moment something happens. Next: how to set one up.
Make an agent autonomous: add a trigger and let it run on every new ticket. 7-day free trial, no credit card required. Start free.
