Automations overview

Automations are reusable AI tasks that you configure with natural language instructions. No code, no workflow builders, no drag-and-drop — just plain English describing what you want done.

How automations work

Each automation has three components:

1. Triggers: When and where the automation should run
   • Scheduled: Run on a recurring schedule (daily, weekly, custom cron)
   • Channels: Where Stilla listens for mentions (Slack channels, GitHub repos, Linear teams)
2. Prompt: Regular text instructions describing what Stilla should do
3. App restrictions: Control what Stilla can access and modify for each automation — set default access levels, per-system overrides, and per-resource permissions to follow the principle of least privilege

When triggered, the automation runs in its own canvas, where Stilla executes the instructions with full access to its tools and integrations.

Automation runs

Every execution creates a separate canvas — an "automation run" — where you can see exactly what Stilla did, what tools it used, and what changes it proposed. This gives you full transparency into automated actions.

Automation runs are stored and searchable, so you can review past executions, debug issues, or audit what happened.

Automation memory

Stilla can persist information across automation runs using a memory canvas. This lets Stilla track trends, remember decisions, and build up context incrementally rather than starting from scratch each time.

Channel triggers

By assigning an automation to specific channels, you can customize how Stilla responds when mentioned in different contexts. Each channel can have its own automation, so Stilla behaves differently depending on where it's mentioned.

For example:

• An automation for your #support Slack channel that follows specific triage steps
• An automation for GitHub PRs that runs your team's review checklist
• An automation for Linear that categorizes and routes new issues

Use cases

• Weekly standup summaries: Aggregate updates from Linear, GitHub, and Slack into a weekly digest
• Changelog generation: Generate release notes from merged PRs
• Customer feedback triage: Route and categorize incoming feedback
• Incident response: Pull context from PagerDuty, Slack, and logs when incidents fire
• Dependency scanning: Check for outdated or vulnerable dependencies on a schedule
• Meeting prep: Before a recurring meeting, gather relevant updates from all connected tools