Resources · Make integration

Xama Onboarding Make integrationAutomate Xama Onboarding with Make.

Can Make take the repetitive clicks out of Xama Onboarding? It can: the Xama Onboarding Make integration offers 39 modules (38 actions, 1 search) for teams that open client files and order reports. Below, you link your account and build a first scenario.

Try the Xama Onboarding integration on MakeSee the 39 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Xama Onboarding Make integration do for you?

The Xama Onboarding Make integration links your Xama Onboarding account to Make, where you build a scenario (the automation itself) out of modules, each module being one brick such as an action or a search. Another app supplies the data, and the Xama Onboarding modules create clients, send onboarding requests or fetch reports.

New client, file opened. When a deal is won in your CRM, Create a Hub Client adds the client to Xama Onboarding and Send Onboarding Request follows right after. Nobody retypes the company name.

Reports that land where the team works. Retrieve an AML Report or Retrieve a Company Report hands an existing report to the next module, which can file it in a shared drive or post a note in a chat tool.

A clean exit. When a contract ends in your billing tool, Offboard Hub Client is the module named for that step on the Xama side, instead of waiting for someone to remember.

Know the limits before you start. The Make documentation for Xama Onboarding is flagged as limited, because little public information exists about the app, and no module is described in detail. The app has no trigger either, so a scenario starts from another app or from its schedule. New to the tool? The Make review covers the basics, and n8n vs Make helps if you are weighing both platforms.

Connect

How do you connect Xama Onboarding to Make?

  1. 01

    Add a Xama Onboarding module

    Open a scenario, click the + and search for Xama Onboarding. Pick a module, for example Create a Hub Client, then click Create a connection. A connection is your Xama Onboarding account linked to Make once, then reused by every module of the app.

  2. 02

    Name the connection

    Make offers a name field, and filling it is optional. A clear label, such as the entity or the account owner, still pays off the day you add a second Xama Onboarding account and have to pick the right one from a list.

  3. 03

    Authorize and save

    Depending on what the app supports, Make either opens a page where you approve the access, or asks you to paste a key issued by Xama Onboarding. Finish with Save and the connection shows up in the module.

First scenario

Your first scenario with Xama Onboarding

GoalWhen a deal is won in your CRM, Make creates the client in Xama Onboarding and sends the onboarding request.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Search for the app where you track deals and choose its trigger for a won deal.

  2. 02

    Connect and set the trigger

    Click Create a connection for that app, then fill in the trigger. Once the account is linked, Make lists the objects it can read, so you pick from a list instead of typing.

  3. 03

    Add Create a Hub Client

    Click the + on the right of the trigger and add Create a Hub Client from Xama Onboarding. Map the company details from the previous module into the fields Make shows you.

  4. 04

    Add Send Onboarding Request

    Add Send Onboarding Request right after and map what the earlier modules produced. The documentation does not list its fields, so read them in the editor before filling anything.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario a single time; open each module to read the bundles it received, a bundle being one item passed along, here one client.

  6. 06

    Schedule it and switch it on

    Set the schedule on the first module (the clock, every 15 minutes by default), then switch the scenario on. On the Free plan, 15 minutes is also the shortest interval allowed.

Modules

What each Xama Onboarding module does

Xama Onboarding gives you 39 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Xama Onboarding1

AML Check Updated

ActionIn the docs only

Keeps the AML side of a client file in step with the rest of your process. Its name sounds like an event, yet the only list available files it under actions, a type guessed from the name, and the documentation adds nothing.

When to use it
right after a step where a compliance officer's decision on a client has been recorded in another tool.
Watch out
open the module and read its fields in the editor before you map anything, since none of them are documented.
Xama Onboarding2

Client Created

ActionIn the docs only

Gives your scenario a step named after a new client in the Hub. The list files it under actions, a type guessed from its name, so check in the editor whether it shows the clock or lightning badge of a trigger.

When to use it
when an earlier module already knows about a new client and the Xama side should reflect it.
Watch out
click Run once and look at the bundle it returns before you build more steps on top of it.
Xama Onboarding3

Client Deleted

ActionIn the docs only

Ties a scenario to the removal of a client from the Hub, at least by its name. What it does exactly is undocumented, and anything labelled deleted deserves caution.

When to use it
in a cleanup flow, once another tool has already marked a client as gone.
Watch out
test it on a dummy client first, because a deletion does not come back.
Xama Onboarding4

Client Updated

ActionIn the docs only

Brings changes made to a Hub client within reach of your scenario, judging by the name. Like its neighbours, it is listed as an action, a type guessed from the name alone.

When to use it
when a new address or a new legal name entered in your CRM should echo in Xama Onboarding.
Watch out
compare it with Retrieve a Hub Client in the editor; the undocumented fields decide which one fits your case.
Xama Onboarding5

