Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Input Fields

Questions about working with input fields when building integrations on the Zapier platform.

  • 38 Topics
  • 43 Replies
38 Topics
JacobWolf
JacobWolfNew
asked in Input Fields
Allowing for Creation of Multiple Children on Action

Hey all, I’m an engineer that just joined the team at beehiiv, the email newsletter platform. I’ve taken over development for our Zapier app and am working to make some major updates to it in the coming weeks. I’m new to Zapier development, but not new to Javascript in general. I’m struggling to find a format that allows for the intended use of how a user would input custom fields. We allow for multiple custom fields to be passed on create subscriber and update subscriber requests in our API and they need both the id and the value. To simplify the user experience, I made a Zapier trigger that will fetch the custom fields on a user’s account dynamically and allow them to select by name, rather than needing to know the custom field ID. This works as intended. Here’s how I’ve done that in code. This is the input field: { key: "custom_fields", children: [ { key: "field_name", label: "Field Name", helpText: "Select the name of the custom field.", dynamic: "list_customfields.id.name", requir

2051
O
Adam From Chalo
Adam From ChaloBeginner
asked in Input Fields
Brevo Custom Action challenge - Create a new campaign

Hi Zapier Community, I hope you're all doing well. I'm reaching out here because I'm facing a bit of a roadblock while trying to create a Custom Action for Brevo. My goal is to set up an automation that allows me to create a new campaign through Brevo's API https://developers.brevo.com/reference/createemailcampaign-1. I've followed the instructions provided and used the Zapier custom action assistant, but I seem to be encountering an issue. When I create the Input Fields, I can only see one field called "campaignDetails." However, according to Brevo's API documentation, there should be more fields available for input. I'm not very technical, so I apologize if this seems like a basic question. Essentially, what I'm trying to achieve is to have the ability to control all the fields as per Brevo's API documentation directly from Zapier. Could someone kindly guide me through the process or point me in the right direction? Any assistance or insights would be greatly appreciated. Thank you s

961
Troy Tessalone
I
Iryna S.New
asked in Input Fields
Search through folder structure - Zapier CLI

Hello guys, I´m developing a Zapier App and its required to select a parent-folder to create something inside it. Im using the Zapier CLI and a wanted to ask how to generate a field with a folder-structure-view like shown in the image (example from the Google Drive Zapier App): Is there a documentation in Zapier CLI regarding that? I know that could be achieved with key: "directory", but I need a few triggers with folder structure.

210
I
A
asyBeginner
asked in Input Fields
optional fields that, if present, have required children

hi all, Is there a way to have required children if and only if the parent has been set or to make items required as a group? We’re trying to do something like the following, where (in this example) supplying pets is optional but if someone supplies part of a pet’s information they have to supply all of it. // Doesn't work, ends up effectively making all pets required...inputFields: [ { key: "first_pet", required: false, children: [ { key: "first_pet_name", required: true, type: 'string' }, { key: "first_pet_species", required: true, type: 'string' }, ... ] }, { key: "second_pet", required: false, children: [ { key: "second_pet_name", required: true, type: 'string' }, { key: "second_pet_species", required: true, type: 'string' }, ... ] },...] We can do this with a bunch of custom validation in perform but wondering if there’s a way to do so within the schema.

751
A
T
tpacunBeginner
asked in Input Fields
Matching label text in a dynamic dropdown

Hi all, I’ve got a dynamic dropdown that makes a request to retrieve a list of items and corresponding IDs in order to pass the IDs along: This works great but I’m wondering about trying to extend functionality - how would I go about allowing a user to match on the label (e.g., “T Shirt”) of the Merchandise Item? I of course can setup additional dynamic input fields to drive this if need be (such as what’s written here) but is there an easier way that I’m missing?

2396
M
A
Abdul RahmanNew
asked in Input Fields
Dynamic Input Fields for Actions

Hi, I am fairly new to Zapier ecosystem and writing a Zapier Action to “Create a new Journey”. Journey here is a Table in my DB. The INPUT FIELDS of my action are not static and depends upon the Type Of “Journey”. There are 3 types of journeys. The most basic type has straightforward input fields. The input fields of other types are nested attributes and are totally dynamic. For the example I am attaching a screenshot. internal_stakeholder_attributes and document_custom_fields are dynamic array of objects which may or may not exist depending upon the type of Journey and its Associations. My questions are : 1) How can I make the input fields dynamic ? 2) How can i nest them ?

4891
shalgrim
T
TavDevBeginner
asked in Input Fields
Fields Duplicating

Having an issue with input fields being duplicated when testing an action. The fields are child fields and appear correctly as seen in the image below. When I run a test with the data from the screenshot, the two fields are being duplicated in the bundle.inputData json. They show as both in the header as well as the Item obj sublist. Not sure what I set up incorrectly. bundle inputData { recType: 'salesOrder', rate: '9', quantity: '2', item__obj: [ { rate: '9', quantity: '2' } ] } Appreciate any input on how to set them to only appear within the item__obj list.

703
C
O
open_letterNew
asked in Input Fields
How to pass custom field in zapier trigger

Hi, I am new to zapier integration. I have created a trigger in which have added “User input Fields” like following screenshot. Now I want to add/pass the static variable ---> "mergeVariables": {} in above zapier trigger. How can I pass this, as I cannot see anywhere an option where I could add this static variable. Please help me with this. Thank you.

791
C
billfugina
billfuginaNew
asked in Input Fields
Invalid date formatted to Today

My CLI application/integration has several actions each with one or more datetime input fields. My QA team has reported that when they send an invalid date string, e.g. `2023-02-31`, it is converted to today’s date and time. I have put some console logging into the action perform function and confirmed that when the rawInput value is an invalid date, the input value is today’s date. I have been asked to treat invalid dates as an error and to halt execution. I have considered adding code that checks the input value and if it is today’s date, then inspects the rawInput to determine if the original input was an invalid date. I think this sounds much easier said than done. Is there an easier way to do this? Is there some way to get the formatter to not convert invalid dates to today?

441
C
G
Grid DevNew
asked in Input Fields
How can I use dynamic fields when they are nested within an object

Hello, I am in the process of integrating my app with Zapier. I have successfully created triggers for my app. However, I am encountering difficulties in understanding how to utilize dynamic fields in the actions I have created, especially when they are nested within an object (please refer to the attached screenshot). I would greatly appreciate any assistance you can provide. Thank you in advance!

920
G
Tytila
TytilaBeginner
asked in Input Fields
_zap_static_hook_code

I’m using the CLI to create a trigger that accepts dynamic fields. It works fine, except that I’m finding bundle.inputData contains an extra field called “_zap_static_hook_code”. If I send bundle.inputData to my API in the body, as I’ve done with actions that use dynamic fields, it causes my API to error because it’s not expecting that field. Can anyone tell me where this field comes from, or why it seems to appear in the inputData for a trigger but not an action? I have a workaround, using JavaScript decomposition to create a copy of bundle.inputData with that field removed. But I’d be more confident about the reliability of my workaround if I understood why it was happening in the first place. If this is some internal Zapier variable that’s getting exposed, then the name of the variable might change in the future and then my workaround would stop working.

560
Tytila
ado2000
ado2000Beginner
asked in Input Fields
passing inputdata to an action formatting the output

Hi all, i have this api request for my action const options = { url: 'my-ap-urli', method: 'POST', headers: { 'Accept': 'application/json', 'Cookie': `JSESSIONID=${bundle.authData.sessionKey}` }, params: { }, body:{ "items": [{ "properties": { "Contact.name": bundle.inputData.contactName, "Contact.surname": bundle.inputData.contactLastName, "Contact.email": bundle.inputData.contactEmail } }] }} what I need is to add the dynamic fields that are present in the bundle input data. How can I add the input data in my properties formatted in this way? "Contact.key": value Thanks

581
B
B
boulderobertNew
asked in Input Fields
Zap works perfectly except not delivering dynamic field data to server when testing action

This post has been edited by a moderator to remove personal information. Please remember that this is a public forum and to remove any sensitive information prior to posting. Going crazy here because my Zap appears to be working perfectly, right up to the point where some of the data fields are not being delivered to the server. I am using a webhook as the trigger, and test data is being delivered correctly to the trigger test. My action captures that data, all fields are mapped properly, as you can see in the attached picture. But then when I test the action and look at the data delivered to the server, some of the fields are missing. The missing data comes from dynamic fields, so I assume that's my problem, but the action shows all of the expected key/value fields properly. How can it display all of that properly, but then not deliver the data to the server? Any help appreciated, but please don’t bother pointing me to the documentation for dynamic fields. I have read all that and sti

4114
M

Quick Nav

Get Help
Zapier Events
Learn and Share
For Developers
Actions
AI Actions/Zapier MCP
Authentication
Data Structuring
Embedding
Error Handling
File Objects
General Discussion
Input Fields
Rate Limits
Testing
Triggers

New Answers

Popular Tags

Terms & Conditions