DataForms.io

DataForms.io is a no-code form builder built around reusable templates. Agents create templates and fields, spin up live forms from them, read the entries those forms collect, and react to each new entry as it arrives.

Verified 1 trigger 20 actions API key available

DataForms.io website Platform Documentation Capability data verified 2026-08-26

A renewal date arrives and the same set of information has to be collected again

Create Form spins a live form out of the stored template and returns the public link

The link goes to the respondent through email or chat, with the record it belongs to

On Form Submitted returns the entry with its answers array keyed by field id

Agent confirms the required fields are answered and pulls each upload from its temporary URL before it expires

List Entries confirms which requests in this cycle are still outstanding

The process owner reads the entries that came back incomplete and decides whether to chase or accept

What This Integration Enables

DataForms.io is built around templates, not forms. The template holds the questions, the field types and the redirect behavior; a form is a disposable instance you generate from it whenever the same data is needed again. That distinction is the whole reason to automate it. Recurring collection work, vendor document refreshes, annual attestations, per-project intake, is exactly the shape of work where a person should not be rebuilding a questionnaire every cycle. FlowRunner agents read and write templates and their fields, create live forms with their public links, and pull entries back with answers resolved to the field ids that identify them.

This connector also carries its own evidence trail, which is unusual and worth knowing about. DataForms.io publishes a reference for thirteen routes; the rest exist and were confirmed against the live API, and each operation states which of the two it is. FlowRunner surfaces that distinction rather than smoothing it over, because a flow that deletes something the vendor documents nothing about is a flow that needs a person in it. That is what the human-in-the-loop step is for.

Without FlowRunner

The same request, rebuilt A recurring collection gets recreated by hand each cycle, and drifts a little every time

Links live in inboxes Whoever sent the form is the only person who knows who received it

Uploads that expire quietly A file answer is a link with a short life, and it goes stale before anyone opens it

With FlowRunner

One definition, many issues The template holds the questions, and each cycle creates a form from it with the same fields and the same ids

Links tracked against records The public URL comes back on creation and is written next to the record that needed the data

Files captured on arrival The agent downloads each upload in the same run that the entry lands

Use Case Scenarios

The annual attestation that issues itself

A compliance calendar in a spreadsheet holds the renewal date for every vendor. On a schedule, the agent reads the due rows from Google Sheets, calls Create Form against the attestation template for each one, and writes the returned public URL back to the row. The links go out over Gmail. As entries arrive, On Form Submitted fires and the agent marks the row complete. Nothing was rebuilt, and every form in the cycle carries identical fields, so the answers line up when the reporting runs.
An entry becomes a record, and the files land with it

On Form Submitted brings back an entry whose answers include a file upload. The agent calls Get Entry for the complete record, reads each answer's field id against List Template Fields so the values reach the right destination, and downloads every upload immediately, because a file answer arrives as a temporary link rather than a permanent one. The structured values create or update the contact in HubSpot, the documents are filed, and a summary posts to Slack for the team that owns the intake.
Template cleanup that does not take live forms with it

Templates accumulate. A quarterly sweep calls List Templates, then List Forms to work out which live forms descend from each one and List Entries to count what those forms have collected. Anything with no descendants and no entries is a clean candidate for removal. Anything with either is presented to the owner instead, because Delete Template is the one call on this connector whose blast radius the vendor does not describe. The agent produces the inventory. The person produces the decision.

Human-in-Loop Highlight

Delete Template is the operation that stops the sweep. DataForms.io publishes no reference page for the route, so while the connector confirmed it exists, the vendor documents nothing about what happens to forms already created from that template or to the entries those forms collected. That is not a small unknown. It is the difference between removing an unused draft and quietly taking down a live collection link along with the answers behind it. So the agent never runs it on its own conclusion. It posts what it can prove: "Template Supplier Onboarding v2 has 3 live forms created from it, one of which collected 41 entries in the last 60 days and is still accepting submissions at its public URL. DataForms.io does not document what deleting the template does to those forms or those entries. Delete it, or retire it by closing the forms instead?" The operations owner answers. The inventory work was the agent's. The irreversible call, on a route with no published contract, was 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

20 actions

Account

Get Current User Returns the account the API key belongs to, including the company id that owns the templates and forms a flow will work with. The natural first step when setting up a connection.

Templates

List Templates Returns the form templates in the account, each with its name, description, layout and redirect URL. The starting point for any flow that creates forms automatically.
Get Template Returns one template by id. Used to confirm a template still exists and to read the redirect URL that forms created from it will inherit.
Create Template Creates a reusable template that forms are then generated from. A new template has no fields yet, so it is normally followed by Create Template Field.
Update Template Updates a template. Only the values supplied change, so a redirect URL or a layout can be retargeted without touching anything else.
Delete Template Permanently deletes a template. The vendor documents nothing about the effect on forms already created from it, which is why this page's human gate exists.

Template Fields

List Template Fields Returns every field on a template with its type, label, parent section and type-specific configuration. This is how a flow discovers the field ids that appear in submitted entries.
Get Template Field Returns one field with its configuration. When the field is a section, the response also carries every field nested inside it.
Create Template Field Adds a field to a template. Reading an existing field of the same type first is the reliable way to copy the shape its configuration expects.
Update Template Field Updates a field's label, section, order or configuration. Supplying the configuration replaces it whole rather than merging, so a flow reads the field before writing it back.
Delete Template Field Removes a field from a template. Answers already collected against the field stay on their entries.

Forms

List Forms Returns the live forms in the account, each with the template it came from and the public URL respondents open. Used to find an existing form before creating a duplicate.
Get Form Returns one form with its public URL and submission settings. The natural follow-up to Create Form when the link is being handed to an email or chat step.
Create Form Creates a live form from a template and returns the public URL. The core action for automating a recurring data request, with settings for single-respondent and collaborative use.
Update Form Updates a form's headline, submission settings or redirect URL. The form's type cannot be changed here, so a standard form does not become a collaborative one.
Delete Form Removes a form and takes its public link offline immediately, so anyone still holding the URL can no longer submit. Read the entries you need first.

Entries

List Entries Returns the submissions collected across your forms, each with its answers, timestamps and the form it belongs to. The reporting and reconciliation read.
Get Entry Returns one submission with its full answers array. The natural follow-up to the trigger when the flow needs the complete record, including a file answer's temporary link.
Delete Entry Permanently deletes a submission and the answers stored on it. The action to reach for on a retention or erasure request.

Advanced

Custom API Request Sends any request to the DataForms.io API using the configured key, for the routes this connector does not wrap by name.

Triggers

1 triggers

Event Triggers

On Form Submitted Fires once for each submission a respondent completes, carrying the whole entry including its answers. DataForms.io publishes no webhook management API, so this trigger polls rather than receiving a push, and the first cycle records where the feed is without emitting anything. An existing backlog therefore does not fire the flow when it is switched on.

Frequently Asked Questions

What can FlowRunner do with DataForms.io?

FlowRunner agents can run Get Current User, List Templates, and Get Template in DataForms.io, plus 17 more actions.

Does connecting DataForms.io to FlowRunner require OAuth?

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

Can DataForms.io trigger a FlowRunner workflow automatically?

Yes. DataForms.io supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with DataForms.io

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us