Services Plugins FAQs

Quickbooks Accounts - Need authorization help

Hello all,

Got the Quickbooks plugin. But hit a wall with authorization.

So far…

  1. Set up domains and redirects
  2. Selected my app for authorization code
  3. Set my scopes
  4. Got my tokens and put them in the plugin settings

I’m currently on the part where I need to create a data type for the refresh token. I created a data type called “Quickbooks Token.” I named it “Old Refresh Token” and set the type to “text.” Then I created an entry using the refresh token from Quickbooks.

This is where I’ve run into some issues.

In the example, the next selection would be “refresh_token” but I don’t see that as an option and I’m not sure where you guys are pulling that from.

I’m also struggling with the set state.
I’m not sure I set up the left side correctly but it seems happy.

For the right side, the error message is “Set state: Value should be a Quickbooks Token but right now it is a GET NEW ACCESS TOKEN (QB Pro).”

Any ideas on how to fix these issues? I’ve been working on this for a while, and I’m still struggling. I’m non-technical, if that wasn’t obvious haha

Thanks in advance.

Hello @tkruger3902,
Thanks for reaching out!

Due to the fact that we have some additional questions regarding your settings, can you please add our Support email to the list of collaborators to your application and provide me a link to your application, so I can take a look at all the issues you have?

To add our Support Team as a collaborator, you need to do the following steps in the Bubble Editor:

Settings > Collaboration > Add email support@zeroqode.com. You can do this even if your app is on the Hobby plan, as our account is on an Agency.

This will allow us to identify any possible cause much faster. :pray:

Looking forward to your reply.

Regards,
Gulce

@Gulce Hey, just added you. Here’s the link: Simple-recruiting-app | Bubble Editor

The app doesn’t have anything to do with quickbooks…just trying to figure it out before I get it setup in the real thing. The relevant page you’ll want to see is called “quickbooks-test”

Thanks so much!

@tkruger3902, Thank you for providing access. :pray:t2:

Let me please check the issue, I will get back to you as soon as possible.

Best regards,

Hi again! @tkruger3902,

Currently, I’m checking your app but the old refresh token field in the database where you need to paste your Refresh Token is empty. Can you please make sure you specify the Refresh Token in the Old Refresh Token field?

Summary


Hope to hear from you soon.

Thanks!

@Gulce It appears to be there on my screen. Is it empty on yours?

@tkruger3902, it was empty for some reason on our end but right now all is good. :slightly_smiling_face:

So, the issue was related to the Access Token state type which is Quickbooks Token (type) on your page. However, it should be “Get new access token (QB pro)”. I’ve created a test page in your app (zq_test) and changed the type of the custom state. Now, everything seems fine.

Please take a look at our test page and give it a try.

Summary



Best,
Gulce

@Gulce The workflows look great, but it’s still returning an HTTP 403 error. Do you guys do consulting? This is extremely important, and I’m more than happy to pay for an hour or two of your time to get this set up right. Thanks.

Hello @tkruger3902,

Unfortunately, we do not provide the implementation for plugins as support - this is beyond our support services. Sorry about that and thank you for your understanding. :pray:

I strongly recommend you check the plugin’s live demo page, the demo editor page and the docs in parallel to see the workflow and setup. You can always refer to these when creating your app and need to implement the functionality.

Still, let me please check this error with our developer team, I will get back to you with feedback as soon as possible.

Best,
Gulce

@Gulce Okay, great. Please let me know what the dev team says. Probably an issue on my end, I just don’t know what it is. Thanks!

Hello @tkruger3902,
Thank you so much for your patience. :pray:t2:

We’ve updated the plugin and fixed the issue with the authorization. Everything seems fine now. :slightly_smiling_face:

Please check it on your side and let me know how it’s going.

Best,
Gulce