Triggers
An agent is only as useful as the moments it springs into action. In Tulsk, one agent carries any number of triggers — and you manage them in plain language from Chat.
Trigger Types
| Trigger | How it fires |
|---|---|
| @mention | Always on — mention the agent in any task comment or in Chat and it responds. |
| Schedule (cron) | The agent runs a task on a recurring schedule, in your timezone. |
| Reply | Reply to an agent’s comment in the same thread and it picks the conversation back up. |
| Assignment | (Opt-in) Assigning a task to an agent triggers a run automatically. |
| Channels | Messages from connected Slack / Telegram / WhatsApp channels reach the agent. |
Managing Triggers From Chat
No settings page required:
- Add: “@Research Agent, run the competitor digest every Monday at 9am” — Chat creates the task (if needed) and attaches the schedule to that agent. Recurring work that names no agent becomes a schedule that runs as you instead.
- List: “What does the Research Agent run on?” — you get the full trigger list as a card: schedules plus the always-on entry points.
- Remove: “Stop the Monday digest” — the trigger is removed.
One agent, many triggers. A single inbox agent can run a morning briefing on a schedule, answer @mentions during the day, and respond in your Slack channel — simultaneously.
Where Triggers Live
There is no separate triggers page. An agent’s schedules sit on the Schedule page in the sidebar, in the same list as your schedules, each labeled “Triggers” and the agent’s name — edit, pause or delete them there. What a trigger did lands where the work lives: the task’s thread and your chat. Tulsk checks agent schedules every 5 minutes, in each schedule’s time zone.
Trigger Modes
Agents have a default disposition for how they pick up work:
Immediate
The agent reacts as soon as it’s mentioned or assigned. Best for support-style and conversational agents.