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 have added the subdomain verification logic everywhere in authentication as well as in the Action Api Endpoint I am verifiying the subdomain before calling the url. Still I am unable to pass this warning.
The code I have added is attached below. I am unable to figure out why I am still getting this warning. Please Help.

Also I have an unpublished previous version and then I have worked on a newer version Will both my versions be published if I publish the latest one???

if (!/^[a-z0-9-]+$/.test(bundle.authData.subdomain)) {
 throw new Error(
   "Subdomain can only contain letters, numbers and dashes (-)."
 );
}

Hi ​@aparajeya,

Which authentication type are you using on the integration?

Note that subdomain validation is recommended for an authentication method that uses pre-configured tokens or secret values (for example, OAuth 2).

If you are using a different authentication type, then this may not be necessary.

Cheers,

i am using session auth, i have also same issue, how i can resolve this warning?

Hi ​@aslam1286 

You can see information on how to resolve this here: Validation Check D026

If however, your authentication does not use “inputFormat” or domain-related authentication fields, then this can be ignored. Unlike “Publishing Tasks” and “Errors”, validation “Warnings” are non-blocking and would not prevent you from publishing an integration or promoting a version. If they can be addressed, then you should address them. However, if they are not relevant to your integration, then they can be ignored.

Hope that helps.

Terms & Conditions