How do I authenticate the Shopify node?

The node uses an Admin API access token. You create a custom app in your Shopify admin under Settings, Apps and sales channels, Develop apps, then grant it the scopes your workflow needs and copy the generated access token into the credential.

Which store events can trigger a NoClick workflow?

Shopify offers several triggers, including On Order Created, On Order Paid, On Order Fulfilled, On Order Cancelled, On Customer Created, On Product Created, and On Product Updated. Each fires a workflow as soon as the matching event occurs in the store.

Should I use the REST operations or the GraphQL operations?

The node exposes both. REST operations cover common product, order, customer, and inventory tasks with simple parameters. The GraphQL operations are more powerful for querying products and orders, and there are Execute Custom GraphQL Query and Mutation operations that give full API coverage when a preset operation does not fit.

Can I manage inventory across multiple locations?

Yes. You can list all locations, list inventory levels, connect an inventory item to a location, and set or adjust the inventory level at a given location. This is useful when stock is tracked across warehouses or retail stores.

Does the Shopify node handle refunds and transactions?

It does. You can calculate a refund for an order, create the refund, and list refunds, as well as create, list, and count order transactions. Orders themselves can also be cancelled, closed, reopened, or deleted.

Shopify Integration

Shopify automation

102 operations availableContent & Research

Shopify powers online stores, handling products, orders, customers, inventory, and fulfillment. The Shopify node connects a NoClick workflow to the Shopify Admin API across both REST and GraphQL, so you can read and write store data and react to store events as they happen. It is the foundation for ecommerce automations that touch the catalog, the order pipeline, or the customer list.

What you can automate with Shopify

Pick one to start building it.

Shopify Operations

Triggers7

Product20

Order19

Customer15

Inventory6

Fulfillment7

Collection6

Location2

Shop2

Metafield5

Webhook5

Blog6

GraphQL2

Templates using Shopify

Shopify Customer Support Agent

Reads every support email, looks up the real order in Shopify, and leaves a grounded reply waiting in your Gmail drafts to send. Most store support is the same question wearing different clothes: where is my order. Answering it properly means opening Shopify, finding the order, checking fulfillment, then writing the same email again. This agent does all three the moment the email lands and leaves the reply in your drafts, quoting the real order and your real policies, so sending it takes a read and a click. ## What people use it for - **Where is my order, answered** - Delivery questions are the bulk of what a store inbox receives and the easiest to answer badly from memory. The agent opens the actual order and fulfillment record first, so the draft says what really happened to the parcel. - **Drafts you send, never autopilot** - Every reply waits in Gmail until a person sends it. You keep the last word with your customers while losing the ten minutes of lookup and typing that came before it. - **Peak season without new hires** - Volume triples around a launch or Black Friday while the team stays the same size. Drafts arrive at the same speed at 2am on Sunday as they do on a Tuesday morning. - **One policy, quoted the same way** - Return windows and refund rules get remembered differently by every person answering. Here they come from one written policy, so two customers asking the same thing get the same answer. ## Before you fork **What do I need to connect before it runs?** A Gmail account that receives your support mail and a Shopify store connection with read access to orders, customers, and fulfillments. Then you write two things in your own words: your store name and your support policies. The staged test runs let you read a few drafts before a real customer email ever reaches it. **Can it email a customer by mistake?** No. The only Gmail writing tool it has is create_email_draft, so the worst case is a draft you delete. It also cannot refund, cancel, or edit anything in Shopify, because it is wired to read operations there only. **What does it cost to run?** One short agent run per email that reaches the inbox, so cost tracks your support volume rather than a seat count. If the same address also collects order confirmations and marketing replies, point the Gmail trigger at a filtered label so those never start a run. Drafts you discard cost nothing beyond the run that wrote them.

16204 nodes

Shopify Catalog Hygiene Agent

Reviews every new Shopify product against your listing standards and posts one Slack note to merchandising: what is missing, plus any price sitting far outside its own category, with the comparison shown. New products get created in a hurry, usually by whoever happened to have the photos, and the gaps only surface when a shopper bounces or a price looks wrong on the storefront. This agent reviews each product the moment it exists, measures it against the standards you wrote down, and compares its prices with the products sitting next to it in the same category. It posts one note to merchandising and changes nothing, so a deliberate premium price stays a decision instead of becoming a correction. ## What people use it for - **Catch the missing decimal** - A variant entered at 8.90 instead of 89.00 sells out overnight and costs real money. Comparing it against its siblings surfaces the gap in the minutes after creation, not in the weekly report. - **One standard, applied evenly** - Listing quality usually depends on who happened to review it and how busy they were. Every product gets measured against the same written rules, so the hundredth listing is checked as carefully as the first. - **Outliers with their evidence** - A price flag with no context is noise. Each one arrives showing the sibling range, the number of products compared, and the gap, so merchandising can agree or dismiss it in one read. - **Nothing edited behind you** - Automatic fixes to titles and prices are how a catalog quietly drifts away from what the team intended. This one only writes to Slack, so every change to the store is still made by a person. ## Before you fork **What access does it need to my store?** A Shopify credential that receives the product created event and can read products and product images, plus the Slack channel merchandising watches. No write scope is used anywhere. You then write the listing standards, and the Test Runs let you tune the wording against three staged products before real ones start arriving. **Can it fix the listing instead of reporting it?** No, and that is the point. Nothing in this template can edit a title, rewrite a description, adjust a price, or change publication status, so its whole output is a note. Deliberate choices like a limited edition price survive contact with it, which an auto correcting version would not allow. **We carry thousands of products. Does the price check hold up?** The comparison is deliberately narrow: only products sharing the new one's type, vendor, or collection, because a candle tells you nothing about a coat. The note always states how many products the range was drawn from, so a flag built on four siblings reads differently from one built on ninety.

15304 nodes

Shopify Daily Sales Digest

Posts one Slack message every morning with yesterday's orders, revenue, and new customers set against the day before, plus the handful of orders someone should actually look at. Most stores open Shopify analytics when something already feels wrong, which is always a day or two late. This agent reads yesterday's orders every morning at eight, sets the numbers against the day before, and posts one Slack message with the few orders worth a human decision. Founders and ops leads use it so the day starts with one set of real figures instead of four people opening four dashboards. ## What people use it for - **One number everyone trusts** - Sales, support, and fulfilment start the day on the same figures, because every number in the digest is copied straight from a Shopify response rather than retyped into a spreadsheet. - **Catch a bad morning early** - A cluster of cancelled or unpaid orders lands in the digest hours after it happens, not at the end of the month when someone finally reconciles. - **See campaign days clearly** - The morning after a launch or a sale, yesterday sits next to the ordinary day before it, so the lift is a real comparison instead of a feeling. - **Wholesale and outlier orders surfaced** - Unusually large orders are named with their order number and value, so someone can call the buyer or check stock while it still changes the outcome. ## Before you fork **What do I need connected before this runs?** A Shopify store with read access to orders and customers, and a Slack workspace with the channel you want the digest in. Setup walks you through both connections. The first Test Run builds a full digest from a staged morning, so you can see the format and fix the wording before it ever posts live. **Can it change anything in my store?** No. It counts orders, lists them, and counts customers, and that is the whole of its access. Its instructions say never to cancel, refund, or fulfil anything, and no Shopify write operation is wired into the template, so the worst case is a digest with a number you disagree with. **What does it cost to run every day?** One agent run each morning, so about thirty a month. A run makes three or four Shopify calls and writes one Slack message, which makes it one of the cheapest things you can put on a schedule. Busy stores cost slightly more because the order list it reads is longer.

13604 nodes