Workflows

Workflow Actions

Execute operations when workflow conditions are met

Actions are the operations your workflow performs. After a trigger fires and conditions are evaluated, actions execute to update tickets, send notifications, call APIs, and more.

Ticket Actions

Action typeEditor labelDescription
set_statusSet StatusChange status (open, pending, solved, closed)
set_prioritySet PrioritySet priority (low, medium, high, urgent)
assign_toAssign ToAssign to user ID, "ai", or "unassigned"
add_tagsAdd TagsAdd tags to the ticket
remove_tagsRemove TagsRemove tags from the ticket
add_internal_noteAdd Internal NoteAdd private note for agents

Communication Actions

Action typeEditor labelDescription
send_replySend ReplySend email reply to customer
send_slack_messageSend to SlackSend a message through a connected Slack workspace
send_webhookSend WebhookHTTP request to an external URL

Teams is unavailable in this release. send_teams_message is a legacy, deferred action type kept only so an existing node can be seen and removed; it is not an executable action and new workflows cannot add or save it.

AI Actions

Action typeEditor labelDescription
generate_ai_responseGenerate AI ResponseGenerate response using AI
classify_ticketClassify TicketAI categorization and sentiment

Platform Actions

Action typeEditor labelDescription
execute_connector_actionRun Platform ActionRun an action from a connected platform

WordPress is the only platform connector in this release.

Using Variables

Actions support dynamic values with double-brace syntax:

  • Ticket: {{ticket.id}}, {{ticket.subject}}, {{ticket.status}}
  • Customer: {{customer.name}}, {{customer.email}}, {{customer.is_vip}}
  • Message: {{message.body}}
  • Workflow vars: {{variables.aiResponse}}

Saving Action Output

Store results for later steps:

actionType: generate_ai_response
config:
  promptTemplate: "Summarize: {{ticket.subject}}"
  saveAs: summary

Use in subsequent action: {{variables.summary}}

Configuration Examples

Send Reply:

actionType: send_reply
config:
  content: "Hi {{customer.name}}, your request has been received."

Webhook:

actionType: send_webhook
config:
  url: "https://api.example.com/notify"
  method: POST
  body: '{"ticketId": "{{ticket.id}}"}'

Error Handling

  • Failure: Error logged, subsequent actions in path skipped, parallel paths continue

Best Practices

  1. Label clearly: "Assign to Billing Team" not "Action 1"
  2. Test with manual trigger: Verify before enabling live triggers
  3. Save AI outputs: Store generated text for later steps

Next Steps