Resources · Make integration

Outseta Make integrationAutomate Outseta with Make.

What if every new Outseta account opened its own deal without anyone typing it? The Outseta Make integration gives you 29 modules, 9 of them instant triggers. This guide shows SaaS founders and ops leads how to connect Outseta and ship a first working scenario.

Try the Outseta integration on MakeSee the 29 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Outseta Make integration do for you?

The Outseta Make integration links your Outseta account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates, reads or searches something. Outseta brings 29 of those bricks for accounts, people, deals, activities and chats, so events in your membership business can start work in other tools.

Turn every signup into a sales follow-up. Put Watch Account Created at the start, add Create a Deal behind it, and each new customer account lands in your pipeline with the account data already mapped in.

Keep a clean history on each contact. When something happens in another app, such as a support ticket or a demo booking, Create a Custom Activity writes it on the person's timeline in Outseta, so the account owner sees the whole story in one place.

Answer chats faster. Watch New Chat hands each incoming conversation to Make the moment it arrives; from there you can alert the right teammate in the tool your team already reads.

What Make does not give you here: the documentation lists no module groups and no limits specific to Outseta, and anything outside the listed modules goes through Make an API Call. If you are new to the editor, the Make training walks through the basics, and Make pricing explains what each plan allows. The same app may also exist on n8n; the n8n vs Make comparison helps you pick a tool.

Connect

How do you connect Outseta to Make?

  1. 01

    Generate an API key in Outseta

    In Outseta, open Settings, then Integrations and API Keys. Create a new key, give it a name you will recognize, and generate it. Outseta shows an API key and a client secret: copy both before closing the screen.

  2. 02

    Add an Outseta module in Make

    In your scenario, search for Outseta, pick a module and click Create a connection. A connection is your Outseta account linked to Make once and reused by every Outseta module. The Connection name field is optional.

  3. 03

    Paste the credentials and save

    Paste the API key and the client secret you copied, then confirm. Make now lists what it can read in your Outseta account, and every other Outseta module in the scenario can pick this same connection from a dropdown.

First scenario

Build your first Outseta scenario in Make

GoalWhen a new account is created in Outseta, Make opens a matching deal in your Outseta pipeline.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. Search for Outseta and choose Watch Account Created.

  2. 02

    Set up the webhook and the connection

    Click Create a webhook, then Create a connection, and paste your API key and client secret. From now on, Outseta calls Make each time an account is created.

  3. 03

    Add Create a Deal

    Click the + on the right of the trigger and pick Create a Deal. Map the account data coming from the first module into the deal fields, so each bundle (one new account) becomes one deal.

  4. 04

    Test with Run once

    Click Run once, then create a test account in Outseta. Make catches it and shows the bundle each module received. Check the new deal in Outseta before going further.

  5. 05

    Switch the scenario on

    Save, then turn the scenario on. Since the trigger is instant, there is no interval to pick: each new account starts the run as soon as Outseta sends it.

Triggers

Outseta triggers: what can start a scenario?

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

Outseta1Watch Account Created

Watch Account Created

Instant trigger

In Make“Triggers when a new account has been created.”

Starts your scenario each time a customer account appears in Outseta, carrying that account's data into the next modules so you can welcome it, log it elsewhere or open a deal for it.

How it fires
instant, Outseta calls Make through a webhook as soon as the account exists.
When to use it
when a signup should set off onboarding work, like a deal for the sales team or a row in a shared tracker.
Watch out
the webhook has to be created in the module before the connection, or the trigger never receives anything.
Outseta2Watch Account Deleted

Watch Account Deleted

Instant trigger

In Make“Triggers when an account has been deleted.”

Tells your scenario that an account is gone from Outseta, which gives you a chance to tidy up the other tools that still hold that customer.

How it fires
instant, the removal reaches Make through a webhook right away.
When to use it
when a closed customer should also disappear from a mailing tool, a spreadsheet or a billing report kept outside Outseta.
Watch out
use the data the trigger sends to find the customer in your other tools, and test the scenario on a throwaway account before pointing it at real ones.
Outseta3Watch Account Updated

Watch Account Updated

Instant trigger

In Make“Triggers when an account has been updated.”

