FlowRunner
PricingContact
Theme
Start Free

Kizeo Forms

Forms

Kizeo Forms is a French mobile data collection platform that replaces paper forms in the field. Agents read entries with crash-safe read markers, push forms to users, manage external lists, export entries to file storage, and react to new field submissions.

2 triggers 39 actions API key available
Kizeo Forms website Platform Documentation Capability data verified 2026-08-26
On Unread Form Entry delivers an inspection a technician completed on site
Get Form Entry returns every answer, the repeating table rows, and the submitting user
Agent confirms the required readings and the signature field were actually filled in
Search Form Data looks for an earlier entry against the same asset this month
Download Entry PDF renders the branded report and stores it for the rest of the flow
The report and its findings post to the operations channel with site and technician named
The service manager reads a failed inspection and decides whether to dispatch a callout

What This Integration Enables

Kizeo Forms is built for work that happens where the network is not. Crews fill in forms on a phone in a basement, a field, or a truck, and the submissions sync when signal returns. That shapes what an integration has to survive, and it is why the most interesting thing in this connector is not an action at all. It is where the read marker lives. Kizeo's own integration mechanism keeps a per action read marker on its server, so an agent asks for what it has not yet seen, processes it, and only then marks it read. If FlowRunner is unavailable for an afternoon, the day's inspections are still waiting on the next poll rather than lost to a watermark that moved without them.

FlowRunner agents read and search entries, render them into PDF, Word, Excel, and CSV documents, pull down the photos and signatures captured on site, dispatch prefilled forms back to a technician's device, keep the reference lists behind a form's dropdowns in step with the system of record, and administer users and the group tree. Kizeo publishes no webhook API, so both triggers poll, and both say so plainly rather than implying an event stream that does not exist. Agents do the collecting, the rendering, and the filing. The judgment calls that a wrong answer would make expensive stay with a person, which is what human-in-the-loop means here.

Without FlowRunner

Submissions wait for someone Completed forms sit in the back office until a person opens the account and looks
Retyping into the system of record Field data is rekeyed into the ERP, which is where the transcription errors come from
Dropdowns drift from reality Field users pick from a customer or equipment list that was last refreshed by hand

With FlowRunner

Submissions are consumed, not collected Each new entry is picked up for processing as soon as the crew syncs it
Field data lands in the system of record The entry, its photos, and its rendered report reach the ERP without a second keystroke
Reference data stays current The lists behind the dropdowns are refreshed from the system of record under review

Use Case Scenarios

  • An inspection becomes a report before the technician reaches the van

    On Unread Form Entry fires for a completed inspection. The agent calls Get Form Entry for the full record, checks that the mandatory readings and the customer signature are present, and calls Download Entry PDF to render the branded report. Download Entry Media pulls the site photos into storage alongside it. The report and the photos are filed to SharePoint, a summary posts to Slack with the site and the technician named, and the job's captured hours and materials open a bill in Acumatica. Mark Entries As Read runs last, after everything downstream succeeded, so a failed filing step means the entry comes back on the next poll instead of vanishing.

  • Tomorrow's work is already on the device

    The day's scheduled jobs are read out of Airtable. For each one, the agent calls Push Entry To User with the customer, the site, and the asset identifier already filled in, plus the planning window the technician should arrive in. Get Form Definition tells the agent which field identifiers to populate, because Kizeo addresses fields by identifier rather than by the caption the technician sees. Crews start the day with the paperwork half done and no reference numbers to type twice.

  • The reference lists follow the system of record

    A nightly agent reads the current customer and equipment master out of Google Sheets, then reads the corresponding Kizeo list with Get External List and compares the two. Additions and renames are routine. Removals are not, because Replace External List Items is a full replacement and anything missing from the payload disappears from the dropdown that field users pick from. So the agent presents the removals for a decision before it writes anything, and the routine part of the sync runs on its own.

Human-in-Loop Highlight

Replace External List Items deletes every existing item and inserts what the payload contains. There is no append mode and no restore. If the upstream export was truncated overnight, a sync agent will faithfully write the truncated list, and by the time anyone notices, a crew is standing in front of a customer whose name is no longer in the dropdown. So the sync agent stops before the write and posts to the list owner: "Tonight's customer export has 412 rows against 1,206 items on the Kizeo list. This write would remove 794 entries, including 63 sites with an inspection scheduled this week. Apply as written, apply additions and renames only, or hold?" The owner picks. Comparing the two lists, spotting the renames, and counting the affected sites is work the agent should do every single night. Deciding that 794 dropdown options should stop existing is not.

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

39 actions

Forms

2
  • List Forms Lists every form the token can reach with its id and name. The starting point for almost any flow, since most other operations take a form id.
  • Get Form Definition Returns a form's complete definition: every field with its identifier, type, validation, and visibility rules, plus the export models and options configured on it. Read this before writing to a form, because Kizeo addresses fields by identifier rather than by caption.

Form Data

