Skip to main content

Connect n8n or Make

SKU.io has its own node for n8n. Install it and your n8n workflows can start when something happens in SKU.io, such as a new sales order, and can create or find SKU.io records from any other step. The node is listed in n8n as SKU.io, with n8n's verified badge, so it works on n8n Cloud and on your own n8n server.

Make (formerly Integromat) has no SKU.io app. It connects through the REST API with an API token, and SKU.io webhooks start its scenarios. That's covered in Connect Make.

Before you begin​

  • You need access to Settings → Developer → OAuth Applications in SKU.io. If it isn't in your menu, ask an administrator to register n8n for you. See Register an OAuth application.
  • Installing a node in n8n needs an n8n owner or admin.
  • For triggers, SKU.io has to reach your n8n over HTTPS from the internet. n8n Cloud already can. A self-hosted n8n needs a public HTTPS address.
  • One n8n credential reaches one SKU.io account. If you manage several accounts, add one credential for each.

What the node can do​

KindName in n8nWhen it fires, or what it does
TriggerOn new sales orderA sales order is created, on any channel or by hand
TriggerOn sales order shippedA sales order is shipped
TriggerOn sales order cancelledA sales order is cancelled
TriggerOn new purchase orderA purchase order is created
TriggerOn purchase order submittedA purchase order is sent to the supplier
TriggerOn purchase order approvedA purchase order is approved
TriggerOn purchase order receivedStock is received against a purchase order
TriggerOn inventory adjustedStock is adjusted
TriggerOn new productA product is created
TriggerOn new customerA customer is created
ActionCreate a customer · Find a customer by emailAdds a customer, or looks one up
ActionCreate an inventory adjustmentAdjusts stock for a product at a warehouse
ActionCreate a product · Find a product by SKU · Update a productAdds, looks up, or changes a product
ActionCreate a purchase orderAdds a purchase order for a supplier
ActionCreate a sales order · Find a sales order by numberAdds a sales order with its lines, or looks one up
ActionCreate a supplier · Find a supplier by nameAdds a supplier, or looks one up

Triggers are instant. SKU.io tells n8n the moment the event happens, rather than n8n checking every few minutes. Lists such as Customer, Product, Store, Supplier and Warehouse load from your SKU.io account.

Connect n8n​

1. Install the SKU.io node​

  1. In an n8n workflow, open the nodes panel and search for SKU.
  2. Click SKU.io.
  3. Click Install node. When it's done, the panel shows Installed and lists the node's triggers and actions.

The SKU.io node in n8n after installing, with its ten triggers listed

If your self-hosted n8n doesn't show the node in search, install it by its package name instead: in n8n, go to Settings → Community nodes, click Install a community node, and enter n8n-nodes-sku-io.

2. Copy n8n's redirect URL​

  1. Under Actions, click the action you want, for example Create a customer.
  2. Under Credential, click Connect to SKU.io.
  3. Copy the OAuth Redirect URL at the top of the dialog. Keep the dialog open.

The SKU.io account credential in n8n, showing the OAuth Redirect URL, Client ID, Client Secret and Base URL fields

On n8n Cloud, the address is https://oauth.n8n.cloud/oauth2/callback. A self-hosted n8n shows its own address.

3. Register n8n in SKU.io​

  1. In SKU.io, go to Settings → Developer → OAuth Applications.
  2. Click New OAuth application.
  3. Enter an Application Name such as n8n. Your team sees it on the approval screen and under Connected Apps.
  4. Leave Client type on Confidential (server-side, has secret).
  5. Paste n8n's redirect URL into Redirect URIs.
  6. Click Register.

The New OAuth application dialog filled in for n8n

4. Copy the Client ID and Client Secret​

  1. Copy the Client ID and the Client Secret. SKU.io shows the secret only once.
  2. Check I have copied the Client Secret and stored it safely, and click Done.

The OAuth application created dialog with the Client ID and the Client Secret

If you lose the secret, rotate it, see Manage OAuth applications.

5. Finish the credential in n8n​

  1. Back in n8n, paste the Client ID and the Client Secret into the credential.
  2. Leave Base URL as https://app.sku.io.
  3. Click Save.

The credential saved in n8n, asking you to connect your account

6. Approve the connection​

  1. Click Connect. A SKU.io window opens. Sign in if you aren't signed in already.
  2. Read the Permissions requested. If your login reaches more than one SKU.io account, pick the account under Authorize for account.
  3. Click Approve.

