Resources · Make integration

Ontraport Make integrationAutomate Ontraport with Make.

Can Make react the moment something changes in Ontraport? Yes. The Ontraport Make integration gives you 16 modules: one instant trigger, 13 actions and 2 searches. This page shows marketers and ops leads how to link the account and ship a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Ontraport Make integration automate?

The Ontraport Make integration links your Ontraport account to Make, a visual tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger, an action or a search. Ontraport sends an event, Make runs the next steps for you, with no code.

Nurture starts on its own. When a web form is submitted, Watch Events wakes the scenario and Add an Object to a Sequence or Campaign drops that record into the follow-up you picked. Nobody has to copy a lead by hand.

Tags drive the rest of your stack. Watch Events also fires when an object is tagged or untagged. A sales team can use that signal to push the record to another tool, or use List Objects With Tag to pull everyone carrying a tag before a campaign goes out.

Records stay in sync. Create an Object, Update an Object and Get an Object let an outside source, a signup sheet or a booking tool, write straight into Ontraport. Messages and rules have their own create and update modules too.

Where the list stops, Make an API Call reaches any endpoint of the Ontraport API with the same connection. The official doc adds a caution: its Ontraport page is AI-generated from the vendor documentation, so check important details with Ontraport. If you weigh other tools, read n8n vs Make, and when a run fails, Make troubleshooting covers the usual errors. To learn the editor properly, see Make training.

Connect

How do you connect Ontraport to Make?

  1. 01

    Get your API Key and App ID

    You need an active Ontraport account. In Ontraport, open the profile icon, then Administration, Integrations and Ontraport API Instructions and Key Manager. Click New API Key, name it, set the contact owner, save, and copy both the API key and the Client ID.

  2. 02

    Open the connection window in Make

    Add any Ontraport module to your scenario and click Create a connection. A connection is your Ontraport account linked to Make once, then reused by every Ontraport module. The Connection name field is optional; a clear name helps when you run several accounts.

  3. 03

    Paste the credentials and save

    Enter the credentials you copied from Ontraport, or follow the instructions shown on screen, then confirm. Starting with Watch Events? That module is instant, so click Create a webhook first, then Create a connection inside it.

First scenario

Your first scenario with Ontraport

GoalWhen a form is submitted in Ontraport, Make adds that record to a follow-up sequence.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module. Search for Ontraport and pick Watch Events.

  2. 02

    Set up the webhook

    Click Create a webhook, then Create a connection and paste your API key and App ID. Fill the module fields; once linked, Make lists what it can read from your account.

  3. 03

    Add the sequence step

    Click the + on the right of the trigger and choose Add an Object to a Sequence or Campaign. Map the record coming from Watch Events and pick the sequence to feed.

  4. 04

    Test with Run once

    Click Run once, then submit a test form in Ontraport. Each module shows the bundles it received, a bundle being one item passed along, here one record. Check it landed in the right sequence.

  5. 05

    Switch it on

    Once the test looks right, switch the scenario on. Every future event now flows through without a click, and each module run counts as one operation on your Make plan.

Triggers

What starts an Ontraport scenario

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

Ontraport1Watch Events

Watch Events

Instant trigger

In MakeReceives events when objects are created, objects are tagged, objects are untagged or forms are submitted.

Watch Events hands your scenario a fresh record each time something meaningful happens in Ontraport: an object is created, an object gets a tag, a tag is removed, or a form is submitted. The record arrives ready to map into the next module.

How it fires
instant. Ontraport calls Make through a webhook as soon as the event happens, so there is no polling interval to set.
When to use it
a new lead fills in your opt-in form and should be routed right away to a sequence, a spreadsheet or a sales tool.
Watch out
the doc asks you to click Create a webhook first on this module, then Create a connection, so follow that order.
Modules

Everything the Ontraport modules can do

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

Ontraport1

Add an Object to a Sequence or Campaign

Action

In MakeAdds objects to sequences or campaigns.

You get a record enrolled in an Ontraport sequence or campaign without opening Ontraport, so the follow-up you already designed starts on cue.

When to use it
right after a purchase or a form entry arrives from another app, to begin onboarding for that person.
Watch out
pick the target sequence carefully, since this module only enrolls; stopping it later needs its sibling, the removal module.
Ontraport2

Create a Message

Action

In MakeCreates a message.

This module gives you a new message stored in Ontraport, built from data your scenario already holds, instead of drafting it in the Ontraport editor.

When to use it
content prepared elsewhere, say in a shared doc or a content tool, should become a ready message in your account.
Watch out
it creates a fresh message each run; to change an existing one, reach for Update a Message.
Ontraport3

Create an Object

Action

In MakeCreates an object of a certain type.

Here you end up with a brand new Ontraport record of the type you select, filled with values mapped from earlier modules.

When to use it
a booking tool or a signup sheet collects people outside Ontraport and you want each one saved in your CRM.
Watch out
this module only creates, so each run adds a record; when a person may already be in Ontraport, change them with Update an Object instead.
Ontraport4

Create a Rule

Action

In MakeCreates a rule.

Create a Rule adds an Ontraport rule to your account from a scenario, so automation logic can be set up alongside the records it concerns.

When to use it
you roll out a repeatable setup for a new offer and want its rule created in the same flow as the rest.
Watch out
check the new rule in Ontraport after a Run once test, before switching the scenario on.
Ontraport5

Delete an Object

Action

In MakeDeletes an object.

Delete an Object removes a record from Ontraport for good, which keeps your database free of entries you no longer want.

