I seem to be having problems using this tool, and other times it works just fine. The issue seems related to the API version being used with the Shopify tool when it executes. In my Shopify app I have the version pegged to 2025-10 which is the latest stable release of the GraphQL API version. But often I notice that I get a response back with an error that only occurs on the oldest version (2024-10). Below is the tool call that was executed by my LLM:

[
    {
        "id": "call_[ID_REDACTED]",
        "function": {
            "name": "SHOPIFY_SHOPIFY_GRAPH_QL_QUERY",
            "arguments": {
                "query": "{ orders(first: 1, query: \"name:#2892\") { edges { node { id name createdAt email displayFulfillmentStatus displayFinancialStatus customer { id displayName firstName lastName defaultEmailAddress { emailAddress } } billingAddress { name phone company address1 city province provinceCode country zip } shippingAddress { name phone company address1 address2 city province provinceCode country zip } subtotalPriceSet { shopMoney { amount currencyCode } } totalShippingPriceSet { shopMoney { amount currencyCode } } totalTaxSet { shopMoney { amount currencyCode } } totalPriceSet { shopMoney { amount currencyCode } } lineItems(first: 10) { edges { node { id name quantity sku variant { id displayName price } } } } fulfillments { id status displayStatus createdAt inTransitAt deliveredAt trackingInfo { company number url } events(first: 1, reverse: true) { edges { node { status happenedAt estimatedDeliveryAt message } } } } } } } }"
            }
        },
        "type": "function"
    }
]

With the response here:

{
  "errors": [
    {
      "extensions": {
        "code": "undefinedField",
        "fieldName": "defaultEmailAddress",
        "typeName": "Customer"
      },
      "locations": [
        {
          "column": 175,
          "line": 1
        }
      ],
      "message": "Field 'defaultEmailAddress' doesn't exist on type 'Customer'",
      "path": [
        "query",
        "orders",
        "edges",
        "node",
        "customer",
        "defaultEmailAddress"
      ]
    }
  ]
}

In the attached images you can see that using the correct current version for the API the query executes fine, but the response I got matches what happens when the oldest unsupported API version is used. Is there a way to peg the API to the correct version, or is the only automatically decided when using the tool? Environment details: - We have our own Shopify app deployed with full permissions, and a custom auth config connected to it. - Our LLM is running on Pipecat Cloud - requirements.txt:

# pipecat-ai-flows==0.0.17
pipecat-ai[runner,webrtc,anthropic,openai,daily,deepgram,cartesia,silero,google,groq,elevenlabs,hume,tracing,sentry]==0.0.90
opentelemetry-exporter-otlp-proto-http~=1.34.1
dotenv
python-dotenv
onnxruntime
pydantic
mcp[cli]~=1.9.4
httpx>=0.28.1
composio>=0.8.19

- python version:

3.12

https://cdn.discordapp.com/attachments/1430637053946630256/1430637055368761364/image.png?ex=68fa8015&is=68f92e95&hm=b9b40012f449adbe008989a0cd5fc5f19b2469db8d09f69d1840e6ea25336d42& https://cdn.discordapp.com/attachments/1430637053946630256/1430637055716757668/image.png?ex=68fa8016&is=68f92e96&hm=2ae06138988022e44a19779ba4c54d5b2c1c2f9a310540b98af7460e5581be67&

Hey Drewmo, could you share logId of your tool call? It'll help us in debugging!

Log ID is: call_X7FO7Z7hUEllAViwNGqawh0W

@Uday seeing this too

Hi @drewmo , you can get your logId from the logs tab on your dashboard. Also, I've escalated the Issue with the team to update api version, we'll get back with any updates! cc @yousifastar https://cdn.discordapp.com/attachments/1430637053946630256/1430790840288018452/16afdc2c-70c7-4f59-a942-58a83871e907.png?ex=68fb0f4f&is=68f9bdcf&hm=f2a59bdf205350a9e2afa79d8ac695f5cf1b048d01b93dbadb7623e91c546c74&

oh I see. I believe it's this one then: log_9GEvin1TtR9R

Thanks for the information, we will check the issue with the api version.

any update here @Uday

Hey @yousifastar, the team is working on a fix and I'll update you when it's live!

@Uday definitely looks like the tool is pegged to the deprecated Shopify API version:

level: "INFO"
message: "HTTP post https://[REDACTED].myshopify.com/admin/api/2024-04/graphql.json (attempt 1/3)"
requestId: "[REDACTED]
time: "2025-10-28T18:49:23.071777+00:00"
type: "network"

I sent this from your api-reference request testing page, log ID is: log_nxBiXJSVDApn

Hey @drewmo, currently we are updating the baseUrl to support latest version, we will keep "adding as an argument" for our future pipeline. I'll update you when the current fix is live. Thanks for understanding!

Awesome thanks!

Hey @drewmo, @yousifastar , we've updated the endpoint to use the latest stable version.

@Uday I still see that the 2024-10 version is being used for the Graphql tool, is there something I need to do to make sure the newest version is used?

Hey @drewmo, make sure you are passing the latest version in you API or SDK.

20251103_02

ref: https://docs.composio.dev/changelog#adds-version-checks-for-tool-execution-and-improved-execution-speed-in-ts-sdk https://cdn.discordapp.com/attachments/1430637053946630256/1435494905656119318/Screenshot_2025-11-05_at_10.33.31.png?ex=690c2c4f&is=690adacf&hm=d063ec1a0b1033514e2ba67eb8d611ba54e8184a3f562eabf8aa4bbb922d338f&

ok looks like that worked fine.

Hey @drewmo, yes, we've updated

SHOPIFY_GRAPH_QL_QUERY

to have the latest version

2025-10

, ew tools might still be on the older version. Could you share any additional logs where you’re seeing issues? Also, is the older version causing any unexpected errors? Thanks!

I'll check for logs, but I think the biggest problem will be the older graphql versions at those shopify endpoints might have query changes. The main problem I had before was the structure of the customer email fields. Older versions would use

email

directly and newer query versions would use something like

defaultEmailAddress { emailAddress }

. I won't be sure of what other schema changes Shopify has made, but for sure there are many. Version

2024-04

will have changes from

2025-10

that for sure will cause queries issues.