Automations

Automations let you turn repetitive board work into background rules. "When a critical ticket is created, assign on-call and notify the #incidents channel." "Every Monday at 9, send a weekly report webhook." You set up the rule once; Spedy takes it from there.

Automations are part of the Pro plan. They live in both board settings and organization settings.

How an Automation Works

Every rule has three parts:

1. Trigger -- the event that starts the rule
2. Conditions -- optional filters that decide whether the rule should run
3. Actions -- one or more steps that happen when the rule runs

If you can say it in plain English -- "when X happens, and Y is true, do Z" -- you can build it as an automation.

Triggers

You can choose from 14 triggers:

• Ticket events -- created, updated, deleted, status changed, assigned
• Label events -- label added, label removed
• Comments -- new comment on a ticket
• Custom fields -- a field value changed
• Project progress -- milestone reached, release created
• Pull requests -- merged, status changed
• Schedule -- runs on a time schedule (minimum interval: 15 minutes)

For schedule triggers, quick-select buttons let you pick common intervals (every 15 minutes, hourly, daily, weekly) without having to write a cron expression.

Conditions

Conditions are optional, but they let you scope a rule to specific cases. You can filter by:

• Ticket type, priority, assignee, team, labels
• How long a ticket has been in its current status
• Any custom field on the ticket

The condition builder uses live data from your board: pick a user, team, status, or label from a dropdown -- no IDs to copy. For fields like select or checkbox, the value input adjusts automatically. For "is one of" / "is not one of", you can pick multiple values.

Multiple conditions on a rule are combined with AND. You can have up to 10 conditions per rule.

Actions

Actions run in order, one after another. You can reorder them by dragging. A single rule can have up to 20 actions.

Available actions:

• Change status -- move a ticket to a different status
• Assign user / team -- set the assignee or team
• Add label / Remove label
• Post a comment (supports multi-line content)
• Send a notification to a specific recipient group
• Create a ticket -- with a pre-filled title, description, priority, and more
• Update a custom field
• Add to milestone / Add to release
• Send a webhook -- to any external URL, with optional authentication
• Trigger an AI agent -- hand off to an agent that takes context into account

If an action fails

You decide what happens if an action in the chain fails:

• Continue (default) -- skip the failed action and keep going
• Stop -- abort the rest of the chain

That way a critical notification still goes out even if a secondary webhook hiccups.

Webhooks With Authentication

When you add a Send webhook action, you can configure how Spedy authenticates against the target system directly in the rule builder:

• Bearer token -- sent as Authorization: Bearer <token>, the standard for most modern APIs
• Basic auth -- username and password, Base64-encoded
• Custom header -- any header name and value, useful for signed payloads
• None -- open webhook without authentication

Spedy also blocks risky header names (Host, Connection, Transfer-Encoding, Proxy-Authorization, Content-Length) so you cannot accidentally create an unsafe webhook.

Preview Mode (Dry Run)

Before activating a rule, click Dry Run to see what would happen. Spedy takes the five most recent tickets on your board, evaluates the rule against each one, and shows you:

• which conditions would have matched
• which actions would have run

Nothing is actually changed. It is the safest way to test a rule against real data.

Run Now

For rules that should execute outside their normal cadence -- typically schedule rules -- click Run now. Spedy queues an immediate execution.

Run Log

Every execution is logged for 90 days, no matter how it was triggered. The log shows you:

• Outcome -- success, partial failure, failure, or skipped
• Duration
• Error details if something went wrong

You can filter the log by outcome to quickly find problem rules.

Templates

You do not have to start from scratch. The template gallery in the rule builder ships with ready-to-use workflows:

• Notify on critical ticket
• Escalate after X days in a status
• Auto-label tickets based on title keywords
• Hand off to an AI agent when criteria are met

Click a template and adjust it for your team.

Board vs Organization Rules

Automations live at two levels:

• Board rules -- scoped to a single board. Best for team- or project-specific workflows.
• Organization rules -- scoped to the whole organization. Best for cross-board workflows and time-based jobs.

You reach both through the matching Settings → Automations section. The builder looks identical.

Permissions

Two permissions govern access:

• automations:view -- see rules and the run log
• automations:manage -- create, edit, toggle, run, and delete rules

Assign these through your organization's permission groups.

Limits

If a rule accidentally chains into another that chains again, Spedy stops at the third level so you cannot build an infinite loop.

Getting Started

1. Open a board and go to Settings → Automations
2. Click New from template or Create rule
3. Configure the trigger, conditions, and actions
4. Run Dry Run against recent tickets
5. Activate the rule

For organization-wide rules, do the same under Organization Settings → Automations.