Resources · Zapier integration

nocnoc Zapier integrationAutomate nocnoc with Zapier.

The nocnoc Zapier integration gives you 1 trigger, 3 actions and 1 search to move orders, shipping notices and SKU data between nocnoc and the rest of your tools, without retyping a tracking number or a stock count by hand.

See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the nocnoc Zapier integration does for a cross-border seller

The nocnoc Zapier integration links your nocnoc account to Zapier, a tool that runs automations between apps for you. Each automation is a Zap: one trigger, the event that starts it, then one or more actions that run every time that event happens. With nocnoc, that means orders coming out, and stock, prices and tracking going in.

Three results come back again and again. An order log that fills itself: New Orders picks up each order created in nocnoc and hands it to a sheet, a CRM or a team chat. A tracking number that reaches nocnoc without anyone copying it: Send Notification for Shipped Order tells nocnoc that a parcel left, with its carrier tracking number and link. A catalog whose stock and FOB price follow your warehouse: Update SKU fixes one product, and Update SKU (With Line Item Support) pushes a whole list in a single step.

Now the limits, because they shape what you can build. There is only one trigger, and it watches new orders: nothing fires when an order ships, gets cancelled or when a product changes. There is no action to create a product, cancel an order or answer a customer. And the only lookup is Find Product by SKU, so you need the SKU in hand before you can read anything back.

If you are weighing other tools for the same job, the n8n vs Zapier and Make vs Zapier comparisons set the criteria side by side, without crowning a winner.

Vocabulary

Zapier vocabulary in one minute

Seven words cover everything on this page. Read them once, the rest follows.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event shows up.
Trigger
The event in an app that starts the Zap. Here it is a new nocnoc order; once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or updates something for you, like a SKU's stock.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan is a count of those.
Polling vs instant
A polling trigger is checked on a timer for anything new. An instant one is reported by the app the moment it happens.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops the run otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can reuse what it found.
Cost

What a nocnoc Zap really costs

nocnoc is not a premium app, so it works from the free plan. What you spend is tasks, and only completed actions count.

  • Free plan100 tasks per month, unlimited Zaps
  • Zap size on free2 steps: one trigger, one action
  • Trigger checksNever billed
  • Premium appNo, nocnoc works on the free plan

The New Orders trigger never costs a task, however often Zapier checks. Each action that succeeds counts once, so a Zap that sends a shipping notice and then updates a SKU spends two tasks per order. An action that fails is not counted. The catch on the free plan: Zaps stop at two steps, one trigger and one action. Add a filter, a search like Find Product by SKU or a second action, and you have a multi-step Zap, which needs a paid plan.

Connect

Connect nocnoc to Zapier in 3 steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your nocnoc account linked once, then reused by every step that touches nocnoc.

  2. 02

    Pick nocnoc

    Type nocnoc in the search box of the dialog, select it, then confirm with Add connection. You need an existing nocnoc account, plus access to any catalog you do not own yourself.

  3. 03

    Sign in and grant access

    A new tab opens on nocnoc. Sign in with the account that holds your products and orders, then allow Zapier to use it. From then on, every nocnoc step reuses that connection.

First Zap

Your first nocnoc Zap: refresh a product when an order lands

GoalEach new nocnoc order looks up its product by SKU, then updates that SKU's stock in nocnoc.

  1. 01

    Create the Zap

    Click Create, then Zap. The editor opens on an empty trigger card, waiting for you to pick an app and the event that should start everything.

  2. 02

    Set the trigger

    Choose nocnoc, then the New Orders event, and select the connection you just added. This is a polling trigger: Zapier checks for new orders on a timer.

  3. 03

    Test it on real orders

    Run the test: Zapier brings back the three most recent orders of the account. Pick one that looks like your usual order, so the mapping that follows rests on real values.

  4. 04

    Add the search, then the action

    Add Find Product by SKU and map the SKU from the order, if your orders carry it. Then add Update SKU, map the same SKU and the new stock value.

  5. 05

    Test, then publish

    Test each step and read what came back, then click Publish. With a search in the middle, this Zap has three steps, so it needs a paid plan.

Triggers

The nocnoc trigger

1 event starts a Zap when something happens in nocnoc. Zapier checks for them at the interval your plan allows.

1

New Orders

Polling trigger

In Zapier“Triggers when a new order is created.”

Starts your Zap each time a new order appears in your nocnoc account, whatever marketplace it came from. Every order arrives as its own run, so the steps after it handle one order at a time.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
you want each fresh order copied into the sheet or chat your logistics team already lives in, so nobody has to refresh the nocnoc dashboard to know what to pack.
Watch out
it only sees orders created after the Zap is published, so the orders already sitting in nocnoc stay out of the flow.
Actions

The 3 nocnoc actions

nocnoc gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Send Notification for Shipped Order

Action

In Zapier“Send notification for shipped order and inform the tracking number.”

Tells nocnoc that a parcel has left and hands over the carrier's tracking number and tracking link, so nobody retypes them by hand.

When to use it
your shipping tool produces the label and you want nocnoc told the second it exists.
Watch out
the order ID, tracking number, tracking URL, SKU and units shipped are all required, so a source missing any one of them blocks the step.
2

Update SKU

Action

In Zapier“Update stock and/or FOB price for a particular SKU.”

