Form.io
FormsManage Form.io forms, their field definitions, and the submissions collected against them, pushing external records in and reading submission data out to other systems.
What This Integration Enables
FlowRunner agents use Form.io to turn collected submissions into downstream action without manual data entry. An agent can read a form components array to learn the exact keys a submission uses, pull new submissions, and write them into a CRM, database, or notification system. It can push external records back into Form.io as submissions and keep field definitions in sync across environments. What it does not do is move every submission downstream unchecked. When a submission meets a condition that needs review, the agent stops and asks a person before it acts.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Submission-to-System Sync
A form collects records. On a schedule, the agent calls List Submissions to pull new entries, reads the form with Get Form to map the component keys, and writes each submission into the CRM or database. It posts a short summary of what it processed. The data lands in the right systems without anyone copying fields by hand.
External Records Into Form.io
Another system holds records that belong in Form.io. The agent reads them, maps them to the form component keys, and creates each one with Create Submission. The records are captured in Form.io consistently, keyed by the exact component keys the form expects.
Review-Gated Processing
A form captures requests, some of which need approval before anything happens. The agent reads each submission and checks it against the review conditions. Routine submissions flow into the downstream process. A submission that meets a review condition pauses and routes to the owner, who decides whether to approve, adjust, or reject it before the agent moves it on.
Human-in-Loop Highlight
When the agent reads a submission that meets a review condition, such as a request above a threshold or a field flagged as sensitive, it does not push it downstream. It pauses and routes to the owner through their preferred channel: "New submission on [Form] from [submitter] meets the review condition [reason]. View it here: [link]. Approve it to continue, adjust it, or reject it?" The owner decides, and only then does the agent move the submission into the next step. The submissions that carry a consequence get a human before the process runs.
Agent Capabilities
13 actionsForms
6- Create Form Creates a new form with its component definitions. Used to provision or replicate a form across environments.
- Delete Form Removes a form. Used in lifecycle cleanup.
- Get Form Returns a form and its components array. Used to discover the exact component keys a submission must use.
- List Form Actions Lists the actions configured on a form. Used to audit how a form routes its submissions.
- List Forms Lists the forms in a project. Used to inventory a project.
- Update Form Updates an existing form definition. Used to keep field definitions in sync.
Submissions
5- Create Submission Creates a submission with a data object keyed by component keys. Used to push an external record into Form.io.
- Delete Submission Removes a submission. Used in data governance workflows.
- Get Submission Retrieves a single submission. Used to read a captured record for downstream processing.
- List Submissions Returns submissions for a form. Used to pull new entries into other systems.
- Update Submission Updates an existing submission. Used to correct or enrich a captured record.
Roles and Connection
2- List Roles Lists the roles defined in a project. Used to audit access.
- Get Current User Returns the authenticated user. Used as a connection check that confirms the project URL and API key.
Start building with Form.io
$100 in credits. No card required. Connect in minutes.