Data inputs

Control the data that your workflow performs on

Using a combination of the begin node and workflow triggers, Middle gives you control over what data is passed into a workflow. Generally, you will input the most recent version of a record into your workflow to perform timely, up-to-date automations. Particularly powerful is Middle's ability to also pass into a workflow the last version of the record. This allows you to generate logic off of record changes over time and create events or actions based on these changes.

Historic record inputs

Because Middle stores synced data, you have the ability to include the last version of a record in your workflow. To do this, you will need to open up the begin node and insert an additional input to the default "input_record" that you get when you create a new workflow. Give this new input a key and name that makes sense. If you are inputting the previous version of an individual's membership type to determine if someone upgraded their membership, you might want to give it a key of "last_member_record" and a description of "Last Member Record." You'll need to select the data type for the previous record you are trying to input. If you just want to reference a single field on the last record, then you'll need to define the data type for this field, such as a string or number. If you want the entire object, you should select the object data type.

Once the Begin node is all set, you'll need to map your inputs in the workflow trigger. If you have not created a workflow trigger for this workflow, you'll want to go ahead and do so. First select the workflow the trigger is meant for. Next to it will be a section for workflow inputs. Go ahead and click to construct an object in the parameter menu. This object should reflect the inputs in the workflow's begin node. You can then map the data to the workflow's inputs. It's important to note that the data types in this object need to reflect the begin node you constructed, otherwise you may receive an error.

You can now reference the past version of a record as a variable in your workflow. This is particularly useful to identify events that are not inherent in the source system's data, such as an individual's change in status.

Last updated