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.

Hello,

My team is building a Zapier integration where users connect an account via an API key. After going through the “Add Connection” flow I get a 404 screen in Zapier’s UI.

From the network console it seems to be a failing GET request to the following path: https://zapier.com/_next/data/app-management-3064226381e35ed03bc1802ce3770ac91d194f7e/app/connections/null.json?hl=ssomeNumericalId]&serviceSlug=null

It appears that despite the 404 screen, the credentials are added successfully.

When checking the API key auth it doesn’t appear to have some requested return data, so I am not sure how to resolve this 404 screen, as it is a poor user experience.

It only appears to occur when adding it through the “My Apps” tab. Adding a connection via setting up a trigger or action doesn’t result in this behavior.

The integration app is currently Private as it is under development. Does this matter?

Thanks.

-Justin

Hey @Justin K Bento 👋

Thanks for reporting this behaviour! I did some digging and this relates to an open issue we have where adding a Private connection via My Apps responds with a 404, but the new connection is still created successfully. I don’t have an ETA on a fix at the moment unfortunately, and as you’ve noted, adding a connection within the Zap Editor won’t see that 404 redirect. 

Terms & Conditions