When building in the Platform UI, you’ll use the Input Designer to create the form users will input data into, to send to your app’s API.
first_name
.First Name
.(required)
label beside the field name in the Zap editor, and will not let users complete the Zap step without adding data to that field.
String
, then check the Dropdown option.
["one", "two","three"]
Enter the fields as used in your API, as Zapier will pass the exact value users select to your app. Zapier will capitalize each item in your dropdown menu in the Zap Editor, and will add spaces instead of any underscores, so an option like first_name
would show in the menu as First Name
to users.
Static Dropdown with Key Value Pairs
If your API requires different values for the field than the text you want to show to users inside the dropdown menu in Zapier, make a key value pair that includes the value to send to your API, the sample value to show users (should be the same as the value), and a user-friendly label.
1
or 2
, but 1
actually means pork
and 2
actually means fish
to a user, you could use the following code to add the dropdown menu pictured:
value:label
, which shows to users as follows:
Hidden
to hide this trigger from your app’s trigger list in Zapier.
id
), along with a field that includes a user-friendly name
for the data in that field.
id
) for users to know what type of data the field expects. Users can also choose to enter a custom value
and map data from other Zap steps into this field. Being able to see what type of value to map is extremely helpful.
3. Add search to a dynamic field (optional)
Dynamic Dropdown menus can optionally include an additional Add a Search Step button beside the dropdown menu. This lets users dynamically select the correct item from a dynamic field based on input from previous Zap steps.