Sends Make the new state of an account whenever someone changes it in Outseta, so the copies of that account in your other tools never drift.

How it fires
instant, Outseta pushes each change to Make by webhook.
When to use it
when a CRM, a data table or a dashboard outside Outseta mirrors your accounts and must follow every edit.
Watch out
an Update an Account placed later in the same scenario changes the account again, which can fire this trigger once more; add a filter so the scenario does not feed itself.
Outseta4Watch Deal Created

Watch Deal Created

Instant trigger

In Make“Triggers when a new deal has been created.”

Brings every new Outseta deal into Make at the moment it is opened, ready to be announced, copied or enriched by the modules you place after it.

How it fires
instant, Outseta sends the new deal through a webhook.
When to use it
when the sales team wants a message in its chat tool for each opportunity, or a line in a forecast sheet.
Watch out
if another scenario already creates deals with Create a Deal, those deals start this trigger too; decide which scenario should react before switching both on.
Outseta5Watch Deal Updated

Watch Deal Updated

Instant trigger

In Make“Triggers when a new deal has been updated.”

Follows your pipeline for you: each time a deal changes in Outseta, Make receives the updated deal and can act on its new state.

How it fires
instant, every edit reaches Make by webhook as soon as it is saved.
When to use it
when a deal moving forward should kick off a task elsewhere, such as preparing a contract or notifying finance.
Watch out
every edit fires it, not only the ones that matter to you, so add a filter after the trigger to keep only the updates you care about.
Outseta6Watch New Chat

Watch New Chat

Instant trigger

In Make“Triggers when a new chat has been received.”

Hands each chat your visitors start in Outseta to Make, so a conversation no longer waits for someone to open the inbox.

How it fires
instant, Outseta calls Make through a webhook when the chat arrives.
When to use it
when support is spread across a small team and each new conversation should ping the person on duty, or be logged in a ticket tool.
Watch out
like every Outseta trigger, it needs its webhook created in the module first, then the connection, or no chat ever reaches the scenario.
Outseta7Watch Person Created

Watch Person Created

Instant trigger

In Make“Triggers when a new person has been created.”

Catches every new person record in Outseta and passes it to Make with its details, so a contact never sits in one tool only.

How it fires
instant, the new person reaches Make through a webhook without delay.
When to use it
when a new member or lead should also land in your email platform, your help desk or a spreadsheet the marketing team uses.
Watch out
a person is not an account; if your logic is about companies that sign up, Watch Account Created is the better starting point.
Outseta8Watch Person Deleted

Watch Person Deleted

Instant trigger

In Make“Triggers when a new person has been deleted.”

Lets your scenario know that a contact was removed from Outseta, which is the signal to erase or archive that person everywhere else.

How it fires
instant, Outseta notifies Make by webhook the moment the person is deleted.
When to use it
when a data removal request has to be applied across several tools, not only in Outseta.
Watch out
match the contact in the other tools with the data this trigger sends, and check the match with Run once before switching the scenario on.
Outseta9Watch Person Updated

Watch Person Updated

Instant trigger

In Make“Triggers when a new person has been updated.”

Keeps every copy of a contact in step with Outseta: when someone edits a person, Make receives the fresh version and can push it where it is needed.

How it fires
instant, the change travels to Make by webhook as soon as it is saved.
When to use it
when a contact detail changed in Outseta must follow in your newsletter tool or CRM.
Watch out
pairing it with Update a Person in the same scenario can create a loop, since that update may fire the trigger again; filter the bundles first.
Modules

What can Make do in Outseta?

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

Outseta1

Cancel an Account

Action

In Make“Cancels an existing account.”

Ends an existing customer account from a scenario, which saves you a trip into Outseta each time a customer asks to stop.

When to use it
when a cancellation request comes from a form or a support tool and should be applied without manual work.
Watch out
cancelling and deleting are two separate modules; try both on a test account to see which result fits your process.
Outseta2

Create a Custom Activity

Action

In Make“Creates a custom activity.”

Writes your own event on an Outseta record, so the history of a customer also shows what happened in other tools.

