Skip to main content
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

Secrets

An input that holds a secret, such as a password or an API key, shows dots. Select Show value to read what you typed and Hide value to hide it again. Under the field, Insert a variable reference puts a reference to a variable in the field, which is the better home for a secret: you replace it in one place and the flow never holds it. People who may only read the flow see ******** instead of the value, and an export or a Git push leaves the input empty. A reference to a variable, a connection or a vault entry is not a secret itself and stays readable.

Files

A file input takes a file from an earlier step, or one that you upload. Select Upload a file to attach a file of up to 10 MB. The input then shows File attached with the name. To use a file that an earlier step produced, insert its reference with the data picker. Collabase checks what the file contains. It accepts PDF, PNG, JPEG, GIF, WebP, ZIP and Office files, gzip and text such as CSV, JSON or XML. Another kind of file is refused with This kind of file is not accepted. A larger file is refused with The file is too large. The limit is 10 MB. A step that produces a file, such as a download, keeps it with the run, and later steps can use it as a file input. Whoever may read the run may read its files.

What a failed input looks like

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 November 5, 2026