Company Report Updated

ActionIn the docs only

Points a scenario at a company report that has changed, going by the module name alone. Nothing in the documentation explains what comes out of it.

When to use it
when the analyst who reads those reports should hear about a refresh by email or in a chat channel.
Watch out
read the bundle after Run once before you send anything to people.
Xama Onboarding6

Contact Created

ActionIn the docs only

Lets your scenario deal with a newly added contact, the person attached to a client in the Hub. It is listed as an action, going by its name, so plan it after another module and confirm its badge in the editor.

When to use it
when a sales assistant adds a signatory in another tool and the Hub should hear about it too.
Watch out
check whether Create a Hub Contact is what you actually need, as the two names are close.
Xama Onboarding7

Contact Deleted

ActionIn the docs only

Handles a contact removed from the Hub, according to its label, which is the only clue available. For a deletion, the lack of documentation is a good reason to go slowly.

When to use it
when someone leaves a client company and the change must follow in Xama Onboarding.
Watch out
compare it with Delete a Hub Contact before choosing, and test on a spare record.
Xama Onboarding8

Contact Updated

ActionIn the docs only

Keeps a contact's changes in view of your scenario, which is what its name promises. No field list exists in the documentation, so the editor is your only guide to what it expects.

When to use it
after a phone number or an email changes in your CRM and the copy in the Hub should match.
Watch out
Update a Hub Contact may suit you better if you want to write the change yourself.
Xama Onboarding9

Create a Company Report

ActionIn the docs only

Orders a company report from Xama Onboarding without anyone opening the app, if the name reflects what it does. The report then becomes something your scenario can pass along.

When to use it
as soon as a new business client appears in your CRM and the due diligence team wants the report.
Watch out
check in the editor which company details it needs, since the documentation lists none.
Xama Onboarding10

Create a Hub Client

ActionIn the docs only

Adds a client to the Xama Onboarding Hub from data another app already holds, so nobody types it twice. In an intake flow, it is usually the first Xama step to place.

When to use it
when a deal closes or a signup form comes in and the client file should exist right away.
Watch out
map the details from the previous module, then click Run once to see which values Make accepts.
Xama Onboarding11

Create a Hub Contact

ActionIn the docs only

Creates a person in the Hub, for example a director or a signatory linked to a client. That spares you the manual entry that tends to follow each new file.

When to use it
right after Create a Hub Client, when the form also carried details about the people behind the company.
Watch out
the documentation gives no field names, so read them in the module before mapping.
Xama Onboarding12

Create an AML Report

ActionIn the docs only

Produces an AML report inside Xama Onboarding from your scenario, going by its name, so the check no longer depends on someone remembering it.

When to use it
when a client reaches the stage where your compliance process requires the report.
Watch out
look at how it differs from Initiate an AML Check in the editor; the documentation explains neither of them.
Xama Onboarding13

Create an Onboarding Report

ActionIn the docs only

Generates an onboarding report for a client, if the label is accurate, and gives the next module a document to work with. Only its name documents it.

When to use it
once a client's onboarding is complete and a manager wants the report archived or shared.
Watch out
add Retrieve an Onboarding Report afterwards if a later step needs the content of the report.
Xama Onboarding14

Delete Report

ActionIn the docs only

Removes a report, as its name says, which makes it the module to reach for when an outdated or mistaken report should disappear from Xama Onboarding.

When to use it
in a correction flow started by a change made in another tool.
Watch out
a deletion cannot be undone, and the documentation does not say which reports it can reach, so try it on a spare one.
Xama Onboarding15

Delete a Hub Client

ActionIn the docs only

Erases a client from the Hub straight from a scenario. Pick it when the record itself must go, not when the business relationship simply comes to an end.

When to use it
when a client was created by mistake or duplicated during an import.
Watch out
for a client who leaves, Offboard Hub Client matches the situation better by its name, and no undo exists after a deletion.
Xama Onboarding16

Delete a Hub Contact

ActionIn the docs only

Takes a person off the Hub, for example a contact entered twice, without you opening Xama Onboarding at all.

When to use it
after a deduplication step in your CRM has flagged the extra record.
Watch out
Contact Deleted has a very close name, so compare both in the editor and test on a spare contact first.
Xama Onboarding17

Initiate an AML Check

ActionIn the docs only

Starts an AML check on a client from Make, as the name states, so screening begins as soon as the file is ready rather than whenever someone gets to it.

When to use it
right after Create a Hub Client, in an intake flow for clients that must be screened.
Watch out
the documentation says nothing about when or how results come back, so plan a separate step to retrieve them.
Xama Onboarding18

Make a Connect API Call

ActionIn the docs only

Sends your own request to what its name calls the Connect API of Xama Onboarding, a way out when no ready module covers what you need.

