Skip to main content

Connect n8n or Make

SKU.io doesn't have a packaged app for n8n or Make (formerly Integromat), but both connect to it well through two standard pieces:

  • Calls into SKU.io, such as creating an order or reading stock, go through the REST API with a personal access token.
  • News out of SKU.io, such as an order shipping or stock being adjusted, reaches them through a webhook that starts the workflow or scenario.

This guide sets up both. The API reference, with every endpoint and field, lives at developer.sku.io.

Before you begin​

  • You need access to Settings → Developer in SKU.io.
  • In n8n you use the HTTP Request and Webhook nodes. In Make you use the HTTP app's Make a request module and the Webhooks app's Custom webhook trigger.
  • Your SKU.io address is your account's own web address, for example https://yourcompany.sku.io. API calls go to that address followed by /api/….

Steps​

1. Create a token for the platform​

  1. Go to Settings → Developer → Personal Access Tokens and click Create Token.
  2. Name it after the platform, such as n8n automations, so you know what to revoke later.
  3. Tick only the scopes your automations need. For example, reading orders needs orders:read, and creating them needs orders:write.
  4. Create the token and copy it straight into the platform's credential store. SKU.io shows it once.

The full walkthrough is in Create a personal access token, and every scope is listed in the API scopes reference.

2. Store the token on the platform​

  • n8n: create a Header Auth credential with the name Authorization and the value Bearer followed by your token.
  • Make: in the HTTP module, add a header named Authorization with the value Bearer followed by your token. Make a keychain entry for it if you'll reuse it.

Add a second header, Accept: application/json, so errors come back in a form the platform can read.

3. Call SKU.io​

  1. Add an HTTP Request node (n8n) or a Make a request module (Make).
  2. Set the method and the URL from the API reference. A good first call is a GET to your SKU.io address followed by /api/me: it answers with the account and the scopes the token carries, so you know the connection is right before you build anything on it.
  3. Pick the credential or header you set up in step 2.
  4. Run the node or module once and check the response.

If the call is refused for permissions, the token is missing a scope. See Fix a 403 from your API token.

4. Start a workflow from a SKU.io event​

  1. In n8n, add a Webhook node and copy its Production URL. In Make, add a Custom webhook trigger and copy its address.
  2. In SKU.io, go to Settings → Developer → Webhooks and click Create Webhook.
  3. Pick the Event, such as sales_order.shipped, and paste the address into Target URL. It must be an HTTPS address that's reachable from the internet.
  4. Click Create webhook and store the signing secret it shows you.
  5. Open the subscription and click Send test delivery. The test arrives in n8n or Make, so the platform learns the shape of the data.

Each delivery is signed with your secret in the X-SKU-Signature header. To reject anything that didn't come from SKU.io, check that signature in a step before the rest of the workflow runs. The method is in Subscribe to webhooks.

Keep it healthy​

  • Watch failed deliveries under Settings → Developer → Webhooks, see Monitor webhook deliveries.
  • Watch the token's usage and expiry on its own page under Personal Access Tokens, and rotate it before it expires, see Manage personal access tokens.
  • If the automation runs entirely inside SKU.io, such as a scheduled reminder or an import from an FTP folder, a workflow does it with no outside platform at all.

Next steps​

Last verified: