Triggers & going live
Connect an event so an employee runs on its own.
Part of the crew rollout: Agents shows as Soon in the app until it reaches your account. See Hiring your crew.
A tested agent still only runs when you press send. A trigger is what turns it into an employee: it connects a real-world event to the agent so it runs on its own, then sends the result back to where the event came from.
Saving and versioning
Save publishes the agent's current graph. Every save is kept as a version, so you can look back at history or publish an earlier version again. Saving never overwrites what came before.
Triggers
A trigger wires an incoming event to the agent. Connect one from the Triggers panel in the editor, and from then on the matching event runs the employee automatically.
| Source | Setup |
|---|---|
| Telegram | Add your bot token to the agent's variables; Modus registers the webhook automatically |
| Slack | Add the bot token and signing secret, then paste the webhook URL Modus gives you into your Slack app |
| GitHub | Add a webhook secret, then paste the webhook URL into the repo's webhook settings |
| Linear | Add a webhook secret, then paste the webhook URL into Linear |
| Discord | Bot token based; on the way |
Each trigger shows its status (active, pending, or error) and can be disabled anytime. When a trigger fires, the agent runs and replies in the same place: a Telegram reply, a threaded Slack message, a comment on the GitHub issue or PR.
Who may talk to the employee on those channels is governed by its DM policy (open, pairing, allowlist, or disabled), set on the dashboard.
Multi-turn context
Within one channel or thread, the agent reuses its session, so an employee answering in a Slack thread or a Telegram chat remembers the earlier messages in that conversation.
You stay in control
A trigger only does the job its agent is built for, with the tools and accounts you granted. As everywhere in Modus, on-chain actions need your say-so. Your crew operates; you approve.