Changes the stock, the FOB price, or both, on one product identified by its nocnoc SKU.

When to use it
a single row changes in your inventory file and you want that one product corrected on the marketplaces through nocnoc.
Watch out
only the SKU is required, so check that the stock or the FOB price you want changed is actually mapped before you publish.
3

Update SKU (With Line Item Support)

Action

In Zapier“Update price and/or stock for a multiple SKUs”

Pushes stock and FOB price for several products at once, one line per SKU, in a single step of the Zap.

When to use it
your warehouse exports a whole batch of quantities and prices, and you would rather spend one task than one per product.
Watch out
here the SKU, the stock quantity and the FOB price are all required on every line.
Searches

The nocnoc search

1 search step looks for data that already exists in nocnoc, so a later step can use it.

A search step sits under the SEARCH heading at the bottom of the Action event list. Three settings decide what happens when the lookup does not go as planned.

1

Find Product by SKU

Search

In Zapier“Search for a Product by its SKU and retrieve its basic information”

Looks up a product in nocnoc from its SKU and returns its basic details to the steps that follow.

When to use it
before an update, you want to confirm that the SKU coming from your spreadsheet really exists in nocnoc, and stop the Zap when it does not.
Watch out
nocnoc decides whether the SKU must match exactly, so test with a code that has a near twin in your catalog.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps relying on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Turns a search into find-or-create. nocnoc offers no such variant, so this box does not show up on Find Product by SKU.
  3. If multiple search results are found?
    Keep the first match, which is the default, stop the Zap, or hand all the matches on at once.
When it breaks

When a nocnoc Zap breaks

Zapier attaches no help article to nocnoc, so the known failures are the ones every Zap shares. Four of them hit a commerce flow hard.

Most broken nocnoc Zaps come down to timing or to a Zap feeding itself. When a run fails and you cannot see why, the Zapier troubleshooting guide walks through the checks in order.

  • Old orders never show up

    A Zap only reacts to what happens after it is switched on. The orders already in nocnoc are not picked up; moving that backlog is a separate job.

  • The Zap feeds itself

    A Zap that writes back into the place its own trigger watches sets itself off again and again, and burns through your tasks fast.

  • A big import gets held back

    After a bulk import or a migration, a trigger that suddenly returns a huge batch can be held back by Zapier's flood protection.

  • The same order twice? No

    Zapier remembers what it has already seen on a polling trigger, so one order does not start the Zap twice.
Need help

Need help automating nocnoc with Zapier?

A person reads every message.

FAQ

nocnoc Zapier integration: frequent questions

01Is the nocnoc Zapier integration free?
Yes, as far as Zapier goes: nocnoc is not a premium app, so it runs on the free plan. That plan gives you 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps, one trigger and one action. As soon as you add a search, a filter or a second action, the Zap becomes multi-step and you need a paid plan. Your nocnoc account itself is a separate matter, handled with nocnoc.
02How many tasks does a nocnoc Zap use?
One task per action that completes, nothing for the trigger. A Zap that takes each new order and updates one SKU spends one task per order. If it also sends a shipping notice, that is two tasks per order. Checking for new orders costs nothing, however often Zapier looks, and an action that fails is not counted. Update SKU (With Line Item Support) is useful here: one step can carry several products.
03Does the nocnoc trigger work in real time?
No. New Orders is a polling trigger: Zapier checks nocnoc on a timer and keeps what it has not seen yet. On the free plan that check happens every 15 minutes, on Professional every 2, on Team and Enterprise every minute. The type comes from nocnoc's own setup and cannot be switched from the editor. On paid plans you can also run a check by hand from the editor when you are testing.
04What does it take to connect a nocnoc account to Zapier?
An active nocnoc account and a Zapier account. From the Apps page in Zapier you add a connection, pick nocnoc, sign in in the tab that opens and grant access. If the products or orders you want the Zap to touch belong to someone else, you also need read or write access on them. Once linked, the connection is reused by every step that uses nocnoc. Testing the trigger then brings back your three most recent orders, a quick sign that the access works.
05Why does the nocnoc shipping notice fail on some orders?
Usually because one required field arrives empty. Send Notification for Shipped Order needs the order ID, the tracking number, the tracking URL, the SKU and the quantity shipped, all five, on every run. If your carrier tool skips the tracking link on some parcels, the step stops there. A filter placed before the action can hold back incomplete shipments, though it turns the Zap into a multi-step one. A step that fails this way is not counted as a task.
06What if the nocnoc operation for the job is missing?
Then Zapier cannot do it with nocnoc today: the five operations listed here are the full visible set. There is no trigger for shipped or cancelled orders, and no action to create a product. Workarounds go through another tool: keep the missing data in a sheet, or start the Zap from your carrier or warehouse app instead. If none of that fits, the job may belong in a different automation tool.
07Zapier, Make or n8n for nocnoc?
It depends on your criteria, not on a ranking. On Zapier, nocnoc is already listed, with its five operations ready to pick. The questions to ask are how many orders you move per month, since every completed action is billed as a task, whether you need events nocnoc does not expose here, and whether someone on your team can maintain a more technical tool. Those three answers decide it. Since nocnoc is not a premium app, a first Zapier test costs nothing on the free plan.
Same platform

Other docs you might need on this stack.

Browse all integrations