Workflow steps

Learn about the different steps that make up a workflow

Workflows are constructed with steps. Middle has five different types of steps that you can use to build out your workflow: Begin, Decision, Action, Bulk Workflow Execution, and File Export.

Adding a new step

To create a new step click on the plus symbol on one of your workflow branches.

Build your workflow with nodes

Begin

The Begin step allows you to input global variables, such as the triggering record, the previous version of the record, or any other input from the trigger.

Workflows triggered by a scheduled trigger will not have any inputs.

From the begin node you can select which record type you would like your workflow to perform on

The above example is a classic example of a Begin step that is only inputting record. The foreign key references the primary key of the trigger-inputted or manually executed record. The "Key to?" tells Middle which record type is being inputted.

Decision

Either true or false, Decision steps route to one of two branches depending on whether their criteria is met. Within Decision steps, you will construct true/false logic.

Decision nodes are operated on from top to bottom.

Decision nodes allow you to filter and route your workflows

Action

As a workflow builder, you will construct dynamic and static inputs into Action steps. These inputs are then used in the function being executed by the Action step. Actions have outputs that can be referenced as global variables later on in the workflow.

Actions are generally setup as forms where you can map data from Middle to another system

Bulk workflow execution

Bulk workflow executions will trigger another workflow to run. When you set up a bulk workflow execution you define a synced record type that the workflow will run on. Used in conjuncture with scheduled triggers, bulk workflow executions can be a powerful tool.

Select the workflow and data you'd like Middle to bulk execute on

File Export

The file export step allows you to export a .bz2 file of synced data stored in Middle. This file can then be accessed via a download URL in downstream workflow actions.

When configuring your file export step you can select the data type you'd like to generate a file for, the fields you'd like included in the file, and whether the data should be filtered by the last updated timestamp.

Last updated

Was this helpful?