Automations: Rules That Handle Your Tickets and Releases For You

Critical tickets straight to on-call? New bugs auto-labelled? A Slack ping when a release ships? A weekly report every Monday at 9? These are small chores you don't want to do — and from now on, you no longer have to.

The new Automations are your "if-this-happens-then-do-that" for Spedy. You build rules that run in the background and Spedy takes care of the rest. No extra tool, no second dashboard — right where your tickets already live.

Automations are part of the Pro plan.

How to Think in Automations

Every rule has three simple parts:

1. When should it run? — the trigger
2. In which cases? — optional conditions
3. What should happen? — one or more actions

In plain English:

When a ticket is created, and its priority is Critical, then assign it to the on-call user and send a message to #incidents.

That's it. No code, no scripts. You click it together in the rule builder and you're done.

Triggers: When Your Rule Fires

Automations react to 14 different events in Spedy:

• Tickets — created, updated, deleted, status changed, reassigned
• Labels — added or removed
• Comments — new comment on a ticket
• Custom fields — a value changed
• Project progress — milestone reached, release created
• Pull requests — merged or status changed
• Schedule — time-based runs, e.g. hourly or every Monday

For the schedule trigger, there are quick-select buttons for the usual intervals (15m, hourly, daily, weekly) — if those work for you, you don't have to type a cron expression. The minimum interval is 15 minutes.

Conditions: Only in the Right Case

Conditions are optional, but they're the difference between a rule that fires on every ticket and one that focuses on what matters. You can filter by:

• ticket type, priority, board, assignee, team, labels
• "how long has this ticket been in this status"
• any custom field

The UI helps you here: dropdowns show real statuses, users, teams and labels from your board — no more pasting IDs by hand. For custom fields the input adapts automatically: SELECT, CHECKBOX, NUMBER, DATE or text. For "is one of" / "is not one of" there's a multi-select with chips.

Multiple conditions are always combined with AND. Up to ten per rule.

Actions: What Actually Happens

A rule can do several things in sequence — up to 20 actions per rule, in whatever order you set via drag-and-drop. The main actions:

• Change status — e.g. move to "In Review"
• Assign — to a user or a team
• Add or remove a label
• Post a comment — multiline supported
• Send a notification — to specific recipients
• Create a ticket — e.g. a follow-up with a pre-filled title and description
• Update a custom field
• Add to a milestone or release
• Fire a webhook — out to your own tool, Slack, n8n, wherever
• Trigger an AI agent — an agent takes over from here

What happens if an action fails in the middle of the chain? You choose: continue (default) or stop. That way a Slack ping still goes out even if an optional webhook to a side system hiccups.

Webhooks With Real Authentication

For the webhook action you can now set how Spedy authenticates against the target system right in the rule builder:

• Bearer token — the standard case for most modern APIs
• Basic auth — username and password
• Custom header — any header name with a value, e.g. for signed payloads
• None — an open webhook without auth

Spedy also blocks risky header names automatically, so you can't accidentally click together something unsafe.

Preview Mode: Check First, Then Activate

Every rule has a Dry Run button. One click — and Spedy shows you what would have happened if the rule had already been active:

• the five most recent tickets on your board
• per ticket: which conditions would have matched
• per ticket: which actions would have run

Nothing real happens. Great for trying rules against actual data before you switch them on.

Need a rule to run right now? Run now kicks it off manually — handy when you want a schedule rule to run once outside its normal cadence.

Run Log: What Happened When

Every run — whether from an event, a schedule, or manually triggered — is logged. For each rule you see:

• Outcome: success, partial failure, failure, skipped
• Duration
• Error message if something went wrong

Logs are kept for 90 days and can be filtered by outcome. So you can tell at a glance which rules run reliably and where you need to take a look.

Templates: A Faster Start

Instead of starting from scratch you can pick from the template gallery. A few examples:

• On critical ticket: assign on-call and notify
• Auto-apply the bug label when someone writes "bug" in the title
• Escalate when a ticket sits in the same status for too long
• Kick off an AI agent when a ticket matches specific criteria

Click a template and it opens in the builder — adjust the name, recipients, and details, done.

Board Rules or Organization Rules?

Two scopes, same building blocks:

You reach both via their respective settings. The builder looks the same in both places.

Limits So Things Don't Get Out of Hand

To keep an automation from accidentally going wild, there are a few fixed limits:

And if a rule triggers another rule, which triggers another: after three chain levels Spedy stops automatically. So you can't accidentally build yourself an infinite loop.

Get Started

1. Open a board → Settings → Automations
2. Click Templates and pick a workflow that fits
3. Adjust the trigger and conditions for your team
4. Run Preview — looks good? → Activate

Automations take the routine off your plate. What's left is the work that actually needs your head.