This article explains how to add and configure an action within a workflow, including how to test each action before adding the next one.
Prerequisites
- A workflow must already be created, with its trigger set up and tested using a sample ticket or event.
Steps
- Log in to HappyFox Workflows.
- Open the workflow you want to configure.
- Click the blank action box to view the list of integrated applications.
- Select an application, then choose an action from its list of available actions. For example, select Create Task.
Note: Actions listed under Workflows are generic utility actions that aren't tied to a specific integrated app, rather than actions performed within a third-party application — for example, Perform Math Operations, Transform Text, Use Lookup Table, Date/Time Formatter, Check Conditions, Delay, and Request Approval.
- Configure the required fields for the action in the right pane. Field values can be static or dynamic:
- Static values are fixed. For example, if you manually enter a task name, every ticket that triggers the workflow creates a task with that same name.
- Dynamic values are pulled from the triggering event. For example, if the task assignee is set dynamically from the ticket's assignee, each ticket assigns the task to whoever is currently assigned to that ticket. See How to Use Merge Fields and Dynamic Variables in HappyFox Workflows for further guidance.
GIF: Populating an action's fields with static and dynamic values.
- Click Save and Test to run the action against your test ticket.
- Log in to the affected application.
- Confirm the action ran as expected.
GIF: Testing an action and confirming it ran successfully in the connected app.
Note: Save and test each action before adding the next one. Field values from earlier actions in the workflow can be reused in later actions.
- Repeat these steps to add each additional action your workflow needs.
- Enable the workflow using the toggle once all actions are configured.
Your workflow now runs each configured action whenever its trigger fires. Next, learn how to use Run History to debug workflow issues if an action doesn't run as expected.