Connector Details
Name | Value |
---|---|
Platform | Shopify |
Auth Type | API Keys |
Direction | Bidirectional |
Triggers | |
Tap Repo | https://github.com/hotgluexyz/tap-shopify |
Target Repo | https://gitlab.com/hotglue/target-shopify-v2 |
Tap Metrics | Usage: |
Target Metrics | Usage: |
Unified Schema |
Credentials Setup
Follow the steps below to get the credentials you need to use the Shopify connector. There are two ways to use Shopify: either via a Shopify Public App (OAuth) or using a Private App (API keys). hotglue environments will default to private apps, but you can use either. Below are guides to setting up both:Public App (OAuth)
When using Public App (OAuth), make sure to use the Shopify OAuth connector in hotglue instead of the API Key based version.
Register a Shopify Public App
To start, you will need to create a Shopify developer account at shopify.dev. After entering some basic information, you’ll be taken to an overview page. There’s a tab that says “Build apps for clients or the Shopify App Store.” When you click it, you’ll see a button to create an app. Click that too. Once you name your app, you’ll get the Client ID and Client Secret that you need for hotglue. Add a logo and preferences URL while you’re at it.
App Setup
There are two distinct ways to have hotglue manage your Shopify App. See the video walkthrough below explaining each option: In both scenarios, you must:-
Add hotglue to the “Allowed redirection URL.” This should be set to
https://hotglue.xyz/callback
-
Configure a URL to redirect to once the authorization process is complete (
complete_url
). This is done in the JSON definition under Settings -> Connectors -> Sources -> Shopify OAuth
Fully Managed
With this method hotglue will handle generating the tenant ID + creating the config. To use this method, simply set your app URL toSemi Managed
Set a custom app URL (to your webapp for example), and then “forward” the request to hotglue. With this method you can supply the desiredtenant
id in the query params.
Here’s a simplified example using Express to illustrate how the semi-managed flow works:
API Access
Depending on your use case, you may need to request permissions for access to certain scopes. Most use cases will require the “Read all orders” scope, which you can request on this page. If it’s relevant to your app, it isn’t too hard to get this access. You may also be interested in requesting subscription APIs and protected customer data.
Distribution
Once you finish configuring your app and confirming that it works for your own account, you can begin the app registration process. You will want to make your app publicly available, so this can’t be a Single Merchant Install. There is a one-time $99 fee associated with registering to be on the Shopify app store.
Private App (API Key)
These steps will be performed by each of your customers when they connect their Shopify account.


If you plan to both read and write data with Shopify, make sure to enable Read and write access. Otherwise, Read access is sufficient.

Tap Changelog
Tap Changelog
Tap Changelog
Version | Notes |
---|---|
v1.4.13 | |
v1.4.12 | |
v1.4.10 | |
v1.4.9 | |
v1.4.8 | |
v1.4.7 | |
v1.4.6 | |
v1.4.5 | - Update retry logic |
v1.4.4 | - Add new streams - Optimize tap performance |
v1.4.3 - Add shop stream | - Added shop stream |
v1.4.2 - Add support for incoming | Added support for incoming orders |
v1.4.1 - Add support for access_token | Added support to use the key access_token in the config in addition to api_key |