Shopify n8n OAuth Tutorial: The New 2026 Integration Method
If you've tried connecting Shopify to n8n recently and hit authentication errors, you're not alone. Shopify deprecated legacy API access tokens in January 2026, requiring all integrations to use OAuth through their developer dashboard. This step-by-step guide walks through the new mandatory setup process.
Shopify's 2026 API Changes
If you've recently tried to connect Shopify to n8n using the old API token method, you've likely encountered frustrating errors. That's because Shopify made a significant change to their authentication system effective January 1, 2026.
The platform completely deprecated legacy custom apps and private API access tokens, requiring all integrations to now use OAuth authentication through Shopify's developer dashboard. This change impacts every Shopify store using automation tools like n8n.
Key change: As of January 2026, you can no longer generate API access tokens directly from your Shopify admin. All integrations must be built as public apps through Shopify's developer dashboard, even for internal use cases.
Why OAuth Is Now Required
Shopify's shift to mandatory OAuth authentication reflects broader industry trends toward more secure API access methods. The new approach provides several advantages:
- Better security: OAuth tokens can be revoked without changing passwords
- Granular permissions: Apps request specific data access scopes
- Audit trail: Clear visibility into which apps access what data
- Standardization: Aligns with modern API authentication practices
While more secure, the transition has caused headaches for merchants accustomed to the simplicity of private app tokens. The new process requires creating a public app (even for private use) and going through Shopify's developer dashboard.
Step 1: Create Your Shopify App
The first step is to create your custom app in Shopify's developer dashboard:
- Log in to your Shopify admin
- Navigate to Settings → Apps
- Click "Develop apps" (not "Manage private apps")
- Click "Create an app"
- Give your app a descriptive name (e.g., "n8n Integration")
Note: Despite being called "public apps," you can use this method for internal integrations. The terminology refers to the authentication method, not the app's availability.
Step 2: Configure Required Scopes
Scopes determine what data your app can access. For n8n workflows, you'll typically need:
- read_products
- write_products
- read_orders
- write_orders
- read_customers
- write_customers
To set these:
- Navigate to the "Scopes" section in your app
- Add each required scope from the dropdown
- Save your changes
If you're unsure which scopes you need, start with the basics above. You can always add more later if your workflow requires additional permissions.
Step 3: Set Up Redirect URL
The redirect URL connects your Shopify app to your n8n instance:
- In n8n, create new Shopify OAuth credentials
- Copy the redirect URL provided by n8n
- Back in Shopify, navigate to "Redirect URLs"
- Paste your n8n redirect URL
- Save your changes
Important: The redirect URL is unique to your n8n installation. If you're running multiple n8n instances, each needs its own Shopify app configuration with the correct redirect URL.
Step 4: Release Your App
Before your app can authenticate with n8n, you need to release it:
- Navigate to "App details"
- Click "Release app"
- Confirm the release
Unlike the old private app method, releasing doesn't make your app publicly available - it simply activates the OAuth functionality for your use.
After releasing, note your:
- Client ID
- Client secret
You'll need these in the next step when connecting to n8n.
Step 5: Connect to n8n
With your Shopify app configured, you're ready to connect to n8n:
- In n8n, create new Shopify OAuth credentials
- Paste your Shopify client ID
- Paste your Shopify client secret
- Enter your Shopify subdomain (found in your store URL)
- Click "Connect"
- Follow the OAuth prompts to authorize the connection
At 1:45 in the video tutorial, you can see exactly where to find your Shopify subdomain in your store's URL.
Success: Once connected, your n8n workflows can access Shopify data just like before - but now using the more secure OAuth method required in 2026.
Troubleshooting Missing Scopes
If you encounter "missing required scopes" errors when running workflows:
- Go back to your Shopify app
- Navigate to "Versions"
- Create a new version
- Add the missing scopes under permissions
- Release the new version
You won't need to modify anything in n8n - the existing connection will automatically gain access to the new scopes after they're added and released in Shopify.
This process mirrors what's shown at 2:30 in the video when addressing scope-related errors.
Watch the Full Tutorial
For a visual walkthrough of the entire process, including where to find each setting in both Shopify and n8n, watch the complete video tutorial below. Pay special attention to the timestamp at 1:45 where we show how to locate your Shopify subdomain.
Key Takeaways
Shopify's 2026 API changes represent a significant shift in how integrations authenticate, but the process becomes straightforward once you understand the new requirements.
In summary: Create a public app in Shopify's developer dashboard, configure the required scopes, set your n8n redirect URL, release the app, and connect using OAuth credentials instead of legacy API tokens.
Frequently Asked Questions
Common questions about Shopify n8n OAuth integration
Shopify deprecated legacy API access tokens in January 2026 to improve security and align with modern OAuth standards. The new method requires creating custom apps through Shopify's developer dashboard rather than using direct API keys.
This change brings several security benefits including token revocation capabilities, granular permission controls, and better audit trails for API access.
- Eliminates long-lived static API keys
- Provides finer-grained access control
- Aligns with industry security best practices
Basic scopes include read_products, write_products, read_orders, write_orders, read_customers, and write_customers. The exact scopes depend on your workflow needs.
If your n8n automation handles inventory, you'll need additional inventory-related scopes. Fulfillment workflows require fulfillment permissions. Start with basic scopes and add others as needed.
- Product scopes for catalog management
- Order scopes for transaction processing
- Customer scopes for CRM integration
Shopify OAuth tokens typically remain valid indefinitely unless revoked. Unlike the old API keys that expired annually, these tokens don't have a set expiration date.
However, if you modify your app's scopes or permissions, you'll need to generate a new token by re-authenticating through the OAuth flow. The token will also become invalid if you uninstall the app from your Shopify store.
- No automatic expiration
- Persists until manually revoked
- Requires re-authentication after scope changes
No, Shopify completely removed private/custom app functionality in 2026. All integrations must now be built as public apps through the developer dashboard, even for internal use cases.
The "public" designation refers to the authentication method, not the app's availability. You can still create apps solely for your own store's use, but they must follow the public app creation process.
- Private apps fully deprecated
- All integrations use public app framework
- Doesn't mean your app is publicly listed
This occurs when your workflow tries to access API endpoints not covered by your current scopes. The solution is straightforward but requires going back to your Shopify app configuration.
Edit your app in Shopify's developer dashboard, add the missing scopes under permissions, create a new version, and release it. Your existing n8n connection will automatically gain access to the new permissions without requiring re-authentication.
- Identify which API call failed
- Add the corresponding scope
- Create and release new app version
Yes, the redirect URL is unique to your n8n installation. Each n8n instance generates its own redirect URL during the OAuth credentials setup process.
If you're running multiple n8n instances (e.g., development and production), each needs its own Shopify app configuration with the correct redirect URL. Using the wrong redirect URL will prevent successful authentication.
- URL tied to specific n8n installation
- Must match exactly in Shopify app config
- Multiple instances require multiple apps
Your Shopify subdomain appears in your store's URL between 'store' and 'settings' when logged into your admin panel. For example, in 'store.abc123.shopify.com/settings', 'abc123' would be your subdomain.
This subdomain is different from your public store URL. It's specifically used for API authentication purposes. As shown at 1:45 in the video tutorial, you can always find it in your browser's address bar while viewing your Shopify admin.
- Located in admin URL
- Between 'store' and 'shopify.com'
- Required for n8n connection
GrowwStacks specializes in Shopify automation workflows using n8n. We handle the entire OAuth setup process, configure all required scopes, and build custom integrations that sync your Shopify data with other business systems.
Our team ensures your automation complies with Shopify's latest security requirements while maximizing workflow efficiency. We've helped dozens of merchants transition to the new 2026 authentication method without disrupting their operations.
- Full OAuth configuration
- Custom scope optimization
- Seamless transition from legacy API
Need Help With Your Shopify Automation?
Transitioning to Shopify's new OAuth requirements can disrupt critical workflows if not done correctly. Our n8n experts will configure your Shopify integration with all required permissions and build custom automations tailored to your business needs.