Jodoo

Jodoo, known as Jiandaoyun in China, is a no-code application platform built on forms and records. Agents read and write form records with file uploads, query aggregate tables, drive workflow instances and their approval tasks, and manage members, departments, and roles.

Verified 53 actions API key available

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

A form record enters an approval workflow in Jodoo

Get Workflow Instance links the approval back to its record, because the instance id is the record's data id

Get Form Fields resolves the generated field names so the agent can actually read what was submitted

Get Approval Comments and Get Workflow Instance Logs collect what earlier approvers already said and why

List Workflow Tasks finds whose inbox the task is sitting in, and the agent delivers the assembled case there

That member presses Approve Task or Reject Task themselves, because Jodoo records the decision under their name

What This Integration Enables

Jodoo, known as Jiandaoyun in China, is not a table with an approval bolted on the side. It ships an approval engine, an organization chart, a role and role group model, audit logs and per app resource accounting, and the FlowRunner connector covers all of it. Agents read and write form records with file uploads, query the saved cross-form summaries Jodoo calls aggregate tables, drive workflow instances and their tasks, maintain members, departments and roles in bulk, and pull audit and usage data for a scope and a time range.

Two behaviors shape how a workflow has to be written. Field names are generated rather than chosen, so Get Form Fields runs before any record operation. And the batch update applies the same values to every record named, which makes it a bulk set rather than a per record edit. Neither is a flaw, but both are the kind of detail that turns a plausible workflow into a wrong one. The connector is built and verified against Jodoo's own API, so what an agent can do here is a matter of record rather than of hope.

What an agent should do is a separate question, and on this platform it has an unusually clean answer. Jodoo's approval operations act as a named person. That is where FlowRunner's human-in-the-loop model stops being a feature and starts being the only correct design.

Without FlowRunner

Approvals arrive without context The task shows up in an inbox and the approver goes hunting for the record, the history and the earlier comments

The org chart is maintained twice Departments and members are updated in the HR system and again by hand in the application platform

Nobody can price an app Usage is a platform-level number, so the app that consumes the resources is a guess

With FlowRunner

Approvals arrive pre-read The agent assembles the record, the prior comments and the exception before the approver opens the task

The org chart syncs Import Members and Import Departments load the structure in bulk, so the platform follows the system of record

Usage is attributable Per app and per member usage reads turn a platform bill into a chargeback line

Use Case Scenarios

The approval inbox that arrives already read

A purchase request enters an approval. Rather than leaving the approver to reconstruct it, the agent calls Get Workflow Instance to tie the approval to the record, Get Form Fields to resolve the generated field names, and Get Approval Comments plus Get Workflow Instance Logs to gather what earlier approvers said. It checks the request against the budget line held in Google Sheets and the vendor record in HubSpot, then posts the whole case into Slack with the exception called out and a link back to the task. The approver reads a page instead of assembling one, and presses the decision in Jodoo.
The organization chart the platform inherits rather than maintains

Joiners, movers and leavers happen in the HR system of record. On a schedule, the agent reads the current structure, compares it against Get Member and List Department Members, and applies the delta with Import Departments and Import Members in bulk rather than one call per person. Role changes go through Add Members To Role. Leavers go to a review list rather than straight to Delete Member, because removing a member frees a licensed seat and ends their access. The platform stops being a second place where the org chart is typed.
Turning platform usage into a chargeback

At the start of each month the agent calls Get Platform Usage for the account total, then Get App Usage and Get Member Usage to break it down. It pairs that with Get Audit Log Types and Get Audit Logs for the same window so unusual activity is visible alongside the consumption. The result is a per department statement rather than a single platform number, and the apps nobody uses become visible enough to retire.

Human-in-Loop Highlight

Jodoo's approval operations do not act as an integration. They act as a person. Approve Task requires the member and the task to correspond, because the platform records the approval under that member's name, and the comment on a Reject Task is what the applicant is shown. An agent holding an API key can technically press either. It should not, and on FlowRunner it does not. The agent works everything around the decision: it resolves the record behind the instance, gathers the prior comments, checks the request against the budget and the vendor master, and delivers the case to the one inbox it belongs in with the exception stated plainly. Then it stops. The approver presses Approve Task or Reject Task, and the audit trail names a human because a human decided. The same discipline covers the recovery operations. Withdraw Task with no task named pulls the whole request back to the start node, Return Task sends it to an earlier approver, and End Workflow Instance stops an approval wherever it has reached while leaving the record standing. Those are moves inside somebody's process, so a person chooses them.

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

53 actions

Apps and Forms

List Apps Returns the apps the API key can reach. Jodoo pages with a skip and a limit and returns no total, so a short page is the end.
List Forms Returns the forms inside an app. A record is identified by an app and a form together, so both ids are needed before any data call.
Get Form Fields Returns a form's fields with their generated names and types. Run it first, because those generated names are the keys every record operation uses.

