About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

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

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

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.

Question

Failed to find or create a customer in Visma eAccounting

  • 24 February 2023
  • 1 reply
  • 101 views
Naturhelse

The app returned "579c87ab-ad98-47a2-8a5a-b469a5a4b1c1".

Trying reestablish this connection and have filled in all fields required but stuck as this error.

Plugins is up to date as of today and API connection is allowed in eAccounting. No help from Visma eAccouting for this error.

1 reply

SamB
Rank
Userlevel 7
Badge +11

Hey @Naturhelse, welcome to the Community!

Hmm, we can see that sort of error sometimes when a field isn’t passed the correct type of value. For example a date field that’s expecting a date in MM/DD/YYYY with the date passed in the incorrect format of DD/MM/YY.

So I wonder if one of those required fields is expected to receive a value in a certain way. Would you mind sharing a screenshot of the set up of that Visma eAccounting action in your Zap? Please remember to remove/hide any private information like names, emails from it first.

That way we’ll be able to take a look at the values being passed into each of those fields to check whether that’s the cause of the error here. Looking forward to hearing from you! 🙂

Reply


Terms & Conditions