When to use it
when someone on your team knows the exact request to send and the other modules fall short.
Watch out
the documentation describes neither the endpoints nor the expected format, so test with Run once before any real data goes through.
Xama Onboarding19

Make a Hub API Call

ActionIn the docs only

Opens a direct line to the Hub side of Xama Onboarding, judging by its name, for requests that the Hub modules of the list do not cover.

When to use it
if you need a Hub operation missing from the list, such as a detail none of the Retrieve modules returns.
Watch out
unlike Make a Connect API Call, its name points to the Hub, so check which one matches your request before building.
Xama Onboarding20

Offboard Hub Client

ActionIn the docs only

Handles the exit of a client from the Hub, which is what offboarding means, without you deleting anything by hand. It gives the end of a relationship its own clean step.

When to use it
when a contract ends in your billing tool or your CRM.
Watch out
the documentation does not say whether it keeps or removes data; for a pure deletion, Delete a Hub Client exists.
Xama Onboarding21

Onboarding Request Updated

ActionIn the docs only

Relates your scenario to a change in an onboarding request, going by its name. That helps an account team following several requests at the same time.

When to use it
after Send Onboarding Request, when the account manager wants the status mirrored in another tool.
Watch out
its type is only guessed from the name, so check its badge in the editor; Retrieve an Onboarding Request may fit better.
Xama Onboarding22

Report Updated

ActionIn the docs only

Deals with a report that has changed, under a generic label that may cover several kinds of report. Only its name describes it, so treat it as a module to explore.

When to use it
when a refreshed report should reach the reviewer in charge of that client.
Watch out
Company Report Updated is more specific, so start there if company reports are all you follow.
Xama Onboarding23

Reset Onboarding Stages

ActionIn the docs only

Sends a client's onboarding back to its starting stages, going by the name, so a file can be redone without manual steps inside Xama Onboarding.

When to use it
when a client submitted the wrong documents and must go through the process again.
Watch out
what happens to stages already completed is not documented, so test on a dummy client first.
Xama Onboarding24

Retrieve a Company Report

ActionIn the docs only

Fetches an existing company report so the next module can file it, share it or read from it. It works on one report at a time.

When to use it
after Create a Company Report, or when a colleague asks for the latest report on a given client.
Watch out
to locate the client first, place Search Hub Clients and Contacts before it.
Xama Onboarding25

Retrieve a Hub AML Report

ActionIn the docs only

Pulls the AML report stored in the Hub for a client, handy when compliance needs that file outside Xama Onboarding.

When to use it
when an auditor or a banking partner asks for proof of screening and the report should land in a shared folder.
Watch out
Retrieve an AML Report also exists, so check in the editor which of the two reads from the place you use.
Xama Onboarding26

Retrieve a Hub Client

ActionIn the docs only

Reads one client record from the Hub, so later modules can reuse its details without anyone copying them by hand.

When to use it
before updating a record in another tool, when you need the current values held in Xama Onboarding.
Watch out
it works on a single client; to look one up, run Search Hub Clients and Contacts before it.
Xama Onboarding27

Retrieve a Hub Company report

ActionIn the docs only

Gets the company report kept in the Hub, as opposed to the one Retrieve a Company Report reads, if the names reflect that split. Few modules of this app deserve a side by side test more.

When to use it
when the Hub is where your team stores the reports of existing clients.
Watch out
run both modules with Run once and keep the one whose bundle holds what you need.
Xama Onboarding28

Retrieve a Hub Contact

ActionIn the docs only

Loads a person's record from the Hub, so a scenario can remind, notify or check that contact with current data.

When to use it
when a message sent from another tool must reach the right person at a client company.
Watch out
one contact per run; if you start from a list, a search module has to come first.
Xama Onboarding29

Retrieve a Hub Risk Assessment

ActionIn the docs only

Brings a client's risk assessment out of the Hub and into your scenario, where it can feed a report or an alert.

When to use it
when a risk manager wants the assessment next to the rest of the client file in another tool.
Watch out
the documentation gives no detail on the returned fields, so read the bundle after a test run.
Xama Onboarding30

Retrieve an AML Report

ActionIn the docs only

Collects an AML report so it can travel to wherever your team reviews compliance, as its name suggests.

When to use it
right after Create an AML Report, to archive the result with the client file.
Watch out
what the bundle contains is not described anywhere, so inspect it in the editor before mapping.
Xama Onboarding31

Retrieve an Onboarding Report

ActionIn the docs only

Hands the next module an onboarding report, the document that sums up a client's onboarding if the name is accurate.

When to use it
when a relationship manager wants each finished report attached to the client record in your CRM.
Watch out
it acts on one report at a time, so plan one run per client.
Xama Onboarding32

