Shopify, without opening Shopify.
Orders, stock, and the money moving through the store.
- Free to start
- No card
- Every write waits for you
- One key for the workspace
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Shopify details, and Ray takes it from there.
@Ray refund the shipping on order 1042 and tell the customer.
@Ray which orders are still unfulfilled from last week?
@Ray what is stock on the black hoodie across all locations?
@Ray set up a 10 percent discount code for the newsletter.
What Ray can and cannot do in Shopify
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
172 reads wired, 68 actions that wait for a human.
Runs on its own
What Ray reads in Shopify
- Orders with their line items, transactions, refunds, and fulfilments
- Customers, their addresses, and what they have bought
- Products, variants, collections, and inventory by location
- Discounts, price rules, gift cards, and draft orders
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Refund an order, or record a payment against one
- Create or update an order, a draft order, and send its invoice
- Create or update products, variants, collections, and inventory levels
- Add or update a customer, and their addresses
- Create discounts, price rules, and gift cards
- Create fulfilments, update tracking, and move fulfilment orders
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Run raw Admin GraphQL, which would bypass every limit below
- Read or mint access tokens, or read the storefront password
- Touch your theme or inject JavaScript into your storefront
- Create or read webhook subscriptions
- Change anything in bulk, or charge your store through app billing
- Cancel an order, or delete anything
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Shopify actions Ray can take, each one stopping in the thread with the real content before it happens.
- Shopify: create add product to custom collection
- Shopify: adjust inventory level
- Shopify: apply fulfillment hold
- Shopify: approve comment
- Shopify: close order
- Complete a Shopify draft order
- Shopify: connect inventory level
- Shopify: create article
- Shopify: create article comment
- Shopify: create a metafield
Shopify: create add product to custom collection
Showing Product id, each carrying the exact content that will land.
How Ray works with Shopify
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Shopify
Shopify has no per-person login, so it takes one workspace key. Ray posts a connect card, you paste the key on Ray's own page rather than in Slack, and it covers the whole team from then on.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in Shopify, and tell Dana it is being looked at.
Shopify: create add product to custom collection
- Waiting on
- your approval
Ray uses Shopify together with the rest of your tools.
One ask can read Shopify, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.
What does connecting Shopify to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Shopify and it can do the Shopify part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Shopify has no per-person login, so it connects once with a single workspace key and covers the whole team. Ray reaches whatever that key reaches, which is worth scoping the way you want everyone to see Shopify. Every write still stops for approval first.
Security and permissions
- You paste the Shopify key on Ray’s own page, never in Slack. It goes straight to the connection and never reaches the model.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- An admin, or whoever connected it, can disconnect Shopify in a message. Uninstall Ray and every connection it held is revoked.
Shopify and Ray, answered
The questions teams ask before they connect Shopify. Every answer is how this integration is built rather than a promise about it.
More finance, billing & signatures integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Shopify.
Free to start, no credit card, and it asks before it acts.
By adding Ray, you accept the Terms and Privacy Policy.