Resources · Make integration

Ksaar Make integrationAutomate Ksaar with Make.

Can Make react when a record lands in a Ksaar workflow? Yes. The Ksaar Make integration gives you 13 modules: 3 triggers, 7 actions and 3 searches. This page shows how to link your account, build a first scenario and pick the right module.

Try the Ksaar integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Ksaar Make integration do for you?

The Ksaar Make integration links your Ksaar application to Make, so records and users move between Ksaar and your other tools without code. You build a scenario, the automation Make runs for you, out of modules: one brick each, such as a trigger that watches Ksaar or an action that writes to it.

A follow-up record for every new request. Watch Records spots each record created in a workflow, and Create a Record opens the matching entry in a second workflow, so the next team never retypes anything.

A clean user base. Watch Users catches accounts that are created or changed. Pair it with Get a User or Update a User to fill in or correct the profile the moment the scenario sees it.

A report from the whole workflow. List Records returns every record of a workflow as separate bundles, one item each, ready to send to a spreadsheet or a summary email built with another app.

Know the limit before you start: Make itself says its documentation for Ksaar is incomplete, because little public information exists about the app. When a module is missing, Make an API Call reaches the rest of the Ksaar API with the same connection. Ksaar may also have an n8n node; the n8n vs Make comparison lays out the differences. If you are new to the editor, the Make training covers the basics, and Make troubleshooting helps when a run fails.

Connect

How do you connect Ksaar to Make?

  1. 01

    Add a Ksaar module

    In your scenario, click the + and search for Ksaar. Pick any module, then click Create a connection. The connection is your Ksaar account linked to Make once, and every Ksaar module reuses it afterward.

  2. 02

    Name the connection

    Give the connection a name you will recognize later, such as the name of the Ksaar application it opens. This step is optional, but it helps once you manage several accounts or a test and a live application.

  3. 03

    Authorize and save

    Authorize Make on the Ksaar page that opens, or paste the key Ksaar gives you if Make asks for one. Then click Save. Make can now read the workflows, records and users your account can reach.

First scenario

Your first scenario with Ksaar and Make

GoalWhen a record is created in a Ksaar workflow, Make creates a follow-up record in a second workflow.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the large + to add the first module. Everything you build next hangs off this first brick.

  2. 02

    Add Watch Records

    Search for Ksaar, choose Watch Records and pick the connection you made earlier. Once it exists, Make lists what it can read in Ksaar, so choose the workflow where new requests arrive.

  3. 03

    Chain Create a Record

    Click the + on the right of the trigger and add Create a Record. Point it at the second workflow, then map the values coming from the new record into its fields.

  4. 04

    Test with Run once

    Click Run once, then create a test record in Ksaar. Open the bubble above each module to read the bundles it received and confirm the follow-up record looks right.

  5. 05

    Schedule and switch on

    Click the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Set the interval, then switch the scenario on.

Triggers

Ksaar triggers: what starts your scenario

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

Ksaar1Watch Records

Watch Records

Scheduled trigger

In Make“Triggers when a record is created.”

Every record freshly added to a Ksaar workflow becomes a bundle your scenario can use, so the next step starts from real data instead of a manual export.

How it fires
scheduled. Make checks Ksaar on the scenario's schedule, every 15 minutes by default, and picks up the records created since the last check.
When to use it
a request, an order or a form entry arrives in Ksaar and something must happen next in another tool.
Watch out
only creations count here; a record edited later will not start this trigger again.
Ksaar2Watch Records Update

Watch Records Update

Scheduled trigger

In Make“Triggers when a record is updated.”

Changes to existing records reach Make with this trigger, which lets a status change or a corrected value flow into your other tools without anyone copying it by hand.

How it fires
scheduled. Make checks Ksaar on the scenario's schedule and collects the records modified since its previous pass.
When to use it
a file moves to a new stage in Ksaar and your team wants the CRM or the shared sheet to follow.
Watch out
if the same scenario then runs Update a Record on those records, each update counts as a fresh change on the next pass, and the scenario feeds itself.
Ksaar3Watch Users

Watch Users

Scheduled trigger

In Make“Triggers when a user is created or updated.”

Accounts of your Ksaar application come to Make here, both new ones and edited ones, so access and contact lists elsewhere stay in step with Ksaar.

How it fires
scheduled. Make checks Ksaar on the scenario's schedule and returns the users created or updated since the last run.
When to use it
a new member joins the application and should also appear in your mailing tool or your team directory.
Watch out
creations and edits come through the same door, so a later filter must tell a brand new user from a changed profile before you create anything.
Modules

Ksaar modules: what each one does for you

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

Ksaar1

Create a Record

Action

In Make“Creates a record in a workflow.”

You get a new record in the Ksaar workflow of your choice, filled with data from an earlier module, whether a form, an email or another app.

When to use it
an order arrives in your shop and the operations team works it in a Ksaar workflow.
Watch out
Make creates one record per bundle, so a search placed before it can multiply the records.
Ksaar2

Delete Record

Action

In Make“Deletes a record by ID.”

This removes a record from Ksaar using its ID, which keeps a workflow free of test entries or cancelled requests without opening the application.

