Resources · Make integration

Orbit Make integrationAutomate Orbit with Make.

Can Make keep your Orbit workspace up to date without copy and paste? The Orbit Make integration gives you 8 modules: 1 trigger, 6 actions and 1 search. This guide shows how to link your account, build a first scenario and pick the right module for each job.

Try the Orbit integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Orbit Make integration do for you?

The Orbit Make integration links your Orbit account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick that watches, creates, updates or searches something. Once linked, Make can spot new activities in Orbit and write members, notes and activities for you.

Members that stay complete. When a person signs up somewhere else, a scenario can run Search for a Member by Identity to check whether Orbit already knows them, then Update a Member or Create a Member depending on the answer. No more duplicates typed by hand.

Context your team can read. Watch Activities picks up what happens in Orbit, and Create a Note writes a short summary on the member, so whoever talks to that person next sees the story first.

Activities from tools Orbit does not see. A webinar signup or a support ticket lives in another app. Create an Activity records it on the right member, and Create an Identity for a Member attaches the extra account so the profile stays whole.

What Make does not give you here: detailed documentation. Make says it cannot document Orbit fully because too little public information exists about the app, so test every module with sample data before you rely on it. For anything the listed modules skip, Make an API Call reaches the rest of the Orbit API. If you are weighing tools, read n8n vs Make; to learn the editor first, see Make training, and when a run fails, Make troubleshooting helps.

Connect

How do you connect Orbit to Make?

  1. 01

    Add an Orbit module

    In your scenario, click the +, type Orbit in the search box and pick any Orbit module. The first time, the module asks for a connection: your Orbit account linked to Make once and reused by every Orbit module. Click Create a connection.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later, such as the workspace it points to. That step is optional. Then either approve Make on the Orbit page that opens, or paste the key Orbit gives you, depending on what the window asks for.

  3. 03

    Save and check the module

    Click Save. Back in the module, the connection now appears in its dropdown. If Make can list your Orbit data in the fields below, the link works and every other Orbit module can reuse it.

First scenario

Your first scenario with Orbit

GoalWhen a new activity shows up in Orbit, Make writes a note on the member who did it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the editor. That empty circle becomes your first module.

  2. 02

    Pick Watch Activities

    Search for Orbit, choose Watch Activities and select your connection, or create it now. Fill the fields Make shows; once the connection exists, it lists what it can read in Orbit.

  3. 03

    Add Create a Note

    Click the + on the right of the trigger and pick Create a Note. Map the member from the first module, then build the note text from the activity details it received.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time; open the bubble above each module to read the bundles it got, each bundle being one item, here one activity.

  5. 05

    Schedule it and switch it on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then flip the scenario on. From now on, new activities turn into notes without you.

Triggers

What starts an Orbit scenario

1 module starts a scenario when something happens in Orbit. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Orbit as soon as it happens.

Orbit1Watch Activities

Watch Activities

triggerIn the docs only

Watch Activities hands your scenario each new activity recorded in Orbit, one bundle per activity, so the modules after it can react to what your members actually do.

How it fires
scheduled. Make lists it without a description, and going by its name, it is scheduled: Make checks Orbit on the scenario's schedule, every 15 minutes by default and never more often than that on the Free plan.
When to use it
any flow that starts from member behavior, like posting a note, alerting a teammate in another app or updating a profile.
Watch out
since Make checks on a schedule, a new activity waits for the next check before your scenario sees it.
Modules

Every Orbit module, explained

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

Orbit1

Create a Member

ActionIn the docs only

Create a Member adds a new person to your Orbit workspace, so someone who joined through another channel gets a profile without anyone typing it.

When to use it
after a signup in a form or a shop, once you know the person is not already there.
Watch out
put Search for a Member by Identity in front of it, or the same person can land twice.
Orbit2

Create a Note

ActionIn the docs only

Create a Note pins a piece of text on a member, which gives your team context they would otherwise have to dig out of another tool.

When to use it
to record a sales call summary, a support outcome or what a new activity was about, right on the profile.
Watch out
the module needs to know which member gets the note, so map it from an earlier module.
Orbit3

Create an Activity

ActionIn the docs only

Create an Activity logs something a member did outside Orbit's reach, so the timeline shows the whole relationship and not only what Orbit collects itself.

When to use it
a webinar attendance, a purchase or a ticket closed in another app.
Watch out
activities you create may also reach any scenario that starts from Watch Activities; run it once on a test member to see whether they loop back.
Orbit4

Create an Identity for a Member

ActionIn the docs only

Create an Identity for a Member attaches one more identity to a profile that already exists, so a person who shows up under several accounts stays one member instead of several.

When to use it
when another app hands you a second account for someone Orbit already knows.
Watch out
it works on an existing member only; find that member first with Search for a Member by Identity.
Orbit5

Make an API Call

ActionIn the docs only

Make an API Call is your way around the missing pieces: it calls any endpoint of the Orbit API from the scenario and reuses the connection you already made.

When to use it
the moment you need something none of the other seven modules does.
Watch out
you describe the request yourself, so keep Orbit's API reference open while you fill it in.
Orbit6

Search for a Member by Identity

SearchIn the docs only

Search for a Member by Identity tells you whether Orbit already knows a person, using one of their identities, and returns the matching member so later modules can work on it.

When to use it
before creating, updating or adding an identity, to avoid duplicates.
Watch out
a search can return zero, one or several bundles; add a filter so the next module only runs when you get a match.
Orbit7

Update a Member

ActionIn the docs only

Update a Member changes a profile that exists already, which keeps Orbit in line with the tool where the data really changes, a CRM or a billing app for example.

When to use it
when a person's details change elsewhere and Orbit should follow.
Watch out
it needs the member to update, so it usually comes right after Search for a Member by Identity.
Need help

Need help automating Orbit with Make?

A person reads every message.

FAQ

Orbit and Make: common questions

01Is the Orbit Make integration free?
Yes, Orbit is a standard app in Make, so you can use it from the Free plan. That plan has real limits though: 2 active scenarios, at least 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 lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations, one operation being one module handling one bundle, so a scenario with two modules uses two per item.
02What is needed to connect Orbit to Make?
An Orbit account and a Make account, nothing more that Make documents. Make's Orbit page lists no special prerequisite. You add any Orbit module, click Create a connection, optionally name it, then either authorize Make on the Orbit page that opens or paste the key Orbit provides. Click Save and every Orbit module in your scenarios can reuse that connection. Since the official page is short on detail, check the connection by running one module on test data.
03Does the Orbit trigger in Make work in real time?
No. Watch Activities is a scheduled trigger, going by its name and how Make lists it: Make checks Orbit on the scenario's schedule instead of being told the moment something happens. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest gap allowed between two runs; paid plans go down to 1 minute. If you need a faster reaction, the only lever the page can confirm is a shorter schedule on a paid plan.
04What if an Orbit module is missing in Make?
Use Make an API Call. It lets a scenario call any endpoint of the Orbit API with the connection you already have, so you are not stuck with the 7 other modules. Make itself warns that its Orbit documentation is limited because there is not enough public information about the app, so expect to read Orbit's own API reference to build the request. Test it with Run once before switching the scenario on.
05Should Orbit automations run in Make or n8n?
It depends on the tool your team already knows. In Make, Orbit comes with 8 ready modules, a visual editor and a connection you set once, which suits people who build without code. Apps like Orbit often have an n8n node too, so if your workflows already live in n8n, check whether it covers the same actions before moving anything. The honest test is to rebuild one real flow in each and keep the one your team maintains more easily.
Same platform

Other docs you might need on this stack.

Browse all integrations