Stilla
Start For Free

Creating automations

Creating an automation takes minutes. Write what you want in plain English, configure when it should run, and you're done.

Step-by-step setup

1

Name your automation

Give your automation a clear, descriptive name. This appears in the automation list and in run history, so make it recognizable — e.g., "Weekly Engineering Digest" or "PR Review".

2

Configure triggers

Choose when the automation runs. Set a recurring schedule, listen for @Stilla mentions in specific channels, or run manually. You can have multiple triggers, and combine them freely. See Triggers.

3

Write instructions

Describe what Stilla should do in the prompt. Be specific about what data to gather, what output to produce, what format to use, what actions to take, and any constraints. The prompt is plain markdown — write it like you're giving instructions to a capable teammate.

Tag using @-tag in the instructions to target channels in Slack, teams in Linear, or repositories in GitHub that Stilla should read, or post to when running.

4

Set restrictions (optional)

Control what Stilla can access and modify. See Automation Restrictions.

5

Test and enable

Run the automation manually to verify it works as expected. Review the automation run canvas to see what Stilla did. Once you're satisfied, enable it.

Prompt best practices

  • Be specific about output: "Write a summary with bullet points grouped by team" beats "summarize what happened"
  • Name your integrations: "Search Linear for issues updated this week" tells Stilla exactly where to look
  • Define success criteria: "Only include PRs that were merged, not opened or closed"
  • Handle edge cases: "If no updates are found, post a short message saying so"

Example: weekly summary automation

Collect all updates from the past week:
- Linear issues completed, started, or created
- GitHub PRs merged
- Significant Slack discussions in #engineering

Write a summary grouped by project. For each project, list:
- Completed work
- In-progress work
- Notable discussions or decisions

Post the summary to #engineering-updates on Slack.

Example: meeting follow-up automation

After each meeting:
1. Read the transcript and identify action items
2. Create a Linear issue for each action item, assigned to the person mentioned
3. Post a summary of created issues to me in a DM
4. If no action items were found, reply confirming the meeting had no follow-ups

Turn on, and off

Toggle automations on and off without deleting them. Disabled automations retain their configuration and run history, so you can re-enable them anytime.