When to use it
a request is cancelled in the source tool and its Ksaar copy should disappear as well.
Watch out
a deletion cannot be undone from Make, so run it once on a test record first.
Ksaar3

Get a Record

Action

In Make“Retrieves a record by ID.”

With a record ID in hand, this module fetches the full record, giving the rest of the scenario every value it holds rather than the few a trigger passed along.

When to use it
an email or another app mentions a record ID and you need its details to answer.
Watch out
it needs the exact ID; to find records by browsing a workflow, use List Records instead.
Ksaar4

Get a User

Action

In Make“Retrieves a user by ID.”

You receive the profile of one Ksaar user, looked up by ID, ready to map into an email, a ticket or another application.

When to use it
a record points to its owner and the scenario must know who to notify.
Watch out
without an ID, start with List Users, which returns the users of the application so you can pick one.
Ksaar5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This one opens the rest of the Ksaar API from your scenario, using the same connection as the other modules, so a feature without its own module is still within reach.

When to use it
none of the ready-made modules does what you need, such as a Ksaar operation missing from the list above.
Watch out
you write the request yourself, and Make's Ksaar documentation does not describe the available calls, so ask Ksaar for them before you build.
Ksaar6

Update a Record

Action

In Make“Updates a record by ID.”

An existing record changes in place, found by its ID, so a status, an amount or a note stays current in Ksaar without a manual edit.

When to use it
a payment is confirmed in your billing tool and the matching Ksaar record should show it.
Watch out
placed after Watch Records Update in the same scenario, it can trigger a new run on every pass.
Ksaar7

Update a User

Action

In Make“Updates a user by ID.”

A Ksaar user profile is corrected from another source, located by its ID, which spares you from maintaining the same person in two places.

When to use it
HR changes a job title or a department and Ksaar should reflect it.
Watch out
Watch Users also reports edits, so pairing the two can make the scenario react to its own changes.
Ksaar8

List Records

Search

In Make“Lists records from a workflow.”

Every record of a workflow comes back as its own bundle, which is the way to export, audit or summarize a whole Ksaar workflow elsewhere.

When to use it
a manager wants the open requests copied into a spreadsheet for a review meeting.
Watch out
each record returned becomes an operation in the modules that follow, so large workflows use up your plan faster.
Ksaar9

List Users

Search

In Make“Lists users of an application.”

You get the users of your Ksaar application, one bundle per person, which lets you sync, check or contact the whole group in one scenario.

When to use it
you want to compare Ksaar accounts with the staff list kept in another tool.
Watch out
a search can return nothing, one user or many, so plan for an empty result before the next step.
Ksaar10

List Workflows

Search

In Make“Retrieves workflows from an application.”

This search returns the workflows of your Ksaar application, which helps when a scenario must pick the right workflow dynamically instead of a fixed one.

When to use it
you run several similar workflows and want one scenario to handle each of them in turn.
Watch out
it lists the workflows themselves, not their records; add List Records afterward to reach the content.
Need help

Need help automating Ksaar with Make?

A person reads every message.

FAQ

Ksaar and Make: frequent questions

01Is the Ksaar Make integration free?
Yes, Ksaar is a standard app in Make, so it works from the Free plan onward. The Free plan has limits you will feel quickly, though: 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) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in credits, meaning operations, each month. Ksaar's own subscription is a separate matter this page does not cover.
02What does it take to connect Ksaar to Make?
A Ksaar account with access to the application you want to automate, and a Make account. Make's documentation lists no specific prerequisite for Ksaar. You add any Ksaar module, click Create a connection, optionally give it a name, authorize Make on the Ksaar page or paste the key Ksaar gives you, then click Save. That connection is created once and every Ksaar module in your scenarios reuses it. If authorization fails, check that the Ksaar account you used can see the application you are targeting.
03Do Ksaar triggers in Make fire instantly?
No. All 3 Ksaar triggers are scheduled: Watch Records, Watch Records Update and Watch Users. Make checks Ksaar on the scenario's schedule and collects what changed since the previous check. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. Ksaar has no instant trigger in Make, the kind an app calls through a webhook as soon as something happens, so expect a short delay between the change in Ksaar and the reaction in your scenario.
04What if a Ksaar module is missing in Make?
Use Make an API Call. It sends any request the Ksaar API supports, with the same connection as the other modules, so an endpoint without a dedicated module stays reachable. You write the request yourself: Make's documentation does not list the available calls, so check them with Ksaar. Keep in mind that Make states its own Ksaar documentation is limited, because little public information exists about the app. When a scenario behaves oddly, run it once and read the bundles each module received: that usually shows whether the issue comes from the data or from the module settings.
05Make or n8n for Ksaar: which fits better?
It depends on the tool your team already works in. On the Make side, Ksaar offers 13 ready-made modules, including 3 scheduled triggers, plus Make an API Call for the rest of the API, and it runs from the Free plan. Ksaar may also have an n8n node, so check what that node covers before choosing. The useful test is simple: list the records, users and workflows your process touches, then see which tool already has a module for each step. The n8n vs Make comparison goes further into how the two editors differ.
Same platform

Other docs you might need on this stack.

Browse all integrations