Each step draws its inputs from what the plug action asks for. A picker offers what you may use, a date offers a calendar, and a list offers rows. This page lists every kind of input and how it behaves. In all of them, a value can come from an earlier step: see Passing data.
Text and numbers
Dates and time
Date, date and time, and number inputs have a switch next to the label. Use it to insert a date or a number from an earlier step.
Choose from a list
Pickers for objects and people
A picker lists what you may use and stores the id. It has three modes: pick from the list, enter the id, or insert data from an earlier step.
People and groups
Steps that notify or ask people take a list of people and groups. Search by name, choose a person or a group and repeat. A group stands for all its members who are not guests and not switched off. Each person is reached once, even if they are in several groups or named twice. A notification takes up to 50 people, an approval up to 50 and an agent step up to 20 approvers.
Filters
The Search action asks for a kind of object and filters. Build the filters with the filter builder, or switch to Query to write the search query with completion. Both write the same query, and the list of fields depends on the kind of object. An empty query finds everything the service account may see. Values may contain data from earlier steps.
Lists and rows
Files
A file input takes the address of a file or data from an earlier step that holds a file.
A step cannot be published while a required input is empty. The flow shows the number of open issues, and the step is marked Incomplete. If an input holds something the action cannot read, the step fails when it runs and the message names the input, never its value.
Last modified on October 26, 2026
