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’m aware App Extensions is a new feature, but is there any documentation on being able to use the pre-defined triggers for dynamic drop downs in App Extensions. I can see the note around this on the App Extensions editor states:

Note: dynamic dropdowns are powered by pre-defined app triggers and therefore not all API data objects are supported. Example: channel.id refers to Slack Channel Ids returned from the Slack Trigger

Using Microsoft Dynamics 365 CRM as an example, let’s say I want to build an App Extension that is similar to the Create Lead action from the public app but the body data is customised because the payload data needs to be modified for our CRM environment in order to successfully send the data. Can I utilise dynamic drop downs like the Create Lead action does on fields like Boolean, Picklist, Lookup etc?

Is there any documentation on the pre-defined app triggers for public apps or will there be? As the App Extension is linked to the public app and our connection, I’d assume the same API calls are still occurring to be potentially used. I’ve been trying to determine the pattern from some trial and error:

Dynamic input must follow the pattern 'contact' or 'contact.name' or 'contact.name.first'. Only a-z, A-Z, 0-9, and _ are allowed

This at least gives me a clue what the format should be, but I have no idea what is available to begin with (if anything).

In this case, what is the main object that contains field data from the lead entity?

With a bit of trial and error I’ve found that the lead object followed by the field name e.g. lead.field seems to work, it provides the values but without labels, so it’s close but not quite right, I assume behind the scenes there is a query being made to EntityDefinitions or similar to obtain these values.

Terms & Conditions