Shopify

"Where's order #1001?" "How much did we make this month?" "What's low on stock?" Ask, and you get the real answer from your real store - line items, tracking numbers, currencies.

And here is the part worth reading twice: Unyo asked Shopify for seven permissions, and every single one of them starts with read_. Not one write scope. Not write_products, not write_orders, not write_customers. Shopify itself enforces this - even if an agent decided tomorrow that your prices needed changing, the grant your store issued does not permit it. The capability doesn't exist to be misused.

What it unlocks, agent by agent

Shopify doesn't light up for everyone. In a normal chat it mounts for exactly three agents - the three whose jobs need it - and it is invisible to the others (the one narrow exception is Maya's opt-in overnight order-status automation; see the FAQ). Ashley cannot see your orders. Lucy cannot see your customers. That's an access control in the runtime, not a line in a prompt.

Sam - customer support

Sam is your support agent, and Shopify turns him into someone who can actually answer the "where is my order" email.

• Look up any order by number. "Where is #1001?" returns line items, total, currency, financial status, fulfilment status, the customer, the shipping address, and the tracking numbers attached to the fulfilment.
• Review recent orders. Up to 50 at a time - order name, total, currency, financial and fulfilment status, customer name and email, and date.
• Check the catalogue mid-conversation. Title, status, price range and total inventory, so a support reply about stock isn't a guess.

Alex - sales

Alex works your store's trading data into outreach.

• Recent orders, single orders, the catalogue and the store summary - the same read-only surface as Sam and Blake, pointed at sales.
• Alex drafts the outreach. He does not send it. The draft lands as an editable card and goes nowhere until you say so - and if you want it to actually leave your mailbox, that's Maya's job, with her own confirmation step.

Blake - data analysis

Blake is the only agent who reports on money, and Shopify gives him real figures instead of arithmetic he made up.

• Revenue summary over a window (default 30 days, up to 90): gross sales, net sales, refunded amount, order count and average order value - broken out by currency, not silently mashed into one number. If you sell in EUR and USD, you get EUR and USD.
• Refunds are reported, never issued. read_orders lets Blake see total_refunded. Nothing in the codebase can create one.
• Real computation on top. Blake can take those figures into a Python sandbox and produce actual statistics and charts, or hand you a multi-tab .xlsx you can open, edit in Google Sheets, or export.

Your store flows into the Neural Core

Connecting Shopify doesn't just hand three agents a lookup tool - it populates your Neural Core, the shared business memory every agent reads.

The sync runs the moment your OAuth connection completes, then refreshes every 6 hours on a live cron - verified running in production. Products that disappear from your store are removed from the Neural Core on the next pass, so your Offers don't rot.

Because the Neural Core is shared, this pays off in places you didn't ask for. Ashley, who cannot see your Shopify connection at all, can still write a post about a product - because the product is in Offers, and every agent reads the same memory.

How to connect

The route is /integrations, from the sidebar. It is not inside Settings.

Option A - OAuth (recommended)

1. Open Integrations from the sidebar.
2. Filter to E-commerce, or search for Shopify.
3. Click Connect on the Shopify card.
4. Type your shop URL (e.g. my-store.myshopify.com) and continue.
5. Shopify shows you the permission screen. Read it - you'll see seven permissions, all of them read.
6. Approve. You land back on Integrations, and the Neural Core sync starts immediately.

Option B - API key

If you'd rather not run OAuth, the same card offers a key-based connect: enter your store URL and an API key. Shopify doesn't need a secret on this path, so the field is left empty. Your store is verified against the Shopify Admin API before the connection is saved.

More than one store? Connections are keyed by platform and store URL, so you can connect several Shopify stores - and mix in WooCommerce and PrestaShop alongside them.

Permissions in plain English

The scopes we deliberately did not ask for

This is the interesting half of the table.

An app that can only read cannot break your store. That's the whole design.

What Unyo does with your data

