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.

Hi there!

There's no category for Output Fields, so I'm posting it here. I’m pretty sure I've run into some bugs w.r.t. dynamic output fields.

It seems like dynamic output fields are only evaluated either:

  • Once the workflow action is fully configured and a “Test node” action is performed, or
  • If the dynamic field generation callback is the only outputField in the outputFields list

The docs say that dynamic fields are automatically evaluated and merged with the static output fields. This hasn't been my experience. Something seems to be bugged there.

Also, it seems that the interactions with altersDynamicFields don't work at all for dynamic outputFields. I would expect that if I mark an inputField as altersDynamicFields, then a change in the inputField value would also trigger a re-evaluation of all dynamic outputFields (after all, if even the configuration of the node is dependent on this value, how can you expect dynamic outputFields to stay static?). This also doesn't seem to work, though I'm not sure if it counts as a separate bug or is just some weird effect of the same bug.

EDIT: I’m using the CLI SDK, for the record.

Be the first to reply!

Reply


Terms & Conditions