When to use it
a person asks to be erased, or a test record created by a scenario needs cleaning up afterwards.
Watch out
treat every deletion as final and test with Run once on a throwaway record before activating.
Ontraport6

Get an Object

Action

In MakeRetrieves an object.

Get an Object fetches one specific Ontraport record so later modules can read its current values instead of guessing.

When to use it
the trigger only passes an identifier and you need the full record before writing to an invoice or a support ticket.
Watch out
it returns a single record; to look through many, Search Objects or List Objects With Tag fit better.
Ontraport7

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Make an API Call lets you reach any endpoint of the Ontraport API from your scenario, reusing the connection you already created, for jobs the listed modules skip.

When to use it
the action you need has no dedicated module here, and the Ontraport API documentation describes it.
Watch out
you write the request yourself, so keep the Ontraport API reference open while you set the path and body.
Ontraport8

Remove an Object from Sequence or Campaign

Action

In MakeRemoves objects from sequences or campaigns

With this module a record leaves a sequence or campaign, so that person stops receiving follow-ups meant for someone else.

When to use it
a prospect becomes a customer in your billing tool and the sales sequence should end at once.
Watch out
point it at the exact sequence the record is in; removing from the wrong one leaves the real follow-up running.
Ontraport9

Tag Objects

Action

In MakeAdds tags to objects.

Tag Objects puts one or more tags on Ontraport records, giving your segments and automations a clear label to work with.

When to use it
a webinar platform or payment tool reports an event and you want Ontraport to know it through a tag.
Watch out
a deduction, not a doc statement: a tag added here is likely to wake a Watch Events scenario listening to tags, so test for loops with Run once.
Ontraport10

Untag Objects

Action

In MakeRemoves tags from objects.

Untag Objects strips tags from records, which keeps your segments accurate once a status no longer applies.

When to use it
a trial ends, a refund is issued or an event is cancelled, and the matching tag should come off.
Watch out
Watch Events listens to untagging, so a scenario watching it will probably react too; check with Run once that nothing fires by surprise.
Ontraport11

Update a Message

Action

In MakeUpdates a message.

Update a Message edits an existing Ontraport message, so a correction made in your source content reaches the copy people receive.

When to use it
an offer, a date or a link changes in your content tool and the stored message must follow.
Watch out
it edits the message you point to, so double-check which one before running, or you change the wrong copy people receive.
Ontraport12

Update an Object

Action

In MakeUpdates an object.

Update an Object changes values on a record that already exists, so Ontraport reflects what happened in your other tools.

When to use it
a deal moves in your pipeline tool or a customer edits their details in a portal, and the CRM record should match.
Watch out
it needs the record identifier; pair it with Get an Object or Search Objects when the trigger does not supply one.
Ontraport13

Update a Rule

Action

In MakeUpdates a rule.

Update a Rule adjusts a rule already living in Ontraport, keeping its logic aligned with how your process works today.

When to use it
an offer changes and the rules tied to it must be edited in one pass instead of by hand in each place.
Watch out
review the edited rule in Ontraport after a Run once test, before activating the scenario.
Ontraport14

List Objects With Tag

Search

In MakeRetrieves all objects with a certain tag.

List Objects With Tag gives you every Ontraport record carrying a chosen tag, each one passed to the next module as its own bundle.

When to use it
you want to export a tagged segment to a spreadsheet or an ad audience before a launch.
Watch out
a search can return zero, one or many records, and each module after it runs once per record, which adds operations on your plan.
Ontraport15

Search Objects

Search

In MakeRetrieves all objects of a certain type.

Search Objects returns all the Ontraport records of one type, each passed on as its own bundle, so you can work through a whole list in one run.

When to use it
you want every record of one type copied to a spreadsheet or reviewed during a clean-up.
Watch out
the result may be empty or hold several records, and the next modules run once per record, so plan for each case.
Need help

Need help automating Ontraport with Make?

A person reads every message.

FAQ

Ontraport and Make: common questions

01Is the Ontraport Make integration free?
Yes, on the Make side. Ontraport is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. Your Ontraport subscription is separate and billed by Ontraport, so check its own pricing page for what your account includes.
02What do you need to connect Ontraport to Make?
You need an active Ontraport account plus an API Key and an App ID, both created in Ontraport under Administration, Integrations, then Ontraport API Instructions and Key Manager. Ontraport may first ask you to submit an API Application form and wait for approval. In Make, add an Ontraport module, click Create a connection and paste the credentials. For the instant Watch Events module, create the webhook first, then the connection.
03Does the Ontraport trigger in Make fire in real time?
Yes. Watch Events is an instant trigger: Ontraport calls Make through a webhook as soon as an object is created, tagged or untagged, or a form is submitted. You do not wait for a polling interval as you would with a scheduled trigger. It is the only Ontraport trigger in Make, so any other starting point, such as an event in another app, comes from that other app's module placed first in the scenario.
04What if the Ontraport module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Ontraport API with the connection you already have, so actions the 15 listed modules do not cover stay within reach. You write the request following the Ontraport API documentation. Also note that Make labels its Ontraport doc page as AI-generated from the vendor documentation, so confirm any important detail with Ontraport before relying on it. Test each call with Run once before switching the scenario on.
05Should you use Make or n8n for Ontraport?
It depends on what you need to build. In Make, Ontraport comes with 16 modules, an instant trigger and a generic API module, and you assemble scenarios visually. Many apps also have an n8n node, but this page does not document one for Ontraport, so check that first. Pick the tool whose modules cover your actual workflow, then compare the two editors side by side on a small test before committing.