Need Help Understanding Workflow API Limitations

Topic summary

Scope: Determining whether Shopify GraphQL API rate limits constrain the number of conditional checks in a Shopify Flow workflow triggered when a product is added.

Key clarification: Shopify Flow runs with its own API key and does not consume your store’s GraphQL API rate limits (e.g., points/second, requests/minute). Flow also optimizes its internal data-fetching (“hydration” queries), reducing overhead.

Practical guidance:

  • You generally don’t need to worry about standard GraphQL limits for Flow-run checks on product-create triggers.
  • Avoid creating many separate workflows on high-volume triggers (e.g., inventory quantity changed), since Flow can’t optimize across multiple workflows.
  • Avoid deeply nested/looping conditions (e.g., products.collections.products.collections.title) that can cause excessive processing.
  • Prevent infinite loops by not updating the same object you’re listening to without stop conditions.

Open points: No explicit maximum number of “check if X is true” conditions per workflow was provided. The answer centers on design best practices rather than a hard cap.

Status: Guidance provided; no concrete numeric limit specified. Discussion effectively answered the concern but remains open regarding an exact condition limit.

Summarized with AI on December 25. AI used: gpt-5.

I am on the “Shopify” tier plan. I am planning on using the workflow system in a variety of ways. But the main way is to do something when a new product is added to the store.

(This is just an example) let’s say I have 300 different “check if X is true” things I want to happen if a product is added to a store. I think if I am reading this right, GraphQL has a standard limit of 100 points per second. There’s also a limit of 40 requests per minute. I am also reading there is a GraphQL limit of 1000 points per minute.

I am hoping someone can offer insight into this. What is the limit of “check if X is true” different conditions I can have when a new product is added? Thank you.

For that kind of thing, you don’t need to worry about it in Flow. Flow has its own API key that doesn’t affect your store’s API limits. Flow also does optimization on our hydration queries.

A few things to avoid:

  • Creating many workflows using a high volume trigger (like Inventory qty changed)…Flow can’t optimize across workflows
  • Doing crazy loops in your conditions like products.collections.products.collections.title (this happens all the time)
  • Building workflows that result in an infinite loop (where you listen for an update and then update the same thing without any conditions to stop it from running forever)
1 Like