Slack Triggers, Retryable Tasks, and Smarter Automations

#Trigger automations from Slack messages

Slack automations can now start when a new message is sent in a channel. You can also filter by channel, which makes it easier to react to requests in a specific support, triage, or engineering channel.

#Reset and retry tasks

If a task gets into a bad state or you want to rerun it cleanly, you can now use Reset and Retry from the task page. Tembo clears the previous task data and restarts the job without you needing to create a brand new task.

#Better webhook and API triggers for automations

Automations now have an editable trigger name/key, and you can trigger them through webhooks or the API using either the workflow ID or key. That makes it much easier to wire Tembo into external systems without relying on brittle internal identifiers. See API trigger automation documentation for more details.

#More control over Jira and GitHub triggers

Jira automations now support new Issue Updated and Issue Label Added triggers, and GitHub's Pull Request Opened trigger can now filter by label. This gives you more precise ways to kick off follow-up work only when the right issue or PR changes happen.

#Faster pull request review inside tasks

Task pages got a more capable right sidebar with clearer pull request actions, checks, diff controls, file filtering, and sandbox log access. Pull request commit data is also richer now, including author details plus additions and deletions counts, so reviewing changes inside Tembo is faster.

#Smoother Linear setup

Linear setup is smoother now too: the integration page can preselect a default repository, and Tembo gives clearer feedback when a workflow expects a linked GitHub account. That reduces setup friction before you turn on Linear-powered automations.

Also various bug fixes and improvements as always :)