Automations

Run coding agents on a schedule or triggered by events.

Run coding agents in the background, on a schedule or triggered by events. A Sentry error gets fixed within seconds. Docs stay in sync with your code. Security vulnerabilities get caught before they become problems.

Each automation runs in a secure sandbox with full codebase and repository access and your configured MCP servers.

Triggers

These are just examples to give you a rough idea. You decide how to set this up, there are no limitations.

Scheduled

Run automations at regular intervals.

Schedule	Example
Hourly	Monitor for CI failures, new Sentry errors
Daily	Generate changelogs, post standup summaries
Weekly	Clean up stale TODOs, security scans
Monthly	Dependency audits, documentation reviews

Event-driven

React to events from your integrations in real-time.

Integration	Events
GitHub	PR opened, PR merged, issue created, comment added
GitLab	Merge request opened, merged, issue created
Sentry	New error, error spike, regression detected
Linear	Issue created, issue updated, status changed
Slack	Message in channel, @tembo mention

Automation slug

Use an automation slug to trigger an automation on demand from external systems or chat commands.

1. Set a Slug on your automation (in the automation’s properties panel).
2. Trigger the automation with that slug from API calls or slash commands.

The payload is passed to the automation as event context, so your instructions can reference it directly. For example, you could write instructions like “Fix the issue at the URL provided in the event payload”.

API trigger (webhook)

You can trigger an automation programmatically using its slug via our SDK or an API request.

Slash command trigger

You can trigger a task with the selected automation by using slash commands.

@tembo /<automationSlug>

Creating an automation

From a template

1. Go to Automations in the dashboard
2. Click Templates
3. Pick a template and click Use template
4. Customize the instructions and enable

Browse all templates

From scratch

1. Click New Automation
2. Write your instructions
3. Add triggers (schedule and/or event-based)
4. Select coding agent
5. Instruct MCP servers or integrations
6. Save and enable

Beyond code

Automations aren’t limited to engineering tasks. With MCP servers, agents can work across your entire stack.

Example	Trigger	What it does
Daily ARR report	Daily	Pulls revenue data from Stripe and posts to Slack
Feature requests from calls	Daily	Scans call transcripts for feature requests and creates Linear tickets
Customer health check	Weekly	Summarizes support tickets, usage trends, and churn signals in Slack
Enrich CRM records	New deal created	Pulls company info and adds context to Attio or your CRM
Create CRM tickets from Slack	@tembo in Slack	Creates a ticket in your CRM enriched with context from other connected integrations

Any tool with an MCP server can be used in an automation.

You can also do this on-demand from Slack without setting up an automation:

@tembo What's our ARR right now? Check Stripe.

@tembo Summarize the feature requests from this week's sales calls and create Linear tickets for the top 5.