Resources · Make integration

Arlo Make integrationAutomate Arlo with Make.

Every new Arlo registration, order or contact can start a workflow on its own. The Arlo Make integration gives you 32 modules: 16 triggers, 9 actions and 7 searches. This guide shows how to link your account, build a first scenario and pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Arlo Make integration automate for you?

The Arlo Make integration links your Arlo account to Make so that registrations, orders, events and contacts move to your other tools without copy and paste. You build a scenario, which is the automation itself: a chain of modules, where each module is one brick such as a trigger, an action or a search.

Orders that reach finance on their own. Watch Order Created fires the moment an order lands in Arlo, so your accounting sheet or invoicing tool gets the line without waiting for someone to export it.

A cleaner contact base. When a lead fills a form in another app, Search Contacts checks whether the person already exists in Arlo, then Create a Contact or Update a Contact does the right thing. Create an Organisation keeps company records in step.

Course follow-up without manual lists. Watch Elearning Registration Created and Watch Multi-Session Registration Created pass each new learner to your email or chat tool, so a welcome message goes out without anyone building a list first.

Know the limits before you start. The Make documentation for Arlo lists its modules flat, without groups, and warns that its text is AI-generated from the official Arlo documentation, so check anything important with Arlo directly. Six of the triggers are scheduled rather than instant. When a need falls outside the listed modules, Make an API Call reaches the rest of the Arlo API with the same connection.

New to the editor? The Make training walks through the basics, Make pricing explains what each plan allows, and n8n vs Make helps if you are still choosing a platform.

Connect

How do you connect your Arlo account to Make?

  1. 01

    Prepare an OAuth client in Arlo

    You need an active Arlo account. In your Arlo developer account, open the OAuth clients section and create a new client. If Arlo asks for a callback URI, paste https://www.integromat.com/oauth/cb/arlo, then copy the Client ID and the Client secret.

  2. 02

    Add an Arlo module and open the connection

    In your Make scenario, add any Arlo module and click Create a connection. A connection is your Arlo account linked to Make once, then reused by every Arlo module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste your credentials and confirm

    Enter the Client ID and Client secret you copied, or follow the instructions Make shows on screen. Once the connection is saved, Make can read your Arlo data and list the records each module works on.

First scenario

Build your first scenario with Arlo

GoalWhen a form in another app receives a new entry, Make creates the matching contact in Arlo.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big +. The first module you add is the one that starts everything, here the form app you already use.

  2. 02

    Set up the form trigger

    Search your form app by name, pick its module for new entries and link the account. Each entry becomes one bundle, meaning one item passed along to the next module.

  3. 03

    Add Create a Contact

    Click the + to the right of the form module, search Arlo and choose Create a Contact. Link your Arlo account with Create a connection if it is not done yet.

  4. 04

    Map the form answers

    Fill the Arlo fields by picking values from the form module instead of typing them. Each contact then carries the answers of the entry that created it.

  5. 05

    Test with Run once

    Submit a test entry in your form, then click Run once. Read the bundles each module received, and check that the new contact appears in Arlo.

  6. 06

    Schedule and switch it on

    Open the clock on the first module under Scheduling. A new scenario runs every 15 minutes by default. Keep that or change it within your plan, then switch the scenario on.

Triggers

Which Arlo triggers can start a scenario?

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

Arlo1Watch Basic Registration Created

Watch Basic Registration Created

Scheduled trigger

In MakeTriggers when a new basic registration is created.

Each new basic registration in Arlo reaches your scenario as its own bundle, ready to be copied into a sheet, a mailing tool or a CRM.

How it fires
scheduled. Make checks Arlo on the scenario's schedule, which is every 15 minutes by default on a new scenario.
When to use it
simple sign-ups need to land in a shared tracking sheet without anyone exporting them by hand from Arlo.
Watch out
a registration created just after a check waits for the next one. If your plan allows shorter intervals, change the schedule on this module rather than looking for an instant version, since none exists in the module list.
Arlo2Watch Basic Registration Updated

Watch Basic Registration Updated

Scheduled trigger

In MakeTriggers when an existing basic registration is updated.