When to use it
when a demo booked, a ticket closed or a document signed elsewhere should appear on the timeline the account owner reads.
Watch out
run Create a Custom Activity once with Run once and check the result in Outseta before switching the scenario on.
Outseta3

Create a Deal

Action

In Make“Creates a new deal.”

Opens a new opportunity in your Outseta pipeline from any event Make receives, with the details mapped from earlier modules.

When to use it
when a signup, a quote request or a booked call should become a deal the sales team can follow.
Watch out
if Watch Deal Created runs in another active scenario, each deal made here starts that scenario as well.
Outseta4

Create an Account

Action

In Make“Creates a new account.”

Adds a new customer account in Outseta from data collected somewhere else, so no one has to retype the customer's details.

When to use it
when a customer signs a contract or pays in another tool and must exist in Outseta right after.
Watch out
run List Accounts first to check the account is not already there, or duplicates build up quickly.
Outseta5

Create a Person

Action

In Make“Creates a new person.”

Records a new contact in Outseta straight from a form, a spreadsheet row or another CRM, with the fields you map from the previous module.

When to use it
leads that sign up on an event page, which Outseta never sees.
Watch out
List People placed before it tells you whether the contact exists already, which avoids two records for one person.
Outseta6

Delete a Deal

Action

In Make“Deletes a deal.”

Removes a deal from your Outseta pipeline when a scenario decides it no longer has a reason to be there.

When to use it
when test deals or duplicates created by an automation need cleaning up after a check.
Watch out
treat the deletion as final and try it on a test deal first; a wrong filter upstream could remove real opportunities.
Outseta7

Delete an Account

Action

In Make“Deletes an account.”

Erases a customer account in Outseta from a scenario, useful when a removal decided in another tool must also happen here, without anyone logging in to do it.

When to use it
when a data deletion request has been validated and the account has to go from every tool.
Watch out
this is not the same as Cancel an Account; if you only want to end a subscription, test the cancel module first.
Outseta8

Delete a Person

Action

In Make“Deletes a person.”

Takes a contact out of Outseta when a scenario tells it to, so a removal made in one place does not stay half done.

When to use it
when someone asks to have their data erased and the request arrives through a form or a support tool.
Watch out
map the right person identifier from a List People search; deleting from a loose match can hit the wrong contact.
Outseta9

Get a Deal

Action

In Make“Retrieves a deal.”

Reads one deal in full when you already know which one you need, so later modules can reuse what it holds.

When to use it
after a trigger or a search that only passed along the deal identifier, before writing a report or a message.
Watch out
it returns a single deal; to find several, List Deals is the right module.
Outseta10

Get an Account

Action

In Make“Retrieves an account.”

Fetches the complete record of one Outseta account, handy when an earlier step only knows who the customer is, not the details.

When to use it
when a new deal or a chat is linked to an account and you need that account's data before acting.
Watch out
it needs the account identifier; if you do not have it yet, start with List Accounts.
Outseta11

Get a Person

Action

In Make“Retrieves a person.”

Pulls every detail Outseta holds on one contact, so the next module works with complete data instead of a bare identifier.

When to use it
when an activity or a chat points to someone and your message needs that person's details.
Watch out
you need the person's identifier; without it, run List People instead.
Outseta12

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Outseta API from your scenario, reusing the same connection, when the ready-made modules stop short of what you need.

When to use it
when an object or an operation of Outseta has no dedicated module in this list.
Watch out
you write the request yourself, so keep the Outseta API documentation open while you set the path and the body.
Outseta13

Subscribe a Person to the List

Action

In Make“Subscribes a person to the existing list.”

Signs a contact up to one of your Outseta lists from a scenario, so opt-ins collected in other tools reach your emails.

When to use it
when someone ticks a newsletter box on a form or a webinar page outside Outseta.
Watch out
the list has to exist in Outseta beforehand; this module adds people to it, it does not create one.
Outseta14

Update a Deal

Action

In Make“Updates a deal.”

Changes an existing Outseta deal from outside, so the pipeline reflects what just happened in your other tools.

When to use it
when a signed proposal or a paid invoice elsewhere should move the matching deal forward.
Watch out
an active scenario built on Watch Deal Updated can fire for each change made here; add a filter to avoid a loop.
Outseta15

Update an Account

