Stilla
Start For Free

Triggers

Triggers control when your automations run. You can schedule them, trigger them from channel mentions, or run them manually.

Scheduled triggers

Set automations to run on a recurring schedule. Stilla supports flexible scheduling:

  • Simple: "Every Monday at 9am", "Every weekday at 5pm"
  • Complex: "Every other Friday", "First Monday of each month"
  • Frequent: "Every 4 hours", "Every 30 minutes"

Schedules use your timezone by default. You can override the timezone if needed for distributed teams.

Each automation can have multiple scheduled triggers. Every trigger evaluates based on the start date you specify — the automation won't run that schedule before its start date.

If multiple schedules are due at exactly the same time, Stilla coalesces them into one automation run. For example, an automation scheduled daily at 9am and every Monday at 9am runs once on Monday at 9am. Each schedule continues advancing independently after that occurrence.

Channel-based triggers (playbooks)

Configure automations for Stilla to respond when @Stilla is mentioned in specific channels:

Slack channels

Add Slack channels to your automation. When @Stilla is mentioned, Stilla processes the message using the automation's instructions. There are two modes:

  • Mention mode (default) — Stilla only responds when someone explicitly mentions @Stilla in the channel
  • Intake mode — Stilla processes every message automatically, without requiring a mention. Useful for dedicated intake channels like #support-requests

GitHub repos

Add GitHub repositories. When @Stilla is mentioned in issues or PRs in those repos, Stilla handles the request.

Linear teams

Add Linear teams. When @Stilla is mentioned in issues belonging to those teams, Stilla responds according to the automation's instructions.

Manual triggers

Run any automation on-demand from the Stilla app, using the Run button. This is useful for:

  • Testing automations before enabling automated triggers
  • Running one-off tasks that don't need a schedule
  • Triggering automations in response to ad-hoc events

Combining triggers

An automation can combine multiple scheduled triggers with channel listeners. For example:

  • A triage automation that runs every morning at 8am to review overnight issues, AND responds to @Stilla mentions in #support for real-time triage
  • A digest automation that posts weekly summaries on schedule, AND can be triggered manually for on-demand reports