Resources · Make integration

Shippingbo Make integrationAutomate Shippingbo with Make.

Can Make react the moment an order lands in Shippingbo? Yes: the Shippingbo Make integration offers 7 modules, including 2 instant triggers and 5 actions. This guide is for e-commerce and logistics teams, and it takes you from the connection to a first working scenario.

Try the Shippingbo integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Shippingbo Make integration do for you?

The Shippingbo Make integration links your Shippingbo account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates or sends something. Here, Make can start a scenario when an order is created or shipped, then create orders, addresses and products in Shippingbo.

Tell people when a parcel leaves. Watch Shipped Order starts a scenario as soon as Shippingbo marks an order as shipped, and the next module can post a message in your team chat or update a row in a shared sheet.

Feed Shippingbo from your other tools. An order taken in a form or a quote tool can become a Shippingbo order through Create an Order, with Create an Address attaching the delivery destination.

Keep the catalog in step. When your team adds a product in the tool where it maintains the catalog, Create a Product copies it into Shippingbo.

Where the integration stops: it has no search module, and Make flags its Shippingbo documentation as limited, because little public information exists about the app. Make an API call fills those gaps with the same connection. For a side-by-side view of the two platforms, read n8n vs Make. To learn the editor step by step, Make training is a good start, and Make pricing explains the plans.

Connect

How do you connect Shippingbo to Make?

  1. 01

    Add a Shippingbo module

    Open your scenario, click the +, search for Shippingbo and pick any of its modules. In the module panel, click Create a connection. A connection is your Shippingbo account linked to Make once, then reused by every Shippingbo module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, for example the store or the warehouse it serves. Then follow what Shippingbo asks: either approve Make on the Shippingbo authorization page, or paste the key Shippingbo gives you.

  3. 03

    Save and check the fields

    Click Save. Make can now read your Shippingbo account, and the module fields offer the options it finds there. If the panel shows an error instead, recreate the connection before going further.

First scenario

Build your first scenario: new products into Shippingbo

GoalWhen a product is added in another app, Make creates it in Shippingbo.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where your team lists new products, such as a spreadsheet, and choose its module that watches new rows.

  2. 02

    Add Create a Product

    Click the + on the right of that first module, search for Shippingbo and pick Create a Product. Select your Shippingbo connection, or create it right there.

  3. 03

    Map the incoming data

    Fill the Create a Product fields by mapping values from the first module: click a field, then pick the matching value that came in. Each bundle, meaning one incoming product, becomes one Shippingbo product.

  4. 04

    Test with Run once

    Add one test product in the source app, then click Run once. Make runs the scenario a single time and shows the bundles each module received. Check that the product now appears in Shippingbo.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From that point, each new product in the source app reaches Shippingbo.

Triggers

What can start a Shippingbo scenario?

2 modules start a scenario when something happens in Shippingbo. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Shippingbo as soon as it happens.

Shippingbo1Watch New Order

Watch New Order

Instant trigger

In Make“Triggers when a new order is created in Shippingbo.”

Watch New Order starts your scenario every time an order is created in Shippingbo, so the rest of the flow works on fresh orders without anyone copying them by hand. Each new order arrives in Make as one bundle, the item passed on to the next module.

How it fires
instant. Shippingbo calls Make through a webhook as soon as the order exists, so there is no polling interval to wait for.
When to use it
a sales team wants a message in its chat tool, or a line in a shared sheet, for each order that enters Shippingbo.
Watch out
every new order runs the whole scenario and uses operations, the executions Make counts on your plan, so keep the flow short on a busy store.
Shippingbo2Watch Shipped Order

Watch Shipped Order

Instant trigger

In Make“Trigger when an order is shipped.”

With Watch Shipped Order, the scenario kicks off at the moment Shippingbo records an order as shipped, which gives you a clean point to inform the customer or the team. The shipped order comes through as one bundle you can map into later modules.

How it fires
instant: Shippingbo notifies Make through a webhook as soon as the shipment happens.
When to use it
customer service wants a note in the CRM, or accounting wants the order flagged as ready to invoice, once the parcel has left.
Watch out
this trigger waits for the shipment; if the flow must start at order creation, pick Watch New Order instead.
Modules