7
  • Search Form Data Searches a form's entries through Kizeo's advanced filter engine, combining free text with field conditions and sorting. The query behind reporting sweeps and duplicate checks.
  • Get Form Entry Returns one entry in full, including repeating table rows and Kizeo's own metadata markers such as record number, submitting user, and answer time.
  • Get Unread Entries Returns the entries a named action has not yet seen. Reading does not clear the marker, which is what makes the two step design safe across a crash.
  • Mark Entries As Read Marks entries as read for a named action. Called after downstream processing succeeded, never before.
  • Mark Entries As Unread Puts entries back in the unread queue so they can be replayed after a downstream failure, or reprocessed deliberately.
  • Push Entry To User Sends a partly filled form to a field user's device with a planning window. This is how Kizeo dispatches work rather than merely collecting it.
  • Get Push Inbox Returns the pushed entries waiting for the token's own user, so a flow can collect assignments addressed to it.

Exports

7
  • List Export Models Lists the Word and Excel export models configured on a form, including which one is the default. Export model ids are what the entry export operations take.
  • Download Entry PDF Renders one entry as a PDF using the form's default export model and stores it in file storage. The fastest path from a field submission to a shareable report.
  • Export Entry With Model Renders one entry through a specific Word or Excel template, optionally converting to PDF. Used when a form carries several report layouts.
  • Export Entries To PDF Renders several entries through one export model into a single PDF, for a combined report such as every inspection completed on a site this week.
  • Export Entries To Spreadsheet Exports several entries as one CSV or Excel listing, either in the standard full column form or following the column template configured on the form.
  • Download Entry Media Downloads a photo, signature, or attachment captured in an entry and stores it. The media name is the value held in the entry's field, so read the entry first.
  • Download Form Picture Downloads one of the fixed images built into the form's design, such as a logo or a reference diagram.

External Lists

3
  • List External Lists Lists the external lists the token can reach with their last update times. These are the reference data behind a form's dropdowns.
  • Get External List Returns one list with all of its items as key and value pairs. The read that a safe sync compares against before it writes.
  • Replace External List Items Replaces every item of an external list with the items supplied. This is a full replacement, so anything omitted disappears from the list and from the dropdowns that use it. The operation this page's human gate exists for.

Users

4
  • List Users Lists every user in the account with roles, contact details, and the twenty reference fields Kizeo keeps against a user.
  • Create User Creates a user and returns the new id. Form User grants mobile application access; the administrative flags grant back office rights.
  • Update User Updates an existing user. Kizeo requires the login on every update even when it is unchanged.
  • Delete User Permanently deletes a user. Entries the user already submitted are kept and continue to reference the deleted id.

Groups

14
  • List Groups Lists every group in the account. Groups are how Kizeo scopes form access and data visibility.
  • List Groups In Tree Order Lists groups hierarchically, parents before children, for mirroring the tree into another system.
  • Get Group Returns one group with its members, its leaders, and its child groups.
  • Create Group Creates a group, optionally nested under a parent. Groups are created empty.
  • Update Group Renames a group or moves it under a different parent. Moving a group carries its members and children with it, which changes what those users can see.
  • Delete Group Deletes a group. Its users survive but lose the access the group granted, so audit membership first.
  • List Group Members Lists the users in a group with their full records. The audit read behind an access review.
  • List Group Leaders Lists a group's leaders. A leader's token is scoped to their branch of the tree rather than the whole account.
  • Add User To Group Adds one user to a group and returns the updated membership.
  • Add Users To Group Adds several users to a group in one call, which is how a new crew is provisioned.
  • Remove User From Group Removes one user from a group. The account survives; the access the group granted does not.
  • Add Leader To Group Promotes a user to leader of a group, granting administrative rights over that branch.
  • Add Leaders To Group Promotes several users to leaders of a group in one call.
  • Remove Leader From Group Demotes a leader back to an ordinary member without touching their account.

Tokens

2
  • Revoke Token Revokes one API token, cutting off every integration using it. Pointed at this connection's own token, it breaks the connection.
  • Revoke All Tokens Revokes every token on the account, this connection included, and new tokens have to be requested from Kizeo support. Reserve it for a credential compromise, and gate it.

Triggers

2 triggers

Event Triggers

2
  • On New Form Entry Fires when a new entry is submitted against the watched form and emits the complete record. It is read only and never touches Kizeo's own read markers, so it can run alongside other integrations on the same form. The first poll sets a baseline without firing, so historical entries are not replayed.
  • On Unread Form Entry Fires for each entry Kizeo reports as unread for a named action, then marks those entries read. The marker lives on Kizeo's server rather than in flow state, so entries submitted while FlowRunner was unavailable are still waiting on the next poll. Give each flow its own action name, since two flows sharing one would consume each other's entries, and use Mark Entries As Unread to replay after a downstream failure.

Frequently Asked Questions

What can FlowRunner do with Kizeo Forms?

FlowRunner agents can run List Forms, Get Form Definition, and Search Form Data in Kizeo Forms, plus 36 more actions.

Does connecting Kizeo Forms to FlowRunner require OAuth?

No. Kizeo Forms connects to FlowRunner with an API key, no OAuth flow required.

Can Kizeo Forms trigger a FlowRunner workflow automatically?

Yes. Kizeo Forms supports 2 triggers that can start a FlowRunner workflow automatically.

Start building with Kizeo Forms

Free plan, no card required. Connect in minutes.