How do workflows interact with tickets?

A ticket can trigger workflows, host approvals, and collect replies that resume a paused run—without duplicate noise loops.

Tickets and workflows work together in three main ways.

1. Triggers

Workflows can start when a new ticket is created, when a new message arrives, or when an internal note is added—if your admins enabled those triggers for that workflow.
Automated messages generated by the workflow itself are ignored as triggers so the same flow does not re-trigger forever.

2. Linked runs

A workflow run can be attached to a ticket your team is already viewing.
Updates from the workflow (questions, approvals, outcomes) appear in the ticket thread when configured, so support sees a single timeline.

3. Human input

A paused workflow can wait for a reply on the ticket. When someone posts a normal message, the workflow can resume and read the new context (exact behavior depends on how the step was configured).

Example

An employee opens a ticket about relocation. A workflow triggered on new ticket asks structured questions on the thread, waits for answers, then routes internally when complete.

Guardrails

Align triggers with which inbox or group should start automation—avoid running payroll workflows on IT tickets by mistake.
Train agents on when not to post bot-style test messages that could trigger the wrong automation during debugging.