What can Make do in Shippingbo?

Shippingbo gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Shippingbo1

Create an Address

Action

In Make“Creates an address for an order.”

Create an Address attaches an address to an order in Shippingbo, so a delivery destination collected elsewhere ends up where the warehouse works.

When to use it
an order was created from another tool and its delivery details sit in a separate form or spreadsheet row.
Watch out
the address belongs to an order, so place this module after the step that creates or receives that order, and map the order from that step.
Shippingbo2

Create an Order

Action

In Make“Creates an order.”

Thanks to Create an Order, data that arrives in the scenario becomes a new Shippingbo order, which spares your team from retyping orders taken outside the online store.

When to use it
a quote accepted in your sales tool, or a phone order logged in a form, has to be prepared and shipped.
Watch out
Make also lists Create an Order V2 with the same short description, and its documentation does not explain the difference; test both with Run once before choosing.
Shippingbo3

Create an Order V2

Action

In Make“Creates an order.”

Behind the name Create an Order V2 sits a second version of the order creation module, which also gives you a new order in Shippingbo from the data your scenario carries.

When to use it
you are starting a fresh scenario and want to compare it with the first version on a real test order before settling on one.
Watch out
keep a single order module per scenario, because running both on the same bundle would create the order twice.
Shippingbo4

Create a Product

Action

In Make“Creates products in your Shippingbo account.”

Create a Product adds items to your Shippingbo catalog from another source, so a new product exists in Shippingbo before its first order comes in.

When to use it
the product team keeps the master list in a spreadsheet or another app and wants Shippingbo to follow it.
Watch out
the integration has no module to update a product, so a later correction in the source will not reach Shippingbo through this module.
Shippingbo5

Make an API call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API call reaches any endpoint of the Shippingbo API from your scenario, with the connection you already set up, for everything the other modules leave out.

When to use it
you need to read or change Shippingbo data, since this integration offers no search module and no update module.
Watch out
you write the request yourself, and Make documents Shippingbo only briefly, so keep the Shippingbo API documentation at hand while you build it.
Need help

Need help automating Shippingbo with Make?

A person reads every message.

FAQ

Shippingbo and Make: frequent questions

01Is the Shippingbo Make integration free?
Yes. Shippingbo is a standard app in Make, so its modules work on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations each month, one per module run on one bundle. Your Shippingbo subscription is a separate matter that Make does not cover.
02What do you need to connect Shippingbo to Make?
A Shippingbo account and a Make account are enough to start, since the Make documentation lists no other prerequisite. Add any Shippingbo module, click Create a connection, name it if you want, then either authorize Make on the Shippingbo page or paste the key Shippingbo gives you, and click Save. That single connection then serves all 7 Shippingbo modules. The documentation for this app is flagged as limited, so if a screen differs from these steps, follow what Shippingbo displays.
03Do Shippingbo triggers in Make fire in real time?
Yes. Both Shippingbo triggers, Watch New Order and Watch Shipped Order, are instant. Shippingbo calls Make through a webhook as soon as an order is created or shipped, so the scenario starts right away instead of waiting for a schedule. That is the lightning badge on the module in the editor. This app has no scheduled trigger, the kind Make polls every 15 minutes by default. For any other event, you can still start a scenario on a schedule and use Make an API call to fetch the data.
04What if a Shippingbo module is missing in Make?
Use Make an API call. It calls any endpoint of the Shippingbo API with your existing connection, which covers what the 5 actions and the 2 triggers leave out, such as reading or updating records, since the integration has no search module. Make flags its Shippingbo documentation as limited, so rely on the Shippingbo API documentation to write the request. If part of the job belongs to another tool, add that app's module next to Shippingbo in the same scenario, and let each module handle its own side.
05Should you use Make or n8n for Shippingbo?
It depends on your criteria rather than on a winner. In Make, Shippingbo offers 7 modules: 2 instant triggers on new and shipped orders, 4 creation actions and Make an API call for everything else. That covers order intake and shipping updates without code. The same app often has an n8n node too, so list the events and actions your flow needs and check that each tool covers them. The n8n vs Make comparison linked above sets out the criteria for both platforms without ranking them.
Same platform

Other docs you might need on this stack.

Browse all integrations