Action

In Make“Updates an account.”

Edits a customer account in Outseta with data coming from another system, which keeps the account up to date without copy and paste.

When to use it
when a customer detail is first entered in a billing or support tool.
Watch out
find the right account with List Accounts or Get an Account before writing, so the change lands on the correct record.
Outseta16

Update a Person

Action

In Make“Updates a person.”

Refreshes a contact in Outseta when their details change in another app, so your team always works from current data.

When to use it
when a contact edits their profile in a help desk or a community tool that is not Outseta.
Watch out
combined with Watch Person Updated in the same scenario, every write starts a new run; filter to stop the loop.
Outseta17

List Accounts

Search

In Make“Retrieves a list of accounts.”

Returns the Outseta accounts that match your criteria, each one as a separate bundle the next modules process one after the other.

When to use it
before creating an account, to check it is not already there, or to build a list for a report.
Watch out
a search can return zero, one or many bundles; plan what the scenario does when nothing is found.
Outseta18

List Deals

Search

In Make“Retrieves a list of deals.”

Gathers the deals in your Outseta pipeline so you can export, sum up or review them in another tool.

When to use it
when a manager wants a view of open opportunities in a spreadsheet or a dashboard built outside Outseta.
Watch out
each deal found becomes one bundle, and every module after the search runs once per deal, which counts operations on your plan.
Outseta19

List People

Search

In Make“Retrieves a list of people.”

Finds the contacts stored in Outseta, which is often the first step before updating, subscribing or deleting a person.

When to use it
when you hold a contact from another app and need the matching Outseta record.
Watch out
when several people match, every one of them flows to the next module; tighten your criteria before an update or a deletion.
Outseta20

Search Activities

Search

In Make“Searches for activities or lists them all.”

Looks through the activities recorded in Outseta, or lists them all, so you can reuse the history of your customers elsewhere.

When to use it
when you want to count or export the custom activities your scenarios wrote with Create a Custom Activity.
Watch out
without any criteria it returns every activity, and each one uses an operation in the modules that follow.
Need help

Need help automating Outseta with Make?

A person reads every message.

FAQ

Outseta and Make: frequent questions

01Is the Outseta Make integration free?
Yes, Outseta is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Every Outseta trigger is instant, so the interval matters less here than for apps that are polled. Paid plans (Core, Pro, Teams and Enterprise) lift the scenario cap, allow 40 minutes of execution and count usage in credits. You still need your own Outseta subscription, which is separate from Make.
02What do you need to connect Outseta to Make?
You need an active Outseta account and an API key with its client secret. In Outseta, go to Settings, then Integrations, then API Keys, create a key and copy both values shown on screen. In Make, add any Outseta module, click Create a connection and paste them. The connection name is optional. For a trigger, click Create a webhook first, then create the connection in the same window. Once saved, every other Outseta module in your scenarios reuses that connection.
03Do Outseta triggers in Make react in real time?
Yes. All 9 Outseta triggers are instant: Outseta calls Make through a webhook as soon as an account, a deal or a person is created, updated or deleted, or when a new chat arrives. Make does not poll Outseta on a clock for these modules, so there is no 15 minute schedule to wait for. What you do have to watch is loops: a scenario that updates a record it also watches can fire itself again, so add a filter after the trigger.
04What if an Outseta module is missing in Make?
It depends on what you need, but Make an API Call usually covers it. That module reaches any endpoint of the Outseta API using the connection you already made, so objects or operations without a dedicated module stay within reach. You write the request yourself, with the Outseta API documentation at hand. Make also flags its Outseta documentation as AI-generated from the vendor's docs, so when a detail matters, confirm it with Outseta directly before relying on it in production.
05Should you use Make or n8n for Outseta?
It depends on your criteria, not on a winner. In Make, Outseta brings 29 ready modules: 9 instant triggers, 16 actions and 4 searches, all usable from the Free plan, with a visual editor and a Run once button to test. n8n may also offer an Outseta node; check which Outseta objects each tool covers for your use case, which tool your team already knows, and how each one counts usage. The comparison linked higher on this page lays out the differences between the two tools in detail.
Same platform

Other docs you might need on this stack.

Browse all integrations