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.

We have an AMP form on one of our pages that posts to a Zapier webhook endpoint. The data is being sent to Zapier just fine but the response from Zapier has an improperly formatted header that causes the AMP-form to throw an error. This, in turn, stops the submit button from being disabled and is causing some users to inadvertently submit multiple identical forms.

Does anyone out there have experience using Zapier webhooks with AMP-forms? Any help would be greatly appreciated.

 

Response header from Zapier nice plug 😉 ]
Error messages in chrome developer console

 

Hi @Morgan & Morgan Developers - This issue has something to do with your fetch call. It’s being called with credentials: ‘include’. Try removing it from your fetch call and see if that works.

Hey @Morgan & Morgan Developers, I hope you’re doing well, I just wanted to check in here!

Were you able to get this working with the information shared by Ikbel, or can we still help out here?

Hey @william @ikbelkirasan, thank you for checking in! Unfortunately AMP forms do not support configurable credentials, so removing `credentials: include` doesn’t seem to be an option.

Terms & Conditions