Retrieve an Onboarding Request

ActionIn the docs only

Reads the current state of an onboarding request, useful when you need to know where a client stands before acting.

When to use it
before a reminder email goes out, to avoid chasing a client who already replied.
Watch out
the fields it returns are undocumented, so look at them in the editor first.
Xama Onboarding33

Risk Assessment Deleted

ActionIn the docs only

Links a scenario to a risk assessment that has been removed, according to its name. It is listed as an action, a type guessed from the name, and no documentation stands behind it.

When to use it
when a removed assessment should be logged in your compliance register for traceability.
Watch out
treat its output with care until a Run once has shown you the bundle.
Xama Onboarding34

Risk Assessment Status Change

ActionIn the docs only

Concerns a risk assessment whose status moves, by its name, and gives your scenario a step built around that change.

When to use it
when a new status should warn the account owner by email or in a chat channel.
Watch out
its type is guessed from the name; if the editor shows no clock or lightning badge, pair it with another app's trigger or the schedule.
Xama Onboarding35

Search Hub Clients and Contacts

SearchIn the docs only

Finds clients and contacts in the Hub, and it is the only search module of the app. A search can return zero, one or several bundles, one per match.

When to use it
when you need to locate a record before a Retrieve or Update module acts on it.
Watch out
with several matches, the following modules run once per bundle, and each run counts as operations on your plan.
Xama Onboarding36

Send Onboarding Request

ActionIn the docs only

Sends a client the onboarding request from Xama Onboarding, which starts their side of the process without you opening the app.

When to use it
right after Create a Hub Client, when a new deal or signup should turn into a request at once.
Watch out
test with a dummy client first, since the documentation does not describe what the client receives.
Xama Onboarding37

Trigger a Report lookup

ActionIn the docs only

Starts a report lookup; despite the word trigger in its name, Make lists it as an action, placed after other modules.

When to use it
when a client's details changed and you want fresh report data fetched for that client.
Watch out
the documentation does not say what the lookup returns, so test it before adding a Retrieve module after it.
Xama Onboarding38

Update a Hub Client's Type

ActionIn the docs only

Changes the type of a client in the Hub, a narrow edit that leaves the rest of the record alone.

When to use it
when a client's category changes after a review carried out in another tool.
Watch out
the accepted types are not documented, so pick them from what Make lists in the module.
Xama Onboarding39

Update a Hub Contact

ActionIn the docs only

Writes changes to a contact in the Hub, so the person's details stay in line with your CRM.

When to use it
after someone's role or email changes in the tool your sales team uses.
Watch out
it acts on one contact already known, so pair it with Search Hub Clients and Contacts to find that contact first.
Need help

Need help automating Xama Onboarding with Make?

A person reads every message.

FAQ

Xama Onboarding and Make: common questions

01Is the Xama Onboarding Make integration free?
Yes, Xama Onboarding is a standard app, so it works on the Make Free plan. That plan comes with limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, 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, an operation being one module run on one bundle. What Xama Onboarding itself charges is outside the scope of this page.
02What do you need to connect Xama Onboarding to Make?
You need a Make account and a Xama Onboarding account able to authorize Make. The official documentation lists no specific prerequisite, so the generic Make flow applies: add a Xama Onboarding module, click Create a connection, name it if you wish, then approve access on the app's page or paste the key the app gives you, and click Save. That one connection then serves all 39 modules. If the app asks for something Make does not show, check your account settings on the Xama side, since the documentation stays limited.
03Does the Xama Onboarding Make integration trigger scenarios in real time?
No, because the app has no trigger module at all, neither scheduled nor instant. A scheduled trigger is one Make checks at the interval you set; an instant trigger is one the app calls through a webhook the moment something happens. To start a scenario anyway, open it with a trigger from another app, such as your CRM or a form tool, or let it run on its schedule, every 15 minutes by default, with a Xama Onboarding module such as Search Hub Clients and Contacts in first position.
04What if a Xama Onboarding module is missing in Make?
It depends on the gap. Make offers no universal Make an API Call module for this app. The list does include Make a Connect API Call and Make a Hub API Call, whose names point to direct requests to Xama Onboarding, but the documentation describes neither, so test them with Run once before relying on them. When that is not enough, another app may cover the step, or a Make agency can look at the case with you and suggest a workaround.
05Is Make or n8n better for Xama Onboarding?
It depends on your criteria rather than on a winner. On Make, Xama Onboarding comes with 39 ready modules in a visual editor and runs on the Free plan within its limits. Many apps also have an n8n node, but nothing here confirms one for Xama Onboarding, so check that first. Then compare the operations you need, the way your team likes to build, and the tool that already runs your other automations. Neither choice is wrong in general.
Same platform

Other docs you might need on this stack.

Browse all integrations