Changes to an existing basic registration come through here, so the tools that copied it the first time can stay accurate.

How it fires
scheduled, which means Make asks Arlo for updates at the pace set in the scenario's Scheduling.
When to use it
a registration you already pushed to a spreadsheet or an email tool gets edited in Arlo and the copy has to follow.
Watch out
if the same scenario later runs Update a Registration on that record, it produces a fresh update that this trigger can pick up again. Send the changes somewhere other than Arlo to avoid a loop.
Arlo3Watch Contact Created

Watch Contact Created

Instant trigger

In MakeTriggers when a new contact is created.

A person added to Arlo becomes one bundle in Make right away, which lets you greet, tag or copy that contact while the information is fresh.

How it fires
instant. Arlo calls Make through a webhook as soon as the contact exists, with no polling in between.
When to use it
your sales or support team works in another tool and needs every new Arlo contact there, with the same name and email.
Watch out
when you add this module, click Create a webhook before Create a connection. Without the webhook, Arlo has nowhere to send the event and the scenario stays silent.
Arlo4Watch Contact Updated

Watch Contact Updated

Instant trigger

In MakeTriggers when an existing contact is updated.

Edits on an existing Arlo contact are pushed to your scenario, so a phone number or an address fixed in Arlo can be fixed everywhere else too.

How it fires
instant: Arlo notifies Make by webhook the moment the contact changes.
When to use it
Arlo is where contact details are kept clean, and a CRM or newsletter list must mirror those corrections.
Watch out
do not pair it with Update a Contact on the same person in the same scenario. Each update would call the webhook again and the scenario would keep running itself, spending operations for nothing.
Arlo5Watch Elearning Registration Created

Watch Elearning Registration Created

Scheduled trigger

In MakeTriggers when a new elearning registration is created.

This trigger collects every new elearning registration and turns each one into a bundle your scenario can act on, from a welcome email to a row in a report.

How it fires
scheduled. Make polls Arlo on the scenario's schedule instead of receiving a push.
When to use it
learners who sign up for an online course should get onboarding material from your email tool without a manual export.
Watch out
Arlo also has Watch Online Activity Created, which is instant and follows the online activity itself. Pick this one for the learner's registration, the other for the course record.
Arlo6Watch Elearning Registration Updated

Watch Elearning Registration Updated

Scheduled trigger

In MakeTriggers when an existing elearning registration is updated.

Updates to an elearning registration flow into Make here, which keeps any list built from those registrations in line with Arlo.

How it fires
scheduled, checked by Make at the interval chosen on the first module, 15 minutes unless you change it.
When to use it
the status of an online learner changes in Arlo and your tracking sheet or learning dashboard must show the new state.
Watch out
run Run once after editing a test registration in Arlo, then read the bundle. You see exactly what Make receives before you map anything, which avoids guessing field names.
Arlo7Watch Event Created

Watch Event Created

Instant trigger

In MakeTriggers when a new event is created.

As soon as someone creates an event in Arlo, your scenario receives it, which is handy to announce it or to prepare the logistics elsewhere.

How it fires
instant. The event is sent by Arlo to Make through a webhook as soon as it is saved.
When to use it
a new session must appear in a shared calendar, a team chat channel or a planning board without someone copying the details.
Watch out
the webhook only exists once you click Create a webhook on this module. Save the scenario and switch it on, otherwise the events Arlo sends are not processed.
Arlo8Watch Event Updated

Watch Event Updated

Instant trigger

In MakeTriggers when an existing event is updated.

A change to an existing Arlo event, such as a new date or venue, reaches Make at once so the people and tools that depend on it can react.

How it fires
instant, pushed by Arlo through a webhook when the event is edited.
When to use it
trainers or attendees need a message when an event they are tied to changes, sent from your email or chat app.
Watch out
every saved edit is a new update, even a typo fix. Before you send messages to attendees, test with Run once on a minor change to see what they would receive.
Arlo9Watch Multi-Session Registration Created

Watch Multi-Session Registration Created

Scheduled trigger

In MakeTriggers when a new multi-session registration is created.

New registrations to multi-session events arrive here one by one, so a learner signed up for a full program can be followed from the first day.

