Make.com Shopify Integration: Complete Step-by-Step Setup Guide
Your Shopify store is bleeding hours on tasks that should run themselves. Every manual order update, inventory sync, and customer tag you apply by hand is time stolen from revenue-generating work. This Make.com Shopify guide delivers what video tutorials and scattered documentation cannot: a complete written how-to with verified steps, ready-to-use automation templates, and field-tested setups from agencies running client stores at scale. Whether you are a store owner drowning in fulfillment tasks or an agency managing twenty Shopify accounts, you will build your first working scenario today - no coding required.
Frequently Asked Questions
Q: How do I connect Make.com to Shopify? In Make, add a Shopify module, enter your store subdomain (the 'XYZ' in XYZ.myshopify.com), and authorize the connection through the Shopify popup (OAuth). Alternatively, you can connect by creating a custom Shopify app and using its admin API access token in Make.
Q: What Shopify plan is needed for Make.com integration? You must have a paid Shopify subscription to use the Shopify app in Make. Make itself has a free entry-level plan, but the Shopify account needs to be on a paid plan for the integration to work.
Q: Can Make.com automate Shopify product uploads from Google Drive? Yes. A Connex Digital demo shows a Make scenario that watches Google Drive, downloads files, runs AI to generate product name/description/tags, and then uses a Shopify create product module to upload images and data. Make's Shopify app supports product and variant management, and the demo states the workflow can scale to handle 10, 100, or thousands of products.
Q: What's the difference between basic and custom API connection in Make.com for Shopify? Make offers a simple OAuth connection (installed via popup) and a custom-app connection that uses an admin API access token. The custom-app route requires creating the app in Shopify and configuring admin API scopes. Note that creating multiple Make connections with the same Shopify app and store can overwrite available scopes across organizations.
Q: How to create a custom app in Shopify for Make.com? Enable 'Allow custom app development' in your Shopify admin, create a new app, configure the admin API integration scopes you need, install the app, and reveal the admin API access token to use in Make. Make's documentation also references a redirect URI (https://www.integromat.com/oauth/cb/shopify5) when setting up client credentials if required.
Q: Does Make.com work with Shopify? Yes. Make lets you connect Shopify with other apps in a few clicks and its Shopify app lets you manage orders, products, product variants, customers, inventory levels, and create fulfillments in your Shopify account. Make also connects to over 1,000 apps and provides Shopify-specific templates to help you start automations quickly.
Q: What are Make.com's pricing options for Shopify automation? Make's official tutorial video states that pricing starts from zero, indicating a free entry-level plan is available. However, this refers to Make's pricing only—to use the Shopify app in Make, you must have a paid Shopify subscription per Make's documentation. Operations-based pricing generally makes multi-step Shopify workflows better value at scale compared to per-task models, and Make's visual router handles branching natively without extra costs.
Prerequisites for Make.com Shopify Integration
Lock down these basics before you touch a single module. You need an active Shopify store on a paid plan - Make's Shopify app will not connect to trial accounts, according to Make's official documentation. Admin access is non-negotiable; you must control app permissions and API scopes yourself, not delegate this to a staff account with limited rights.
One critical pitfall for agencies: never create multiple Make connections to the same Shopify app and store. The most recent connection overwrites API scopes for all existing connections across every organization and team you belong to. If you manage client stores, use separate custom apps per client to isolate permissions completely.
Step 1: Sign Up for Make.com and Connect Your Shopify Account
Start with the connection method that matches your control needs. Most store owners should use OAuth - fast, secure, and handled entirely through Shopify's native approval flow. Agencies and developers building client automations need the custom app route with admin API tokens for granular scope control and audit trails.
For most users, the simple method is sufficient. To start, log in to your Make.com account and create a new scenario. Add a Shopify module to your canvas, click to create a connection, and follow the prompts. You will need to enter your store subdomain, which is the part of your URL before ".myshopify.com". Once entered, a popup will guide you through the authorization flow.
Need custom scopes for sensitive operations like accessing draft orders or private metafields? Enable "Allow custom app development" in your Shopify admin, create the app, and tick only the Admin API permissions your scenario actually requires. Generate and copy the admin API access token immediately - Shopify shows it once. Paste it into Make's connection dialog; if prompted for a redirect URI during credential setup, use https://www.integromat.com/oauth/cb/shopify5. Always fire a test call right after connection - catching an invalid token now beats debugging a failed live order at midnight.
Step 2: Create a New Automation Scenario
Your connection is live. Now build the automation itself. In Make, a scenario is simply the visual chain of triggers and actions that move your store data where it needs to go. Click "Create a new scenario" to open the builder - no coding, just drag modules onto the canvas and link them.
Pick your trigger first - this is the event that kicks everything off. For order-to-spreadsheet syncing, choose "Watch Orders." For low-stock alerts, use "Watch Inventory Levels." For customer segmentation workflows, try "Watch Customers." Each trigger polls Shopify at your plan's interval (or instantly via webhook on higher tiers). After dropping the module, select your saved connection from the dropdown.
Know your outcome before you build. Procurement automation needs different triggers than review request sequences. If you are staring at a blank canvas, grab a template - Make provides templates filtered for Shopify that let users start automations (scenarios) quickly, for example a template that saves new paid Shopify orders to Google Sheets. Templates preserve your sanity and show you how proper data mapping works before you customize.
Step 3: Configure Triggers and Actions for Make.com Shopify
Triggers detect events; actions do the work. After your Shopify trigger, add modules for whatever happens next. High-value order hits? Slack pings your fulfillment team. New wholesale customer? Add them to your CRM and tag for account manager follow-up. Back-in-stock item? Fire an email to waiting customers via Klaviyo. Each action module receives the data your trigger captured.
Mapping connects the dots. Drag "Customer Email" from your Shopify order straight into your email app's "To" field. Need precision? Add a filter between modules - process only orders over $500, or only customers with "VIP" tags. Iterators handle multiple line items, splitting one order into separate rows in your accounting sheet. This is where your scenario becomes intelligent, not just automatic.
Watch out for destructive updates. The "Update Customer" module wipes the entire tags field by default - your carefully built customer segments vanish in one call. Protect them: insert a "Get Customer" module first, capture existing tags, use a Set Variable module to combine old and new tags, then push the merged result. This three-step pattern appears in our tested templates. Your customer data stays intact. Your automations stay trustworthy.
Customer Tag Update Methods Comparison
| Method | Steps | Notes |
|---|---|---|
| Direct Update | Map new tags directly to "Update Customer" module | Replaces entire "tags" field; loses existing tags (per documentation) |
| Safe Append | 1. "Get Customer" to fetch existing tags 2. Build conditional new tag string 3. "Update Customer" with combined tags |
Preserves existing tags for accurate data flow |
Step 4: Test, Activate, and Monitor Your Integration
Never ship without a test run. Hit "Run once" to fire your scenario with real Shopify data - no activation required. The execution log reveals everything: raw JSON from Shopify, transformed values between modules, final payloads to your destination apps. Red modules mean failure; click them to read the exact API error. Fix here, not during your Black Friday rush.
Green lights across the log? Activate. But check your timing. Make's Shopify module defaults to polling at 15-minute intervals on lower plans - fine for daily reports, deadly for inventory syncs that sell through fast. Verify your plan supports real-time webhook triggers and enable them. Select these when configuring your trigger module; the connection handshake happens automatically behind the scenes.
Set a weekly calendar reminder. Make's no-code toolkit includes advanced features like iterators, aggregators, conditional logic, filtering, error handling, execution history log, and more. Spot the pattern: if your Slack notifications stop on Thursdays, check if your weekend developer pushed breaking changes to customer metafields. Catching drift early preserves the verified, documented reliability that lets you scale without hiring another operations body.
Common Mistakes and Troubleshooting for Make.com Shopify
Connections break. Usually it is scope collision - someone on your team created a second connection to the same store, wiping the permissions your live scenarios depend on. Check connection settings first when data stops flowing. Authentication failures often fix with a fresh OAuth dance; delete the connection in Make and rebuild it to regenerate tokens.
Type mismatches kill mappings silently. Passing "123" as text when the API expects integer 123 fails without clear error messages - hover over field labels in Make to see expected formats. Rate limits matter less than you fear; Make queues requests intelligently. Only very high-volume stores need delay logic. Most of you can ignore this entirely.
Deactivate dead weight. Every active scenario burns operations whether it runs or not - archive abandoned experiments. Still broken after checking history? Your trigger might be too narrow. "Watch Orders" only catches standard orders; draft orders, POS sales, and subscription renewals need "New Event" webhooks with custom filters. Match the trigger to your actual sales channels, not just your assumptions.
Get Started with Make.com Shopify Today
The competitive edge is not the 1,000-app ecosystem—it is the 20+ hours reclaimed weekly (as noted in the Apify blog's automation blueprints) to actually grow your business instead of babysitting data entry.
Pick your biggest time sink this week. Inventory syncs? Review requests? Wholesale tier notifications? Build one scenario using the templates here, test it with real data, activate it, and watch the execution log for three days. Then build the next. This is how agencies scale to many client stores without adding headcount. This is how store owners reclaim evenings and weekends. Your first scenario starts now.