Kissflow

What This Integration Enables

Kissflow gives operations teams structured processes with real approval chains, and its discipline is the point: a purchase order is not an email, it is an instance moving through defined steps. What FlowRunner adds is the connective tissue Kissflow cannot supply from inside its own walls. Agents launch process instances from wherever requests actually originate, keep the datasets that processes look up against synchronized with external systems of record, and read process and board state back out for the people who need status without a login. - Launch process instances, leave requests, purchase orders, onboarding, from external systems and forms - Export process submissions for reporting, notifications, and downstream sync - Keep datasets like departments, cost centers, and product catalogs aligned with the ERP or master source - Read board cards to track pipelines and task work in flight - Fetch a specific item's full record and workflow step from its ID Because Kissflow schemas are tenant-defined, the field names on every process and dataset are yours, not the platform's, and the connector works with that reality: field values pass as JSON keyed by your own field names, and searchable pickers resolve process, dataset, and board IDs per account. The practical effect is that FlowRunner automations speak your installation's language rather than forcing a generic shape onto it. The interesting boundary here is that Kissflow processes contain their own human approvals. FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate sits one step earlier: before the agent submits anything into that formal chain at all. Approvers inside Kissflow judge the request; the gate outside it guarantees the request they judge is faithful to its source.