The SKU.io approval screen for n8n, listing the permissions requested and the account

n8n shows Connection successful, and the credential is ready to use.

7. Run your first action​

  1. In the node, check that Credential shows your SKU.io account.
  2. Fill in the action's fields. For Create a customer, enter a Name.
  3. Click Execute step. The output shows the record SKU.io created.

A Create a customer step in n8n with the new customer in its output

To start a workflow from SKU.io instead, add the node's trigger, pick the event, and publish the workflow. Publishing registers a webhook in SKU.io for the event, and taking the workflow offline removes it.

See and remove the connection in SKU.io​

  • Connected app. n8n is listed under Settings → Developer → Connected Apps with the permissions you approved. Revoke it there to cut n8n off straight away. See Review connected apps.

    n8n listed under Connected Apps in SKU.io

  • Webhooks. Each published workflow with a SKU.io trigger has a webhook subscription under Settings → Developer → Webhooks, with its delivery history. See Monitor webhook deliveries.

Troubleshooting​

What you seeWhat to do
Searching n8n for SKU.io finds nothingSearch for SKU instead.
n8n's connection window says Client authentication failedThe Client ID or Client Secret in the credential doesn't match SKU.io. Paste both again. If you no longer have the secret, rotate it in SKU.io and paste the new one.
SKU.io won't open the approval screen for n8nThe address under Redirect URIs has to match n8n's OAuth Redirect URL exactly. Edit the application in SKU.io and paste it again.
A step fails with a permissions messageThe SKU.io user who approved the connection can't do that action. Reconnect as a user who can, or ask an administrator to widen that user's role.
A trigger never firesCheck the workflow is published and that your n8n is reachable over HTTPS from the internet. Then look for its subscription under Settings → Developer → Webhooks and read the delivery log.

Connect Make​

Make has no SKU.io app, so it connects with 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 Make through a webhook that starts the scenario.

The same pieces work in n8n's HTTP Request and Webhook nodes, for anything the SKU.io node doesn't cover. The API reference, with every endpoint and field, lives at developer.sku.io.

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/….

1. Create a token for Make​

  1. Go to Settings → Developer → Personal Access Tokens and click Create Token.
  2. Name it after the platform, such as Make automations, so you know what to revoke later.
  3. Tick only the scopes your scenarios need. For example, reading orders needs orders:read, and creating them needs orders:write.
  4. Create the token and copy it straight into Make. 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. Call SKU.io from Make​

  1. Add the HTTP app's Make a request module.
  2. Add a header named Authorization with the value Bearer followed by your token, and a second header, Accept: application/json, so errors come back in a form Make can read. Make a keychain entry for the token if you'll reuse it.
  3. 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.
  4. Run the 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.

3. Start a scenario from a SKU.io event​

  1. In Make, add the Webhooks app's 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 Make, so the scenario 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 scenario runs. The method is in Subscribe to webhooks.

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.

Next steps​

Video transcript

In n8n, open the nodes panel and search for SKU. Open the SKU.io result, which carries n8n's verified mark. On the details that appear, click Install node. The download takes a few seconds. When it finishes, the panel shows the node as installed. Once it's installed, the panel lists ten triggers. Each one starts a workflow when something happens in SKU.io, such as a new sales order. Below them, under Actions, are eleven steps that add or look up records. Expand that list, and pick Create a customer. The node opens, ready to set up. Under Credential, click Connect to SKU.io. The dialog that opens shows an OAuth Redirect URL at the top. Copy that address, because SKU.io asks for it next. In SKU.io, go to Settings, Developer, then OAuth Applications, and click New OAuth application. Name it n8n, and keep the client type as Confidential. Paste the redirect URL you copied, and click Register. SKU.io then saves the new application. SKU.io now shows the Client ID and the Client Secret. You only see the second one once, so copy both of them now. Then tick the box to confirm you stored it safely, and click Done. Back in n8n, open the Create a customer node again, and click Connect to SKU.io. Paste the Client ID into the first field, and the Client Secret into the second. Then click Save to keep the credential. Now click Connect, and SKU.io opens its approval screen for n8n. It lists every permission n8n is asking for, and below them, the account it will reach. Click Approve, and n8n confirms the connection. Back in the workflow, the node signs in with the credential you just connected. Type a name for the new customer, then click Execute step. A moment later, the output shows the record SKU.io created. In SKU.io, go to Settings, then Developer, and open Connected Apps. n8n is listed with the permissions you approved, and you can revoke its access there at any time.

Last verified: