Connecting Data in Your Flow Steps

The functions & apps you use in your flow steps allow you to specify what data should be mapped to the input fields each step (function) expects.

For example, in the image below, we're using a function called twitter-search which we've specified requires two input fields: a searchTerm and a sinceId. You can edit the package.json of a function to specify what input fields (parameters) a function expects. Read our docs on Editing the package.json file for functions more info

Screenshot 2019-01-04 09.02.45

Connecting Data from Previous Steps

You are able to select data that was passed in from previous flow steps by hitting the plus icon on the right of the input fields, which help you autocomplete the syntax to bind to data from a specific step.

Screenshot 2019-01-04 09.07.47

The syntax for connecting to a previous value is:


or if you're connecting to a value from the trigger, the following works:


Connecting Explicit Values

You can also pass in an explicity value to an input field, if you want it to use that same value every time the flow runs. For example, if we wanted the searchTerm input field to always take in the string "Mountain Climbing" we could just pass that in explicitly as follows:

Screenshot 2019-01-04 09.10.11