How it fires
scheduled. Make looks for new records in Arlo at each run of the scenario's schedule.
When to use it
a course made of several sessions needs a separate welcome sequence or a dedicated tracking sheet, distinct from one-off events.
Watch out
this one is scheduled, while Watch Registration Created is instant. Running both on the same sign-ups can handle a learner twice, so pick the one that fits your need.
Arlo10Watch Multi-Session Registration Updated

Watch Multi-Session Registration Updated

Scheduled trigger

In MakeTriggers when an existing multi-session registration is updated.

When an existing multi-session registration is edited, this trigger passes the new version to your scenario, keeping downstream copies correct.

How it fires
scheduled; Make fetches the updates from Arlo on the rhythm of the first module's clock.
When to use it
a participant switches sessions or their registration changes, and the attendance sheet used by your trainers must show it.
Watch out
on the Free plan the shortest interval is 15 minutes, so a change may appear later than expected. Plan your messages accordingly instead of promising an immediate reaction.
Arlo11Watch Online Activity Created

Watch Online Activity Created

Instant trigger

In MakeTriggers when a new online activity (elearning) is created.

Creating an online activity, the elearning item itself, sends it to Make instantly, which lets you publish or catalogue it without delay.

How it fires
instant. Arlo contacts Make over a webhook as soon as the activity exists.
When to use it
a new online course has to show up on a catalog page, in a newsletter draft or in your internal course list.
Watch out
this follows the activity, not the learners. To react to people who sign up for it, use Watch Elearning Registration Created, which is scheduled.
Arlo12Watch Online Activity Updated

Watch Online Activity Updated

Instant trigger

In MakeTriggers when an existing online activity (elearning) is updated.

Edits to an existing online activity are pushed to your scenario, so any page or list that describes that elearning item can be refreshed.

How it fires
instant, through a webhook Arlo calls when the activity changes.
When to use it
a course description or status is corrected in Arlo and the copy on your catalog or in your team documentation must match.
Watch out
the Free plan keeps 2 active scenarios. If you split created and updated activities into two scenarios, you may reach that ceiling quickly, so one scenario with both paths can be wiser.
Arlo13Watch Order Created

Watch Order Created

Instant trigger

In MakeTriggers when a new order is created.

Each new order placed in Arlo lands in your scenario instantly, ready to become an invoice line, a sales alert or a row in a revenue sheet.

How it fires
instant. Arlo sends the order to Make by webhook the moment it is created.
When to use it
finance wants every order in its accounting tool, or sales wants a chat message the moment a customer buys.
Watch out
test with a real order in a safe setup, then Run once. Mapping from a genuine bundle is far more reliable than guessing what an order contains.
Arlo14Watch Order Updated

Watch Order Updated

Instant trigger

In MakeTriggers when an existing order is updated.

This trigger reports changes to existing orders the moment they happen, which keeps billing and reporting tools aligned with Arlo.

How it fires
instant; a webhook from Arlo wakes the scenario as soon as the order is edited.
When to use it
an order is cancelled, corrected or completed in Arlo and your accounting sheet must reflect its new state.
Watch out
if one scenario handles both new and updated orders, write to a record you can find again, such as a row matched on the order, so updates do not create duplicates.
Arlo15Watch Registration Created

Watch Registration Created

Instant trigger

In MakeTriggers when a new registration is created.

New registrations in Arlo trigger your scenario instantly, the broadest way to react whenever someone signs up for something you run.

How it fires
instant. Arlo calls Make through a webhook as soon as the registration is saved.
When to use it
you want one welcome flow for every sign-up, whatever the event type, without separate scenarios per kind.
Watch out
Arlo also offers scheduled triggers for basic, elearning and multi-session registrations. Using this one alongside them can process the same sign-up twice, so choose one approach.
Arlo16Watch Registration Updated

Watch Registration Updated

Instant trigger

In MakeTriggers when an existing registration is updated.

Any edit to an existing registration reaches Make immediately, so cancellations or status changes spread to your other tools without a delay.

