Automate BSI With Make: 3 Modules, No Code, Step by Step

What you can automate

What does the BSI Make integration let you automate?

The BSI Make integration links your BSI account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger or an action. With BSI you can watch CX data, add CX participants, and call the BSI API directly when those two are not enough.

Feed CX data to the rest of your stack. Put Watch CX Data at the start of a scenario and every new item it finds becomes a bundle, one item passed from module to module, that you can send to a spreadsheet, a chat channel or your CRM.

Add participants from another app. When a contact signs up through a form or closes a deal elsewhere, Create CX Participant registers that person in BSI, so nobody has to retype names by hand.

Reach what the listed modules skip. Make an API Call reuses the same connection to reach any endpoint of the BSI API, which covers requests the two ready-made modules do not handle.

Be aware of one limit: Make's own documentation for BSI is marked as limited, because there is not enough public information about the app. Expect to test each module with real data before trusting it. If you are new to the tool, our Make training covers the basics, and Make troubleshooting helps when a run fails. The same app may also exist as an n8n node; the n8n vs Make comparison lays out the differences between the two tools.

Connect

How do you connect your BSI account to Make?

01
Add a BSI module
In a scenario, add any BSI module and click Create a connection. A connection is your BSI account linked to Make once, then reused by every BSI module you add later, so you only do this step one time.
02
Name the connection
Give the connection a name if you like. It is optional, but a clear label such as the workspace or team it belongs to saves confusion later when several people share scenarios or when you link more than one BSI account.
03
Authorize and save
Either authorize Make on the BSI page that opens, or paste the key BSI gives you, depending on what the app asks for. Then click Save. The module can now read your BSI data and list what it finds.

First scenario

Build your first scenario with BSI

GoalWhen a new contact appears in another app, Make registers that person in BSI as a CX participant.

01
Create the scenario
Open the Scenarios page, create a new scenario and click the big + to place the first module on the empty canvas.
02
Start from your other app
Pick the app where new contacts show up first, such as your form or CRM tool, choose its trigger and connect that account.
03
Add Create CX Participant
Click the + on the right of that trigger, search for BSI, choose Create CX Participant and click Create a connection (or Add).
04
Map the contact data
Fill the BSI fields by mapping the values from the first module. Once connected, Make lists the BSI objects it can read, so you pick instead of typing.
05
Test with Run once
Click Run once. Make executes the scenario one time and shows the bundles each module received, so you can check the participant landed in BSI.
06
Schedule and switch on
Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. New contacts now reach BSI without you.

Triggers

What can start a BSI scenario?

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

BSI1Watch CX Data

Watch CX Data

triggerIn the docs only

Watch CX Data lets a scenario start on its own from your BSI customer experience records, so fresh data reaches other tools without anyone exporting it. Each new item arrives as a bundle the next modules can use.

How it fires

scheduled, Make checks the app on the scenario's schedule. This type is inferred from the module's name, so look for the clock badge on the module to confirm it.

When to use it

when your team wants new CX data copied into a report, a shared sheet or a chat channel as it shows up.

Watch out

Make's documentation gives no description of this module, so run it once and read the bundles before you build on specific fields.

Modules

What can Make do in BSI?

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

BSI1

Create CX Participant

ActionIn the docs only

Create CX Participant adds a person to BSI from data that lives in another app, which spares you from copying contacts over one by one. Each run acts on one bundle.

When to use it

right after a customer fills in a form or signs a contract in another tool, so they are ready for your CX follow-up.

Watch out

the documentation lists no fields for it, so check with Run once which values BSI requires.

BSI2

Make an API Call

ActionIn the docs only

Make an API Call gives you access to any endpoint of the BSI API through the connection you already set up, so you are not stuck when the two ready-made modules fall short.

When to use it

when you need to read or change something in BSI that neither Watch CX Data nor Create CX Participant covers.

Watch out

you write the request yourself, so keep the BSI API reference open while you set it up.

Need help

Need help automating BSI with Make?

A person reads every message.

FAQ

Common questions about BSI and Make

01Is the BSI Make integration free?

Yes, BSI is a standard app, so it works from the Make Free plan. That plan allows 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 (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one operation being one module running on one bundle.

02What do you need to connect BSI to Make?

A BSI account and a Make account are enough to begin. Make's documentation for BSI lists no prerequisite and no dedicated connection steps, so the generic flow applies: add a BSI module, click Create a connection, optionally name it, authorize Make on the BSI page or paste the key BSI provides, then click Save. The connection is created once and every BSI module in your scenarios reuses it afterwards. Nothing else is required on the Make side.

03Does the BSI trigger in Make react in real time?

No, Watch CX Data is treated as a scheduled trigger, a type inferred from its name: Make checks BSI on the scenario's schedule rather than being called the moment something changes. A new scenario runs every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval, while paid plans go down to 1 minute. The clock badge on the module in the editor confirms the type.

04What if a BSI module you need is missing in Make?

Use Make an API Call. It reaches any endpoint of the BSI API with the same connection, so you can cover requests that Watch CX Data and Create CX Participant do not handle. Keep in mind that Make marks its BSI documentation as limited, since little public information exists about the app. Test each request with Run once and check the bundles it returns before switching the scenario on, so a wrong request never runs unattended.

05Should you use Make or n8n for BSI?

It depends on which tool your team already runs. The same app often exists as an n8n node too, so check that both offer the modules you need before choosing. With Make, BSI comes with 1 scheduled trigger, 2 actions including Make an API Call, and works from the Free plan. Pick the platform where the rest of your automations already live, so connections and monitoring stay in one place.

Add a BSI module

Name the connection

Authorize and save

Create the scenario

Start from your other app

Add Create CX Participant

Map the contact data

Test with Run once

Schedule and switch on

Need help automating BSI with Make?