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.

When I use the https://zapier.com/ platform I can create Zaps that work with Loop and Formatter, however, when I use https://developer.zapier.com/ to create official templates, it does not work. On the developer platform, it does not handle the data correctly for the Loop and Formatter plugins.

Developer platform: When I create values to loop, they don’t show up in the test. 

 

Developer platform, the test:


What it looks like on the official zapier.com:


Since the loop does not output the filenames and URL in the developer template, I can’t continue building the template. I experienced a simliar problem with the formatter.

 

Let me know if you have any suggestion. 

Hi @emilwallner ,

I’m afraid what you’re seeing is related to a limitation with Zap Templates. 

In the context of Zap Templates, apps are unable to use real data. Instead, steps simply output pre-defined sample data, which can then be mapped to later steps. 

Since the output for Formatter and Looping can vary from user-to-user and Zap-to-Zap, the sample data for these two apps is pretty minimal, containing only the fields we can guarantee will always be available in the output. For more custom field mappings, users would need to handle their own mapping after starting a Zap with the template.

I apologize as I understand this is a noteworthy limitation, and I’ve shared feedback with the relevant team. 

Thank you for your detailed explanation. I was indeed under the impression that the pre-defined sample data would enable me to create templates. I was hoping to create a simple plug-and-play solution.

However, realizing the limitations, I’m creating video tutorials for each integration to show users how to integrate each Zap. This will require more time and effort for each integration, and adds a layer of complexity for the users.

I appreciate your understanding and assistance in this matter. Should there be any changes or updates regarding this limitation, I'd be grateful if you could keep me informed.

Reply


Terms & Conditions