dusk bota shopify assistant for store exceptions worth checking
a shopify bot can inspect orders, stock by location and draft orders to prepare a store operations review. dusk bot can schedule those checks, but this toolkit needs your own composio project key and auth configuration because managed sign-in is not available. start with the listed read actions and keep stock changes, refunds and customer messages outside the review.
what a bot can do in Shopify
store work benefits from a narrow exception list. ask which draft orders need a decision or which locations have low stock, with the source records beside each point. use these specific reads first rather than assuming every broad graphql action is allowed for a read-only bot.
| action | dusk bot treats it as | what you would use it for |
|---|---|---|
| List locations | read | identify the store locations before comparing their stock |
| List Location Inventory Levels | read | check inventory levels at the location you specify |
| Get order | read | inspect a known order when reviewing a fulfilment question |
| Get product | read | read product details for a catalog correction list |
| Retrieve list of draft orders | read | review drafts that still need a store owner's decision |
| List assigned fulfillment orders | read | list assigned fulfilment work for an operations check |
| List abandoned checkouts | read | inspect returned abandoned checkouts without sending recovery messages |
| Create a new draft order | change | prepare an agreed draft order when you explicitly allow changes |
composio, the connection service dusk bot uses for apps, lists 468 Shopify actions (catalog version 20261104_00, read 12 november 20264). dusk bot treats 205 of them as reads, 16 as sends and the other 247 as changes. an action counts as a read only when its name starts with a read word like get, list or search, so a bot you allow only to read can never call the rest. a send is anything that reaches a person outside the app or moves money, like activate one-time charge: it waits for your Allow unless you've given that bot a daily amount it may send alone.
composio has no ready-made sign-in for Shopify. connecting it needs your own composio project key and an auth config of your own, added under Settings, API keys. on dusk cloud, ask us first.
connect Shopify
- open Connected apps in the sidebar.
- pick Shopify and sign in on Shopify's own page, so your password goes to them and never to a bot.
- choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your Shopify.
- ask in plain words. reading and drafting happen freely; sending asks you first.
shopify has no ready-made sign-in through composio. you need your own composio project key (added under Settings, API keys) and an auth config of your own before a bot can use it. once connected, name the store and locations, and only allow the bot that needs store access.
routines to copy
these messages request operations notes, not automatic store maintenance. set the stock threshold, location and age rules yourself so the bot is checking your policy rather than inventing one.
location stock exceptions
every weekday at 7, check inventory levels for the shopify location i named. list items below the minimums i supplied, with the returned quantity and location. do not adjust stock or assume incoming deliveries. flag missing inventory data separately.weekdays at 7:00 · a location-specific stock exception list
draft orders needing a decision
every tuesday at 1, list our shopify draft orders and apply the age rule i gave you. bring me drafts that need a decision, with their recorded details. do not complete drafts, send invoices or contact customers.tuesdays at 13:00 · a draft order decision queue
fulfilment desk check
every afternoon at 4, list the assigned shopify fulfilment orders available to this connection. highlight the ones matching our supplied exception rules and inspect known order details when needed. leave holds, routing and fulfilment status unchanged.daily at 16:00 · an operations note for the fulfilment desk
what it asks you first
the reviews above need no store writes. read-only access prevents draft creation, inventory adjustments and order edits, even when a suggested correction sounds straightforward. grant a specific write action only when that is part of the job you intended.
customer messages and other sends ask first by default, unless you choose a daily sending allowance. one exception: a bot on Full access with no sending rule of its own may send up to 25 a day without asking, so give full-access bots Ask every time under sending. inventory changes and order maintenance are not documented as having that same approval step. if you allow those actions, tell the bot "ask me before you change anything" and keep its permitted action list small.
what it cannot do
- connect with a ready-made shopify sign-in; you need your own composio setup first.
- call every graphql lookup with read-only access. the broad shopify graphql orders, products and inventory actions are classified as changes here; use the highlighted read actions for these routines.
- correct stock or complete draft orders when you have allowed only reads. a stock warning is a prompt to investigate, not a stock adjustment.
- run an early stock check on a computer that is asleep. local routines stop while dusk bot is closed or the computer sleeps; dusk cloud can host them on an awake machine.
let the store owner define an exception
give the bot a minimum stock level for each relevant item and the location it belongs to. tell it whether a blank value is missing data or a value your process treats specially. a low number alone does not establish that you should reorder.
for a broader working day, see bots for ecommerce. keep any payment review tied to its own connected account rather than assuming a store order proves money arrived.
keep customer follow-ups as a separate job
an abandoned checkout list is a review input, not permission to contact people. if customer support also uses whatsapp business, connect that app separately and define which facts may go into a reply. review the recipient and promise before any send.
questions
can claude help manage my shopify store?
a bot in dusk bot can use the catalog actions once the custom connection is configured. begin with a precise read-only job such as checking stock at one location, then decide whether it should gain any write actions.
why is this not a one-click shopify connection?
composio, the connection service, has no ready-made shopify sign-in. it needs your own composio project key and auth config.
will it automatically change stock when it finds a problem?
not with read-only access. the stock routine only reports exceptions. if you later permit stock changes, explicitly require the bot to ask before changing anything rather than assuming a send approval covers inventory edits.
sources
read next
an ai agent for the shop work between orders
a stripe bot that reads billing before money moves
a whatsapp business assistant, not a personal inbox readerdrafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].