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.

My company has several Zaps that trigger from different Submittable events (e.g. “New Submission” or “Submission Status Changed”), and these Zaps have worked fairly consistently for some time -- in some case over multiple years. However, I recently (yesterday, 10/15) began receiving errors related to the triggers themselves:

Error while hydrating data from Submittable: You do not have V4 API Access Enabled: Contact account management to learn more or to add this feature to your account.

I confirmed with Submittable (both by looking at my integration settings and by confirming with Submittable support) that the API v4 is active in my account. I went through some troubleshooting steps with Zapier support as well, including re-connecting the Submittable app to my Zapier account, refreshing the API key from the Submittable side, and deleting the connection altogether before re-connecting with the new key, The same error continues to appear.

I am able to connect my Zapier account to Submittable, but no triggers are functioning, and I can’t even pull test data. Zapier support seems to think there is an error on the Submittable side, so I’m waiting to hear if there is a fix coming. However, Submittable support seems to think there is an error on the Zapier side, which they cannot fix (additionally, the Submittable API is fully self-service, which means their support has been incredibly unhelpful). 

Has anyone experienced this? Any ideas as to a potential fix? Would appreciate any and all suggestions. 

Hey ​@zgoldberg,

Even after deleting the connecting and reconnecting, if it didn’t fix I would recommending testing the Submittable API directly with something like Postman. If that works, that means your API key is working from their side. Maybe you can share that with support to better troubleshoot. Hope it helps!

PS: If you need more active help, I’m happy to connect through my Zapier Solution Partner page if you’d like to reach out here- https://zapier.com/partnerdirectory/automation-jinn

Hi ​@zgoldberg 

NOTE: Most Zap app integrations are created and managed by the app developer using the Zapier Developer Platform, so you would likely need to work with Submittable Support for help with their Zap app errors/issues.

 

A tip to try when connecting your app account to Zapier is to use a new/different private browser to make sure it is a fresh connection.

 

All of the Submittable Zap app triggers are instant, meaning those are triggered from webhook events sent by Submittable.

However, if the error is in the Zap trigger step, some Zap app triggers that are instant are configured behind the scenes with additional app API requests to fetch additional information, because often webhook events contain a minimal data payload.

e.g. webhook data payload includes the Entry ID, but no other details, so an API request would be need to use the Entry ID to fetch all of the details about the entry.

 

 

If you are looking to hire help, there is a directory of Zapier Partners: https://zapier.com/partnerdirectory

Terms & ConditionsAccessibility statement