This article lists every HappyFox Help Desk action available in HappyFox Workflows and describes what each one does, so you can identify the right action when building or troubleshooting a workflow. Each section links to a dedicated article with step-by-step configuration guidance.
Applicable Plans: Available on all plans.
Ticket properties
Set or update core fields on a ticket — status, priority, category, assignee, due date, tags, and time spent. Use these actions to keep ticket data accurate as it moves through a workflow.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Ticket content
Add or modify content on a ticket — replies, private notes, canned responses, and forwarded messages.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Ticket creation
Create new tickets or related tickets from within a workflow — with or without a ticket template.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Note: Ticket deletion is not supported as a workflow action. To suppress a ticket, use Set Status to set it to a resolved or closed status.
Task management
Create and update tasks attached to a ticket, including applying task templates that generate multiple tasks at once.
|
|
|
|
|
|
|
|
|
|
|
|
Custom fields
Set custom field values on a ticket, its associated contact, or an asset.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Ticket operations
Actions that change how a ticket relates to other tickets, contacts, or agents — or trigger automated processing such as satisfaction surveys.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Warning: Merging tickets is irreversible. Once two tickets are merged, only one ticket remains active.
Contact and contact group management
Create, update, filter, and manage contacts and contact groups directly from a workflow.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Asset management
Link, copy, retrieve, and filter asset records associated with tickets and contacts.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Third-party issue and task linking
Link or unlink tickets to issues, work items, and tasks in connected third-party apps. The relevant integration must be active before these actions are available in the workflow builder.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Note: These actions link existing issues and tasks to tickets — they do not create them.
Frequently Asked Questions
Can I delete a ticket using a workflow? No. Ticket deletion is not supported as a workflow action. Use the Set Status action to set the ticket to a resolved or closed status instead.
How do I stop a workflow that is currently running? You cannot stop a workflow mid-run from within the workflow builder. To prevent future runs, disable the workflow from the Workflows dashboard. For in-progress runs, use Run History to identify the current step and determine whether any completed actions need to be reversed manually.
What is the difference between Relate Tickets and Merge Ticket? Relate Tickets creates a reference link between two tickets — both remain separate and active. Merge Ticket combines a ticket into another ticket raised by the same contact; only one ticket remains active after the merge. Merging is irreversible.