Workflows

Workflows automate repetitive ticket operations with a visual node builder.

Availability

Workflow access requires:

• Organization role: owner or admin
• Plan: growth or enterprise

Builder model

A workflow is a graph of:

• Trigger nodes
• Condition nodes
• Action nodes

Current trigger nodes

• on_ticket_created
• on_status_changed
• on_ticket_assigned

Current condition node

• if_condition (expression-based branching)

Current action nodes

• change_status
• change_priority
• assign_to_user

Practical use cases

1. Route new tickets from specific templates
2. Escalate priority when status changes indicate risk
3. Auto-assign ownership for repeatable categories

Start simple, then layer conditions to avoid brittle automation.