How it fires
instant, sent by Arlo over a webhook the moment the registration changes.
When to use it
a trainer's attendee list, a waiting list or a CRM record must update as soon as a participant's registration moves.
Watch out
Update a Registration in the same scenario would fire this trigger again. Keep writes back to Arlo in another scenario so the two never feed each other.
Modules

What can the Arlo modules do in a scenario?

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

Arlo1

Create a Contact

Action

In MakeCreates a new contact.

Adds a new person to Arlo from data that arrives in your scenario, so leads from forms or other apps reach Arlo without retyping.

When to use it
a web form or a CRM captures a prospect who should exist in Arlo before registering.
Watch out
run Search Contacts first, or the same person can be created twice.
Arlo2

Create an Organisation

Action

In MakeCreates a new organisation.

Creates a company record in Arlo, giving the contacts who work there a proper home instead of a loose text field.

When to use it
a new client company signs a deal in your CRM and its team will book sessions through Arlo.
Watch out
check with Search Organisations first, because company names are often typed slightly differently.
Arlo3

Get a Contact

Action

In MakeRetrieves an existing contact.

Fetches one Arlo contact you already know, returning its full details for the next modules in the scenario to use.

When to use it
a previous module gives you a contact reference and you need the complete record, for example to address an email correctly.
Watch out
it reads a single known record; to find people by criteria, Search Contacts is the right tool.
Arlo4

Get an Organisation

Action

In MakeRetrieves an existing organisation.

Retrieves the full record of one Arlo organisation, which lets a scenario enrich a message or a report with company details.

When to use it
an order or a contact points to an organisation and your invoice or CRM entry needs the company information too.
Watch out
you need the organisation reference from an earlier module; without it, start with Search Organisations.
Arlo5

Get a Registration

Action

In MakeRetrieves an existing registration.

Pulls the complete version of a single registration from Arlo, useful when an earlier step only carried part of the information.

When to use it
a scheduled search or another app hands you a registration reference, and you need its current details before sending a confirmation.
Watch out
right after a registration trigger, the bundle may already hold what you need. Run once and compare before adding an extra operation.
Arlo6

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Calls any endpoint of the Arlo API with your existing connection, which covers what the dedicated modules do not.

When to use it
you need an Arlo object or action that has no dedicated module in Make.
Watch out
you describe the request yourself, so read the Arlo API documentation first and test each call with Run once before switching the scenario on.
Arlo7

Update a Contact

Action

In MakeUpdates an existing contact.

Changes the details of an existing Arlo contact, keeping Arlo in line when information is corrected somewhere else.

When to use it
a customer updates their profile in your CRM or a form, and Arlo must hold the same email and phone.
Watch out
never place it in a scenario that starts with Watch Contact Updated on the same contact, or the two will keep triggering each other.
Arlo8

Update an Organisation

Action

In MakeUpdates an existing organisation.

Edits an existing organisation in Arlo so company records follow what your sales or finance tools know.

When to use it
a client company changes its name or billing details in your CRM and Arlo should show the same thing.
Watch out
map only the fields you really want to change; test with Run once on a sample company before running it on your real list.
Arlo9

Update a Registration

Action

In MakeUpdates an existing registration.

Modifies an existing registration in Arlo from your scenario, which saves manual edits when the change is decided in another tool.

When to use it
a payment confirmed in your billing app or an answer in a survey should change the matching Arlo registration.
Watch out
Watch Registration Updated reacts to this change; keep the two in separate scenarios so they do not loop.
Arlo10

Search Basic Registrations

Search

In MakeSearches for basic registrations or lists them all.

Finds basic registrations in Arlo that match your criteria, or lists them all, and returns each one as its own bundle.

When to use it
you need to send a reminder to everyone registered for a simple event, starting from a trigger in another app.
Watch out
a search can return zero, one or many bundles, and every following module runs once per bundle, which counts operations.
Arlo11

Search Contacts

Search

In MakeSearches for contacts or lists them all.

Looks up people in Arlo, or lists every contact, so a scenario can check before it creates or changes anything.

When to use it
a new lead arrives from a form and you want to know whether Arlo already has that person before choosing between create and update.
Watch out
a search can return zero, one or several contacts; read the result of Run once before mapping, so the next module works on the right person.
Arlo12