Records

List Records Returns records from a form. Jodoo pages by the last record's id rather than by an offset, so the next page is requested with the id of the previous page's last row.
Get Record Returns one record from a form.
Create Record Adds a record to a form. Filing it as a particular member matters when a downstream workflow routes on who submitted it.
Create Records In Batch Adds many records to a form in one call. The tightest rate limit of the record operations.
Update Record Changes one record. For a subform, the subform row's own id has to be in the data or Jodoo replaces the rows rather than editing them.
Update Records In Batch Applies the same values to many records at once. This is a bulk set rather than a per record edit, because every field supplied is written to every record named.
Delete Record Deletes one record from a form.
Delete Records In Batch Deletes several records from a form. It answers with a success count rather than a per record result, so compare it against how many ids were sent.
Get File Upload Tokens Returns a block of upload credentials bound to one transaction id. A file uploaded to one of them is only attached when a create or update in the same transaction follows.

Aggregate Tables

List Aggregate Tables Returns an app's aggregate tables, which are Jodoo's saved cross-form summaries.
Get Aggregate Table Fields Returns an aggregate table's fields. Their names are what a filter on the aggregated data must use, and they will not match the underlying form's names.
List Aggregate Table Data Returns the rows of an aggregate table with optional filtering, paging by a cursor from the previous answer.

Workflow and Approvals

Get Workflow Instance Returns a workflow instance. The instance id is the record's data id, which is what connects a form record to the approval running on it.
Get Workflow Instance Logs Returns an instance's log entries, including the approval comments left on it.
Get Approval Comments Returns the approval comments on a record's workflow. The read that gives an approver the history without opening five screens.
List Workflow Tasks Returns the workflow tasks waiting on one member. Jodoo has no everything-pending read, so an inbox always belongs to somebody.
Approve Task Submits a workflow task, which approves it and moves the instance on. Jodoo acts as the named member, so the task has to be theirs.
Reject Task Rejects a workflow task. Rejecting usually ends or reverses the instance, and the comment is what the applicant is shown.
Return Task Sends a task back to an earlier node so the applicant or an earlier approver can change something.
Transfer Task Hands a task to somebody else, who then owns the approval.
Add Task Approver Inserts another approver before, after, or alongside the current one.
Withdraw Task Takes back a task that was already submitted. With no task named it withdraws from the start node, which pulls the whole request back to the applicant.
Reactivate Workflow Node Restarts a workflow instance at a chosen node, which is how a finished or stuck approval is put back in motion.
End Workflow Instance Ends a workflow instance wherever it has reached. The record survives and the approval stops.
List Carbon Copies Returns the workflow instances copied to a member for information rather than for approval.

Contacts

Get Member Returns one member of the organization. Jodoo identifies a member by their member number rather than by an email address.
List Department Members Returns the members of a department, optionally walking the whole tree beneath it.
Create Member Adds a member to a department. A member created this way is activated immediately with single sign-on and counts toward the account's licensed users.
Update Member Changes a member's name or departments. The department list is replaced rather than added to.
Import Members Adds or updates many members in one call, each with their name, number and departments.
Delete Member Removes a member from the organization, which frees their licensed seat.
Delete Members In Batch Removes several members from the organization at once.
Create Department Adds a department. Leaving the parent empty puts it under the root.
Update Department Renames a department or moves it under a different parent.
Import Departments Creates or updates many departments in one call, which is how a whole organization chart is loaded.
Delete Department Deletes a department. Its members stay in the organization without it.

Roles

List Roles Returns the organization's roles. The limit defaults to one if it is not given, which is worth setting deliberately.
Create Role Creates a custom role inside a role group.
Update Role Renames a custom role or moves it to another role group.
Delete Role Deletes a custom role. Anything that granted permission through it stops doing so.
Add Members To Role Gives a custom role to members, which is how permission is granted in bulk.
List Role Groups Returns the role groups, which are how Jodoo organizes roles.
Create Role Group Creates a role group.
Update Role Group Renames a role group.
Delete Role Group Deletes a role group.

Usage and Audit

Get Platform Usage Returns the whole account's resource usage for a day.
Get App Usage Returns per app resource usage for a day, which is how a chargeback or a cleanup flow finds the expensive apps.
Get Member Usage Returns per member resource usage for a day.
Get Audit Log Types Returns the audit log scopes that can be queried. Run it first, because the scope on the log read must be one of these.
Get Audit Logs Returns audit log entries for a scope and a time range, paging by a cursor from the previous answer.

Frequently Asked Questions

What can FlowRunner do with Jodoo?

FlowRunner agents can run List Apps, List Forms, and Get Form Fields in Jodoo, plus 50 more actions.

Does connecting Jodoo to FlowRunner require OAuth?

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

Can Jodoo trigger a FlowRunner workflow automatically?

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

Start building with Jodoo

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us