Use the Workflow Builder to create and edit workflows. Each workflow contains a trigger that initiates its actions: API Calls, Logical Steps, and Functions. The Workflow Builder depicts actions as a series of blocks connected by nodes. Each node is a single process that must be completed before the workflow continues to the next. Nodes for If/Else logic steps contains nested sub-nodes, each of which must be completed before the workflow continues. Actions are performed on data that has been retrieved, filtered, and manipulated in previous actions in the workflow.
Note: To create or edit a workflow, you must switch the workflow to Inactive in the upper right of the page.
To understand the Workflow Builder elements, see Workflow Builder Symbols and Action Buttons.
The example shows a deactivated workflow with Add buttons that can be edited.
To add new action
To add an Action to workflow in the Workflow Builder, click the Add button (+) next to an action or at the bottom of the workflow. A new window with the four types of actions opens. Click a tab at the top to choose the type of action for the workflow.
Once the action block is in the workflow, you can click and drag to a position anywhere in the workflow.
Note: If you click the Add button next to a Step, the new action is nested within the If/Else steps or For Each step.
If/Else steps that require nested actions, such as functions or other steps, within them.
For Each step is an iterative process that executes a series of nested steps on each index of data in an array.
Break Point stops the execution of the workflow.
A function is a custom block of Ruby code that accepts a JSON argument and executes the code. Examples: Format data, make ftp call, or perform specific logic.
APIs exchange data between designated applications, or endpoints, without human interaction. An API Call requests data from an application, which in turn sends a response. The request must be properly structured to ensure the response returns data that meets the requests requirements.
Click one of the vendor blocks at the top to view standard API Calls that can be used with that vendor’s application. For example, a list for an API Call that begins in Concur and ends in BigCommerce, or vice verse, contains standard API Calls for your Cloudsnap account.
See Add API Calls.
A trigger mechanism starts the workflow. The trigger defines how data is collected from a particular app then the conditions that initiate the workflow at the source (Point A).
See Configure Trigger.