Search Elearning Registrations

Search

In MakeSearches for elearning registrations or lists them all.

Returns the elearning registrations that match your search, or all of them, one bundle per learner registration.

When to use it
you want a report of online learners in a spreadsheet, or a nudge to those who registered for a given course.
Watch out
listing everything can produce a large batch of bundles; narrow the search so later modules do not spend operations on records you ignore.
Arlo13

Search Events

Search

In MakeSearches for events or lists them all.

Pulls a set of Arlo events, filtered by your criteria or complete, which is the base for calendars, catalogs and planning sheets.

When to use it
your website or a shared planning board must show the upcoming events defined in Arlo.
Watch out
each event comes back as a separate bundle, so the next module runs once per event; an aggregator can group them when the next app expects a single list.
Arlo14

Search Multi-Session Registrations

Search

In MakeSearches for multi-session registrations or lists them all.

Finds the registrations tied to multi-session events, or lists them all, so programs made of several sessions can be followed as a whole.

When to use it
a trainer asks for the list of participants enrolled in a full program before its first session.
Watch out
it returns people’s registrations, not the programs; to list the programs themselves, use Search Events.
Arlo15

Search Orders

Search

In MakeSearches for orders or lists them all.

Retrieves Arlo orders matching your criteria, or every order, ready to be summed, exported or checked against your accounting.

When to use it
finance wants to reconcile Arlo orders with payments recorded in another tool.
Watch out
for new orders as they happen, Watch Order Created is instant and a better fit, since each search and every module after it counts operations.
Arlo16

Search Organisations

Search

In MakeSearches for organisations or lists them all.

Looks for companies stored in Arlo, or lists them all, so a scenario can reuse an existing organisation instead of creating a duplicate.

When to use it
before Create an Organisation, when a new client comes from your CRM and may already be in Arlo.
Watch out
a search on a common word may return several companies; check the bundles from Run once before mapping one of them.
Need help

Need help automating Arlo with Make?

A person reads every message.

FAQ

Questions about the Arlo Make integration

01Is the Arlo Make integration free?
Yes, Arlo is a standard app in Make, available from the Free plan. The Free plan lets you keep 2 active scenarios, with 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 (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations, one per module run on one bundle. You still need an active Arlo account, whose own subscription is separate.
02What do you need to connect Arlo to Make?
You need an active Arlo account and access to its developer area. There, open the OAuth clients section, create a new client, enter the callback URI given by Make if Arlo asks for it, and copy the Client ID and the Client secret. In Make, add any Arlo module, click Create a connection, give it a name if you like, and paste the two values. The connection is then reused by every Arlo module of your scenarios. For an instant module, click Create a webhook first, then Create a connection.
03Do Arlo triggers in Make react in real time?
It depends on the trigger. Out of 16 Arlo triggers, 10 are instant: Arlo calls Make through a webhook as soon as a contact, event, online activity, order or registration is created or updated. The 6 others, for basic, elearning and multi-session registrations, are scheduled: Make checks Arlo on the scenario's schedule, every 15 minutes by default. On the Free plan that interval cannot go below 15 minutes; paid plans allow 1 minute. If speed matters for registrations, Watch Registration Created is instant.
04What if an Arlo module is missing in Make?
Use Make an API Call. It calls any endpoint of the Arlo API with the connection you already set up, so objects or actions without a dedicated module stay within reach. You write the request yourself, so keep the Arlo API documentation open and test each call with Run once. Also keep in mind that Make's own documentation for Arlo says it was generated with AI from the official Arlo documentation and may contain mistakes, so confirm any important behavior with Arlo directly before relying on it.
05Should you use Make or n8n with Arlo?
It depends on your criteria. On Make, Arlo comes with 32 ready modules, a connection you set up once, and instant triggers for contacts, events, orders and registrations, which suits people who want to build visually from a guided editor. n8n often has a node for the same apps, so check whether one exists for Arlo and which operations it covers before deciding. Compare the modules you actually need on each side rather than the platforms in general, then test your main scenario on the one that covers it.