Kintone
DatabaseTreat Kintone apps as a live database for your agents. They query records with conditions and pagination, create or update up to 100 records at once, post comments with mentions to record timelines, and read app schemas to build valid payloads dynamically.
A new order lands from the storefront
Get Form Fields reads the orders app schema so the payload maps to current field codes
Query Records looks for an existing record with the same order number
Add Record writes the order with customer, amount, and status
The flow flags orders above the team's approval threshold
The fulfillment lead reviews flagged orders and picks standard or expedited handling
Update Record sets the decision and Add Record Comment mentions the packing team
What This Integration Enables
Kintone's quiet achievement is that operations teams built their own systems of record with it: the order tracker, the vendor list, the inspection log, each one an app someone assembled without engineering. The gap is that those apps still get fed by hand. FlowRunner closes it by treating every Kintone app as a live database an agent can query, write, and annotate, and the connector's schema discovery is what makes that durable: an agent calls Get Form Fields first, learns the current field codes and types, and builds valid payloads against the app as it exists today, not as it existed when someone wrote a script.
- Query records with real conditions, ordering, and pagination to feed reports and downstream steps
- Create and update records one at a time, or up to 100 per request with the bulk actions
- Enforce optimistic locking on updates so concurrent edits fail loudly instead of overwriting silently
- Post comments with @mentions to a record's timeline so notifications land where the work lives
- Discover apps and schemas dynamically with List Apps and Get Form Fields
Without FlowRunner
Apps updated by hand The Kintone apps that replaced the spreadsheets still depend on someone retyping data from other systems
Integrations break on schema changes A renamed field silently kills the sync script, and nobody notices until the numbers disagree
Notifications happen in hallways A record changes state and the person who needs to act finds out at the next meeting
With FlowRunner
Apps fed by every connected system Orders, payments, and bookings write themselves into the right app within seconds of the event
Agents read the schema before they write Get Form Fields tells the agent the current field codes and types, so payloads adapt instead of breaking
The timeline carries the workflow Comments with @mentions land on the record itself, notifying exactly the people who need to move
Use Case Scenarios
-
Orders flow in, exceptions flow to people
A Shopify order fires the flow. Query Records confirms the order is new, Add Record writes it into the orders app, and for orders above the threshold, Add Record Comment mentions the fulfillment lead with the details. When a Stripe payment confirms later, the flow finds the matching record with Query Records and marks it paid with Update Record, passing the revision so a simultaneous manual edit fails the update instead of being overwritten.
-
The bulk import that respects the schema
Every morning, the flow aggregates yesterday's qualified leads from Typeform and the booking calendar. Get Form Fields pulls the lead app's current schema, the agent maps each lead's fields to the live field codes, and Add Records writes them in batches of up to 100. When someone renames a dropdown or adds a required field, the next run sees the change in the schema and adapts the payload, instead of failing at 2 am with a cryptic field error.
-
The weekly report that assembles itself
On Friday afternoon, Query Records pulls every record in Status = "Open" ordered by age, with the total count included. The flow writes the snapshot to Google Sheets, posts a summary to Slack with the oldest items called out, and drops Add Record Comment mentions on the records that have sat untouched past the SLA, tagging their owners directly on the timeline where they will see it Monday morning.
Human-in-Loop Highlight
Delete Records removes up to 100 records per request and cannot be undone. In an app that has served as the team's system of record for years, that is potentially a hundred order histories, inspection results, or vendor negotiations gone in one call. So a FlowRunner cleanup agent never decides what dies. A quarterly sweep queries for records that look abandoned: closed status, no timeline activity, no linked records. It posts the candidate list with counts and a sample, and asks the app owner to confirm. The owner strikes two records that look dormant but are evidence in an open dispute, approves the rest, and only then does Delete Records run. The query, the filtering, and the batching are machine work. The judgment about which history the team can afford to lose 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
102 actionsRecords
8- Get Record Retrieves a single record by ID, with every field code mapped to its type and value. The full-context read before a decision or an update.
- Query Records Retrieves multiple records using Kintone query syntax: field conditions, ordering, and pagination, with an optional total count. A single request returns up to 500 records. The read behind every report and sweep on this page.
- Add Record Creates a single record, mapping field codes to value wrappers. Calculated, lookup-mapped, status, and category fields are set by Kintone and must be omitted. Returns the new record's ID and revision.
- Update Record Updates a single record by ID, changing only the supplied fields. Pass a revision to enforce optimistic locking, so an update against a stale copy fails instead of overwriting someone's edit.
- Add Records Creates up to 100 records in one request from an array of record objects, returning IDs and revisions in order. The workhorse for imports and aggregation flows.
- Update Records Updates up to 100 records in one request, each entry pairing a record ID with the fields to change. Used for batch status moves and enrichment passes.
- Delete Records Permanently deletes up to 100 records by ID in a single request. This cannot be undone, which is exactly why this page's human gate exists for it.
- Run Bulk Request Runs several record API calls in sequence across multiple apps in one request. Used when a single business event has to land consistently in more than one app.
Record Cursors
3- Create Records Cursor Opens a cursor so an agent can page through a result set larger than a single query returns.
- Get Records From Cursor Retrieves the next batch of records from an open cursor. The read used to walk an entire app without holding it all in memory.
- Delete Records Cursor Closes a cursor by ID. Used to release the cursor slot when a sweep finishes early.
Process Management
3- Update Record Status Advances a record through its process management workflow to the next status.
- Update Multiple Record Statuses Advances several records through their process management workflow in one request. Used for batch approvals and stage moves.
- Update Record Assignees Sets who is responsible for a record at its current process management status. The call that puts a named person on the hook rather than a queue.
Comments
3- Get Record Comments Retrieves the comments on a record's timeline. Used to read the discussion history before an agent adds to it.
- Add Record Comment Posts a comment to a record's timeline, optionally mentioning users, groups, or organizations so they are notified. The step that turns a workflow event into a notification on the record itself.
- Delete Record Comment Removes a comment from a record's timeline. Used to retract an agent's own posting, not to edit the team's history.
Files
2- Upload File Uploads a file to Kintone and returns a file key. This does not attach the file to anything on its own: the key has to be written into an attachment field with Add Record or Update Record before it is part of a record.
- Download File Downloads a file from an attachment field and returns it base64 encoded, using the file key found on the record's attachment field.
Apps and Schema
8- List Apps Lists the apps available to the authenticated user with ID, name, description, and space, with name filtering and pagination. Used to resolve app IDs before any record operation.
- Get App Gets an app's general information, including name, description, related space, and who created and last updated it.
- Get App Settings Gets an app's description, name, icon, color theme, and current revision.
- Get Form Fields Retrieves an app's field definitions: code, label, type, required flags, and dropdown options. The discovery step that lets agents build valid payloads against the app as it exists today.
- Get App Form Layout Gets how fields are arranged on an app's form, including rows, groups, and subtables.
- Get Form (Legacy) Retrieves an app's form details through the legacy form endpoint. Kept for apps and scripts still built against the older shape.
- Get Apps Statistics Gets usage statistics across apps. Used to find the apps that are actually load-bearing before anyone reorganizes them.
- Move App To Space Moves an app into a different space, which also moves who can see it.
Live App Settings
9- Get App Views Gets an app's view settings, meaning the saved lists and filters users see.
- Get App Status Gets an app's process management settings: the statuses records move through and the transitions between them.
- Get App Reports Gets an app's graph and report settings.
- Get App Actions Gets an app's action settings, which copy data from one app into another.
- Get App Customize Gets the JavaScript and CSS customizations attached to an app.
- Get App Admin Notes Gets the notes left for app administrators and their visibility settings.
- Get App Notifications General Gets an app's general notification settings.
- Get App Notifications Per Record Gets an app's per-record notification settings, which fire on conditions rather than on every change.
- Get App Notifications Reminder Gets an app's reminder notification settings, which fire relative to a date field.
Permissions
7- Get App ACL Gets who can see and administer an app.
- Update App ACL Updates who can see and administer an app. This writes to the pre-live app, so it takes a deploy to reach users.
- Get Field ACL Gets the per-field permission settings, which control who can read or edit individual fields.
- Update Field ACL Updates the per-field permission settings. Tightening a field here hides data from people who could read it a moment ago, so it belongs in a reviewed change.
- Get Record ACL Gets the record-level permission rules, which grant access based on field values rather than on the app as a whole.
- Update Record ACL Updates the record-level permission rules. A rule change here can expose or hide whole classes of records at once.
- Evaluate Record Permissions Evaluates what the connected API user can actually see and edit on records and fields in an app. The check to run before assuming a flow has the access it needs.
Preview App Configuration: Reads
17- Get Preview App Settings Gets the pre-live app's description, name, icon, color theme, and revision.
- Get Preview App Form Fields Gets the fields and field settings staged on the pre-live app. The read that shows what a deploy would change.
- Get Preview App Form Layout Gets the field layout staged on the pre-live app.
- Get Preview Form (Legacy) Retrieves the pre-live app's form details through the legacy form endpoint.
- Get Preview App Views Gets the view settings staged on the pre-live app.
- Get Preview App Status Gets the process management settings staged on the pre-live app.
- Get Preview App Reports Gets the graph and report settings staged on the pre-live app.
- Get Preview App Actions Gets the action settings staged on the pre-live app.
- Get Preview App Customize Gets the JavaScript and CSS customizations staged on the pre-live app.
- Get Preview App Admin Notes Gets the administrator notes staged on the pre-live app.
- Get Preview App Notifications General Gets the general notification settings staged on the pre-live app.
- Get Preview App Notifications Per Record Gets the per-record notification settings staged on the pre-live app.
- Get Preview App Notifications Reminder Gets the reminder notification settings staged on the pre-live app.
- Get Preview App Plugins Gets the plug-ins staged on the pre-live app.
- Get Preview App ACL Gets the app permissions staged on the pre-live app.
- Get Preview Field ACL Gets the field permission settings staged on the pre-live app.
- Get Preview Record ACL Gets the record permission settings staged on the pre-live app.
Preview App Configuration: Writes
18- Update Preview App Settings Stages a change to the app's name, description, icon, or color theme. Nothing users see changes until a deploy.
- Add Preview App Form Fields Stages new fields on the app's form. Used to extend an app for a new data source before anyone has to fill the fields in.
- Update Preview App Form Fields Stages changes to existing field settings, including labels, options, and required flags.
- Delete Preview App Form Fields Stages the removal of fields from the app's form. Once deployed, the data those fields held goes with them.
- Update Preview App Form Layout Stages a new arrangement of fields on the app's form.
- Update Preview App Views Stages changes to the saved lists and filters users work from.
- Update Preview App Status Stages changes to process management: the statuses records move through and who can move them.
- Update Preview App Reports Stages changes to the app's graph and report settings.
- Update Preview App Actions Stages changes to the app's action settings.
- Update Preview App Customize Stages new JavaScript or CSS customization for the app.
- Update Preview App Admin Notes Stages changes to the notes shown to app administrators.
- Update Preview App Notifications General Stages changes to who gets notified about general app activity.
- Update Preview App Notifications Per Record Stages changes to the conditional per-record notifications.
- Update Preview App Notifications Reminder Stages changes to the date-driven reminder notifications.
- Add Preview App Plugins Stages the addition of plug-ins to the app.
- Update Preview App ACL Stages a change to who can see and administer the app.
- Update Preview Field ACL Stages a change to per-field permissions.
- Update Preview Record ACL Stages a change to record-level permission rules.
Creating and Deploying App Changes
3- Create Preview App Creates a new app in its pre-live state, so its schema and settings can be built up before anyone can use it.
- Deploy App Settings Pushes the pre-live app to the live app, which is the only call in this group users actually feel. It deploys every pending pre-live change, not only the ones this flow staged, so an unrelated half-finished edit sitting in preview ships with it.
- Get Deployment Status Gets the deployment status for one or more apps. Used to confirm a deploy finished before a flow writes records against the new schema.
Spaces
12- Get Space Gets a space's information, including its apps, threads, and configuration.
- Get Spaces Statistics Gets usage statistics across spaces.
- Create Space From Template Creates a space from a space template. Used to stand up a standard project or client workspace on demand.
- Update Space Updates a space's settings.
- Update Space Body Updates the body content shown on a space's portal page.
- Get Space Members Gets a space's member list. Used to check who has access before posting anything into it.
- Update Space Members Replaces a space's member list. Anyone left out of the submitted list loses access to everything in the space.
- Update Space Guests Replaces a space's guest member list, controlling which external people can reach it.
- Add Space Thread Adds a discussion thread to a space.
- Update Space Thread Updates a space thread's name or body.
- Add Space Thread Comment Posts a comment to a space thread, so an agent can report into the team's discussion rather than only onto a record.
- Delete Space Deletes a space. The apps, threads, and history inside it go too, which makes this the widest single delete the connector offers.
Guests
2- Add Guest Users Adds guest user accounts to Kintone. It does not put them in a guest space and sends no invitation email, so access is a second, deliberate step.
- Delete Guest User Deletes a guest user account outright. To take someone out of one guest space without destroying their account, update that space's guest members instead.
Plug-ins
7- Get Plugins Gets the plug-ins imported into the Kintone environment.
- Get App Plugins Gets the plug-ins added to a specific app.
- Get Apps Using Plug-in Gets every app that has a given plug-in added. The dependency check to run before touching a plug-in.
- Get Required Plug-ins Gets plug-ins that apps still depend on but that have been removed from the environment. Used to find apps that are quietly broken.
- Install Plug-in Imports a plug-in into the Kintone environment from an uploaded file.
- Update Plug-in Updates an imported plug-in to a new version. Every app using it picks up the change.
- Uninstall Plug-in Removes an imported plug-in from the Kintone environment. Run Get Apps Using Plug-in first, because apps that depend on it stop working.
Frequently Asked Questions
What can FlowRunner do with Kintone?
FlowRunner agents can run Get Record, Query Records, and Add Record in Kintone, plus 99 more actions.
Does connecting Kintone to FlowRunner require OAuth?
No. Kintone connects to FlowRunner with an API key, no OAuth flow required.
Can Kintone trigger a FlowRunner workflow automatically?
Kintone doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other Database integrations
Start building with Kintone
Free plan, no card required. Connect in minutes.