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.

I have been trying to find a way to define dynamic output fields for a hook trigger so that they would be available in the later steps but been having no luck. I saw this post which would be similar to my case, but no input values will be taken from the user.

 

This is the a sample payload for the performList:

{
  "id": "123456",
  "customFields": {
     "fieldName1": "fieldValue1",
     "fieldName2": "fieldValue2",
     "fieldName3": "fieldValue3",
  }
}

 

The field names would vary depending on the account subscribed to the hook, and when there are changes made to the field values, the payload will then include a to and from fields for the field that changed, i.e.:

{
  "id": "123456",
  "customFields": {
     "fieldName1": "fieldValue1",
     "fieldName1To": "fieldValue1To",
     "fieldName1From": "fieldValue1From",
     "fieldName2": "fieldValue2",
     "fieldName3": "fieldValue3",
  }
}

 

How can I define the output fields for the To/From fields so that these would be available in the action step? Any and all help would be greatly appreciated. Thank you!

 

P.S. I’m using the CLI for the integration.

Hi @temr,

Seeing that you are already using the CLI platform, in the trigger’s code, add a function that would fetch the account-specific extra fields. These fields should be returned in the same format (schema as an input field).

Then in the output field definition, call this function. This would render the dynamic output fields along with the statically defined output fields.

The following articles should also help:

 

All the best,

Hi @Osas ,

 

Thanks for responding. Though that was my roadblock earlier, currently we don’t have a way to fetch the ‘To’/’From’ fields since this isn’t being stored, rather it’s sent dynamically. But I was able to figure it out. I manipulated the response being sent in the performLoad to add the necessary key-value pairs.

 

Looks like that worked for both the Zap setup and the Live Zap.

 

Thanks again. :)

Reply


Terms & Conditions