Shopify GraphQL - Shopify Payments, Payouts

Integrator.io
1

Hi,

I'm working on custom flows for Shopify, and so far, I have been able to create GraphQL flows for all my needs.

The only area I'm having an issue with, is Shopify Payments. When I try query a shopifyPaymentsAccount, I'm getting permission issues:

"message": "Access denied for shopifyPaymentsAccount field. Required access: the read_shopify_payments or the read_shopify_payments_accounts access scope.",

I've been trying to troubleshoot this with my customer (they own the Shopify store), but in the end, I realized that since I'm connecting to Shopify using the Integrator.io Shopify App, it's the App that is probably missing the right permissions.

In investigating the App Permissions in Shopify, I do see this:

image
image957Ă—217 7.19 KB

So, I'm not sure how else to troubleshoot that.

Has anyone been able to handle Shopify Payout information through GraphQL using Celigo at this point?

Thanks in advance,

2

The API permission your customer needs to grant is the “View Shopify Payments Accounts”, as you can see is separate from viewing payouts and disputes:

image
image1372Ă—722 44.7 KB

3

Thanks for the answer, Chris. To which user should they grant this permission? In my mind, the Integrator.io Shopify App needs to have this permission, and I think this is out of my control.

My user itself is a super user with all these permissions. So I'm still stuck.

Thanks for any further info,

4

Ah I see what you mean. So for my Shopify GraphQL connection, i created a custom app in my Shopify Admin and manually set all the API permissions under Configuration. Once you install it, you get an API access token. In Celigo, the Shopify connection auth type is not OAuth 2.0 but Token and I enter the token I got from Shopify. So it doesn’t utilize the Integrator.io Shopify app at all. I don’t know if it’s possible to edit the API permissions for that.

image
image762Ă—428 26.7 KB

image
image759Ă—807 54.4 KB

5

Chris... this is exactly what I needed to know. We definitely cannot change the permissions for the Integrator.io app, Celigo would need to do that (@tylerlamparter , could you chime in if possible?)

But knowing that there's a possibility of creating a "Custom App" in Shopify and still use the Shopify Connection in Celigo, that's gold!

Really appreciate your input on this. From what I see now, the customer did contact their Shopify specialist in trying to troubleshoot this, and apparently their Shopify specialists created a Custom App. But they never set up the connection in Celigo with such access.

Thanks!

If Tyler doesn't chime in (as this needs to be changed in the Integrator.io App), I'll mark your answer as the best solution for this topic.

thanks again.

6

I suspect we have this in the roadmap to add in, but am waiting for some internal confirmations. With any app change, we have to go through Shopify's approval process so it can take some time to make any changes like this.

The custom app is a great approach in the meantime.

7

Thanks for sharing this request Marcelo. We will be updating the Shopify connection to include these scopes, subject to Shopify’s approval. We’ll share updates as we make progress.

8

@tylerlamparter thank you! @nileshkumar , nice to see you here. It's been a long time.

Thanks for sharing this info. If this helps, I've ran into another roadblock with GraphQL access scopes: Returns.

I tried getting a Return field using the Orders Query, using GraphQL, and it seems it's also denied under the current access scopes:

image
image637Ă—272 16.9 KB

Great to hear about these improvements in the Shopify Connector so that we can keep migrating customers fully into GraphQL.

Thanks tons!

9

Thanks for sharing the return scope details.

In the updated scope list, Returns is also included. We will make sure to support both read_returns and write_returns. I’ll keep you posted as the scope gets added and enabled.

10

Hi Marcelo

The following scopes have now been added to the Shopify GraphQL connection:

  • read_shopify_payments_accounts
  • read_returns
  • write_returns

This should enable the related GraphQL use cases.
Thanks.