Ksaar

Ksaar is the French no-code application platform. Agents discover applications and their workflows, create, search, and update workflow records with Ksaar's JSON search, manage application users, and read the files attached to either.

Verified 24 actions Basic auth available

Ksaar website Platform Documentation Capability data verified 2026-08-24

A retention policy run opens against a Ksaar application

Search Records builds the candidate list with a JSON filter tree, and Count Workflow Records sizes each workflow it touches

List Workflow Fields confirms every key in the filter is a real field identifier, because Ksaar ignores a key it does not recognize rather than refusing the call

Download Record File preserves the attachments that would otherwise go with the records

The agent posts the candidate count broken down by workflow, with the number of attached files alongside it

A data owner approves the list before Bulk Delete Records runs, because that route is scoped to the whole application rather than to the workflow the review started in

What This Integration Enables

Ksaar is the French no-code application platform, and its data model puts a person at the center of every row. Creating a record requires an email, and that email is not a form field: it is the owner the record is attributed to. The people who sign in to the application are first-class objects with their own configurable profile fields and their own file fields, sitting alongside the workflow records rather than off in an admin corner. That shapes what an agent can do here. It can find a user by email, read what their profile schema actually contains, write to it, and put documents on it, all as ordinary steps in a flow.

The other half of the surface is the search. The plain record listing applies no filter at all, so real work happens through Search Records and its nested JSON filter tree, with comparisons and groups that nest and field paths that can hop across linked records. Bulk creates, updates and deletes exist for volume. Because Ksaar ignores an unrecognized key rather than refusing it, an agent that writes without reading the schema first can appear to succeed while changing nothing, which is exactly the class of failure human-in-the-loop exists to catch before it compounds.

Without FlowRunner

Filters that fail silently An unrecognized field key is ignored rather than refused, so a wrong filter reads as an empty result instead of an error

Records without an owner Rows exist in a table with no reliable link back to the person the application serves

Cleanup scoped by hope A bulk deletion is aimed at one table and reaches whatever the identifier list actually contained

With FlowRunner

Filters checked against the schema Field identifiers are read before the search runs, so a typo surfaces as a mapping problem rather than as zero rows

Records attributed on creation Every record carries the owning user's address, so a workflow can always answer whose record this is

Cleanup scoped and counted The candidate set is sized per workflow and shown to a person before anything is deleted

Use Case Scenarios

Records that know whose they are

A support request arrives by email. The agent calls Find User By Email to turn the address into the application user, List Workflow Fields to get the field identifiers for the request workflow, and Create Record with that user's email as the owner. Supporting documents arrive through Upload Record File. A confirmation goes back through Gmail and the request appears in the team's queue in Slack. Nobody has to reconcile the row against a person afterward, because the row was attributed when it was created.
Profile upkeep across an application's user base

An application's users each carry a configurable profile: certifications, addresses, an identity document. The agent reads List User Fields so it knows what the profile actually contains in this application, then works through the users with List Application Users, calling Get User for the current state and Update User for the fields that need refreshing. Where a certificate is due for renewal it calls Download User File to inspect what is on record and Upload User File to replace it, and Delete User File to clear an expired one. The profile stays current without anyone opening it.
Loading a season's worth of records at once

A partner sends a batch of applications as a file. The agent parses it, validates each entry against the field identifiers from List Workflow Fields, and calls Bulk Create Records so the whole set lands in a single call rather than looping against a per minute request limit. Anything that fails validation is held back with a reason rather than being written half formed, and the exceptions go to a person while the clean records go straight into the workflow.

Human-in-Loop Highlight

The deletion gate on this connector is not about deletion being permanent, although it is. It is about scope. Delete Record removes one record and the files attached to it. Bulk Delete Records is keyed on the application rather than on the workflow, because the identifiers it takes may come from several workflows at once, and there is no dry run. That means a retention sweep that was reasoned about while looking at one table can reach records in tables nobody had open. So the agent never hands that list straight to the API. It posts the breakdown: "The retention filter matches 1,204 records across three workflows: Demandes 1,043, Pieces jointes 138, Archives 23. 412 of them carry attached files that will be deleted with the record. The review that produced this policy only covered Demandes. Proceed with all three, restrict to Demandes, or hold?" The data owner answers, and only then does the bulk call run against the confirmed set. The agent is far better at assembling that list than a person. The decision about how wide the sweep reaches is not an assembly problem.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

24 actions

Applications and Workflows

List Applications Returns the applications the API key can reach. A key is issued per application, so this is how a flow discovers that application's identifier without hard coding it.
List Application Workflows Returns the workflows inside one application. A workflow is Ksaar's table, and this is where the identifier every record operation needs comes from.
List Workflow Fields Returns a workflow's field definitions with their identifiers, UUIDs, labels and types. The schema every record operation is keyed by.

Application Users

List Application Users Returns the end users of an application, meaning the people who sign in to it rather than the people who built it.
Find User By Email Looks up one application user by email address. The reliable way to turn an address a flow already has into the user identifier later steps need.
List User Fields Returns the field definitions of an application's user profile. Read it before writing to a user, because a profile write is keyed by field identifier.
Get User Returns one application user with every profile field the application defines.
Update User Writes profile fields onto an application user. Keys are field identifiers rather than labels, and an unrecognized key is ignored rather than refused.

User Files

Download User File Downloads the file held in one file field of a user profile into FlowRunner file storage and returns a URL later steps can use.
Upload User File Downloads a file from a URL and stores it in a file field of a user profile.
Delete User File Removes one file from a file field of a user profile, leaving the field and the rest of the profile untouched.

Records

List Workflow Records Pages through every record in a workflow in creation or update order. It applies no filter at all.
Count Workflow Records Returns how many records a workflow holds without transferring any of them. A cheap check before a flow commits to paging a table.
Search Records Searches a workflow with a nested JSON filter tree, with sorting and pagination. A filter is either one comparison or a group, groups nest, and a field can be an identifier, a UUID, or a path across linked records.
Create Record Creates one record in a workflow. Ksaar requires an email on every record, and that email is the owner the record is attributed to rather than a field of the form.
Get Record Returns one record by identifier with all of its field values.
Update Record Writes field values onto an existing record. Only the keys supplied are written, so this is the safe operation for changing one field.
Delete Record Permanently deletes one record and the files attached to it. There is no undo.

Bulk Operations

Bulk Create Records Creates many records in one workflow in a single call, each entry carrying its own owner email and field values. Far cheaper than looping against a per minute request limit.
Bulk Update Records Updates many records across one application in a single call. The route is keyed on the application because the records may come from several workflows.
Bulk Delete Records Permanently deletes many records across one application in a single call. There is no undo and no dry run, so the identifier list should come from a search rather than from a person typing.

Record Files

Download Record File Downloads the file held in one file field of a record into FlowRunner file storage and returns a URL later steps can use.
Upload Record File Downloads a file from a URL and stores it in a file field of a record.
Delete Record File Removes one file from a file field of a record, leaving the record and its other fields untouched.

Frequently Asked Questions

What can FlowRunner do with Ksaar?

FlowRunner agents can run List Applications, List Application Workflows, and List Application Users in Ksaar, plus 21 more actions.

Does connecting Ksaar to FlowRunner require OAuth?

No. Ksaar connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Ksaar trigger a FlowRunner workflow automatically?

Ksaar doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Ksaar

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us