Skip to main content

Hi there!

I'm pretty sure I've run into a bug, so feel free to recategorize this.

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

This contradicts the documentation saying that dynamic outputFields work just like dynamic inputFields -- with dynamic inputFields, the automatic evaluation and merging seems to work as advertised.

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.

Hi @Max Wagner 

If you are building a Zap app integration using the Zapier Developer Platform, make sure to post your topic in this category: Developer Zone


I've repostet the topic in the Developer Zone as

Any reader interested in follow-ups should check there as well.


Reply