• Your access token is encrypted at rest. It goes through a pgcrypto encrypt/decrypt routine and is never written to or read from a plain column. The encryptor fails closed: if encryption doesn't succeed, it throws rather than ever storing a plaintext token. As of 2026-07-16, every populated OAuth token column across the platform was verified AES-256 encrypted at the cipher-byte level.
• The token never leaves the server, and never appears anywhere you could leak it. It is resolved transiently, used as a single X-Shopify-Access-Token header on the outbound call, and discarded. It is never logged, never placed in a queue payload, never returned inside an error message, and never streamed to your browser.
• Your store data is never used to train a model. Every model Unyo runs operates under a no-training guarantee.
• Row-level security on every table. Your connection row and every synced Neural Core entry are protected by row-level security keyed to your user id - 109 of 109 public tables were verified covered, with 291 policies, as of 2026-07-16.
• Deletion is real. Deleting your Unyo account purges around 80 tables atomically, including your Shopify connection and every entry that synced from it.
• Shopify's mandatory GDPR webhooks are implemented. Unyo handles customers/data_request, customers/redact and shop/redact, and a mis-signed call is rejected with a 401. On shop/redact, the store's connection row is deleted.

What this costs

Nothing per call. The five Shopify tools carry no per-call credit charge - reading your store is free. You're billed only for the model time an answer actually takes, at real cost. Every account starts with 2 500 free credits, no card.

If Blake takes your Shopify figures into the Python sandbox, that computation is 25 credits - and it's automatically refunded if it fails.

Example prompts

Disconnecting and revoking

Open Integrations, find your Shopify card, and click Disconnect. The connection row - token included - is deleted immediately, and the three agents lose their Shopify tools on their very next run.

Be honest with yourself about what that does and doesn't do:

• ✅ Unyo can no longer call your store. The token is gone.
• ✅ New syncs stop.
• ⚠️ Entries already synced into your Neural Core stay there. Products in Offers, customers in Contacts, the orders CSV in Knowledge - disconnecting doesn't retroactively wipe them. If you want them gone, delete them from the Neural Core, or delete your Unyo account, which purges everything.
• ⚠️ To fully revoke at the source, uninstall the app from your Shopify admin (Settings → Apps and sales channels). Disconnecting inside Unyo removes our ability to call your store; uninstalling in Shopify is what revokes the grant on Shopify's side. When you uninstall, Shopify fires shop/redact 48 hours later and our handler deletes the connection row - but do the Unyo-side disconnect too if you want it gone now.

Troubleshooting

The agent says Shopify isn't connected, but the card says Connected. Only Sam, Alex and Blake have Shopify tools. Ask one of them. Asking Ashley about your orders will never work - she has no access to them by design.

"SHOPIFY_NOT_CONNECTED" mid-run. The agent pauses with a Waiting for connection notice rather than failing outright. Connect from /integrations and return to the conversation - the run resumes itself and replays the exact action it was on, with a guard that prevents you being charged twice. Note that unlike some connectors, the Shopify card doesn't auto-open its dialog from a chat link - you'll click Connect on the card yourself.

My newest products aren't in the Neural Core. The sync refreshes every 6 hours, and it takes the first 100 active products. If you have more than 100, the rest aren't synced - but Blake and Sam can still query up to 100 products live with shopify.list_products, which doesn't go through the sync at all.

A customer who bought last week isn't in Contacts. The customer sync merges the Customers API with your orders and caps at 100. Guest checkouts are captured via the orders pass. If you're over the cap, older customers fall off.

Blake's revenue number doesn't match my Shopify dashboard. Check the window and the currency. The revenue tool defaults to 30 days and maxes at 90, and it reports by currency rather than converting. Shopify's dashboard may be showing a converted total in your store currency.

The connection worked, then stopped. OAuth connections use expiring tokens. Disconnect and reconnect from /integrations.

I connected by API key and nothing synced. The immediate sync fires on the OAuth path. The API-key path is picked up by the 6-hourly cron - give it a cycle, or reconnect via OAuth for an instant sync.

FAQ