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.

Hi.

 

When I tried to create a new App connection, I received this error:

 

Zapier could not connect to your account.

Got 401 calling GET https://disco.crm2.dynamics.com/api/discovery/v9.0/Instances, triggering auth refresh.

 

I read an article:

But I think we have recommended API version.

I attached a screenshot:

 

Could you help us.

Hi @CitMKT 

If you need help, it may be best to open a ticket with Zapier Support here: https://zapier.com/app/get-help

Getting error on connecting to Dynamics

  • Our integration currently works with v8 and v9 of the Dynamics REST API.
    If you're using an older or newer version (9.1 or greater), you will not be able to connect to Zapier.
    If you use a newer version of Dynamics, please contact Zapier support so we can register your interest.
  • We don't support self-hosted instances of Dynamics yet.

Just to follow up on this one, it looks as though @CitMKT reached out to our Support team and were added as an affected user on an existing bug report for this issue.

For anyone that thinks that they may also be running into this same issue, please reach out to the Support team via the Get Help form. They’ll be able to dig into your Zaps to confirm whether you’re being affected by the same issue and get your details added to the report! 

Hey friends, I wanted to swing by and and mention this bug has been closed on our end! 

If you’re still running into this error feel free to open a ticket with my friends in support and they’ll be happy to dig into this with you. 🙂

Terms & Conditions