Workflows

Actions

Overview

Actions define what happens when a workflow's conditions are met. You can add multiple actions to a single workflow, and they will execute in order.

Available Action Types

Assign Ticket

Assigns the ticket to a team member or team. There are four assignment strategies:

  • Specific member: Assign directly to a chosen user.
  • Team: Assign to a team without selecting an individual.
  • Least busy team member: Automatically assigns to the team member with the fewest open tickets. This helps distribute workload evenly.
  • Random team member: Assigns to a randomly selected member of the chosen team.

When using team-based strategies, you must select which team to use.

Add Tags

Attaches one or more tags to the ticket. Select from existing tags in your workspace. Tags are additive, so any tags already on the ticket will remain. This is useful for categorization and filtering.

Set Status

Changes the ticket's status. Available statuses are open, closed, and spam. For example, you could automatically close tickets matching known spam patterns or reopen tickets that receive a new reply from a specific domain.

Send Auto-Reply

Sends an automatic reply to the customer. Write your message text in the configuration field. The reply is sent as a regular outbound message from your workspace, so the customer sees it as a normal email response. Use this for acknowledgment messages, out-of-office notices, or initial response templates.

Add Internal Note

Adds a private note to the ticket that is only visible to your team. This is helpful for documenting why a workflow was triggered or leaving instructions for the agent who picks up the ticket.

Send HTTP Request

Sends an HTTP request to an external URL, allowing you to integrate with third-party services. You can configure:

  • Method: GET, POST, PUT, PATCH, or DELETE.
  • URL: The endpoint to send the request to.
  • Content type: JSON or form-urlencoded.
  • Body: A JSON template with dynamic placeholders.

Available placeholders include {{ ticket.subject }}, {{ ticket.status }}, {{ ticket.url }}, {{ contact.email }}, {{ contact.name }}, {{ channel.name }}, and more. These are replaced with actual ticket data when the request is sent.

Configuring Actions

Each action type has its own configuration panel that appears when you add or edit it. Required fields are validated before the workflow can be saved. You can reorder actions by dragging them, and they will execute in the displayed order.