Events & Channels
Give CUGA a life outside the chat box — let it watch the world, react to events from your tools, and talk to you on Slack, WhatsApp, Telegram and Discord.
Out of the box, CUGA answers when you ask. The events layer gives it a life of its own: it can watch for things to happen and act, and it can talk to you where you already are.
Everything here is opt-in and runs with no extra infrastructure — no Activepieces, no message queue, no external scheduler. It's a second process next to CUGA, and you turn on exactly the pieces you need.
Three things it adds
⏰ Proactive triggers
CUGA watches the world on a schedule and acts on change — "every morning post the crypto prices", "check this page every 10 minutes and tell me only if it changed". Native cron and polling, in-process.
🔔 Watch your tools
React to events from GitHub, Box, Slack, Discord, Telegram and any system that can send a webhook — "when a PR opens, summarize it", "when someone reacts 🐛, triage it". Or watch your own function on a timer — anything CUGA can call, it can watch.
💬 Channels
Talk to CUGA from Slack, Discord, Telegram, WhatsApp — not just the web chat. Ask questions, or set up automations by messaging it in plain language.
The mental model
Think of the events layer as three verbs, all reachable in one natural-language command — /automate:
| Verb | You say | What CUGA does |
|---|---|---|
| Schedule | "every weekday at 9am, send me the weather" | runs the agent on a cron, delivers the answer |
| Poll | "watch this API every 10 min, ping me if it changed" | runs on an interval, delivers only on a real change |
| Watch | "when a new PR opens on my repo, review it" | subscribes to a trigger from GitHub / Box / a webhook and fires on the event |
The answer is delivered wherever you asked for it — the web chat, or a channel like Slack or
WhatsApp. Arming is a one-line human-in-the-loop step: you type /automate …, CUGA proposes the
standing flow, and you confirm with yes.
Behind every fire is a roster — a team of specialist agents where a supervisor routes each event to the one whose job it is (a PR → the reviewer, a Box file → the screener). You can extend it with your own agents and tools. See Agents & rosters.
No Activepieces required
Channels, the cron/poll scheduler, the generic webhook, GitHub triggers and Box triggers are all direct — they talk to each provider themselves. Activepieces is only involved for the SaaS OAuth triggers still on it (Gmail, Outlook), which are optional and off by default.
What's optional (almost everything)
You add capability one credential at a time. Nothing below blocks anything above it:
- Events alone — arm and fire cron/poll/webhook flows, delivered to the built-in web chat. Needs only your LLM keys + a gateway token. No channel tokens, no public URL. → Quickstart
- + a channel — add one bot token to talk to CUGA from Slack / Discord / Telegram / WhatsApp. → Channels
- + a trigger integration — add a secret to watch GitHub / Box / webhooks. → Triggers
- Deploy — ship the whole thing to IBM Code Engine. → Deploy
New here? Start with the Quickstart — it proves the whole arm → schedule → fire → deliver loop locally in five minutes, with no channels and no cloud. The Keys page is the one place every environment variable is listed, grouped so you only read the rows for the pieces you turn on.
