Resources · n8n integration

Form.io n8n integrationAutomate Form.io with n8n.

A submitted form should start the work, not wait in a list. The Form.io n8n integration arrives through a trigger node that listens over webhooks, with 2 events across 2 families: a submission created, a submission updated. It suits teams who already collect structured data in Form.io and want n8n to carry the rest.

Try the Form.io integration on n8n

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Form.io n8n integration actually give you?

The Form.io n8n integration links one Form.io form to an n8n workflow through the Form.io Trigger node, version 1. It listens over a webhook, meaning a URL that Form.io calls as soon as something happens on that form, so n8n never has to ask for news. Two events are available: one for a submission that has just been sent, one for a submission that has been edited.

The first build most teams put together is a spreadsheet mirror. Submission Created fires, n8n reads the incoming item, and a node such as Google Sheets appends one row per response. No end-of-week export, and the sheet is already the shared view the rest of the company keeps asking for.

Notification is the second pattern. A form that feeds a real process needs a human at the other end, so the trigger output goes straight to Slack, with a message built from the values you map yourself using an expression like {{ $json.field }}. The person who picks up the case reads the answer in the channel, not in a dashboard they have to open.

The third one keeps a durable record. In Airtable, each submission becomes a record, and Submission Updated keeps that record aligned when the form is edited later. Two triggers, or one trigger with both events ticked, cover the whole life of the entry.

Anything else you need from the Form.io API goes through the HTTP Request node. It calls any endpoint and reuses the same credential through predefined authentication, which keeps one connection for the whole workflow instead of two. That pairing is worth knowing early, because it decides whether a workflow stays in one branch or splits.

One detail shapes every design: the Form.io Trigger points at one project and one form, both picked from dropdowns fed by the credential. Decide which form deserves its own workflow before you start wiring nodes, since that choice sets the scope of everything downstream. Teams new to n8n itself can start with the n8n training, and the n8n review covers the platform side of the decision.

Connect

How do you connect Form.io to n8n?

  1. 01

    Create the Form.io credential

    Open the Credentials menu in n8n and create a Form.io credential. A credential is stored once on the instance and reused by every workflow that needs it, so this step happens a single time even if ten workflows end up listening to forms. Back in the Form.io Trigger, that credential shows up in the node's dropdown and you select it there.

  2. 02

    Pick the project and the form

    Project Name or ID and Form Name or ID are both required. Each one is a dropdown filled from the credential you just selected, and each one also accepts an identifier passed through an expression when the value comes from an earlier node or a variable, in the {{ $json.field }} form. The form you choose here is the one whose submissions reach the workflow.

  3. 03

    Tick the events and activate

    Trigger Events holds the 2 events, Submission Created and Submission Updated. Tick the ones the workflow should react to. Activating the workflow is what registers the webhook URL on the Form.io side, so activation is a configuration step, not a formality: until the workflow is active, the URL that receives submissions does not exist yet.

Triggers

What fires a Form.io workflow?

Form.io Trigger is the node that starts a workflow when something happens in Form.io. It listens to 2 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your Form.io account.

What you see in n8n

Every event, by family

One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.

create.*1
  • create.
    • create
update.*1
  • update.
    • update

Configuration notes

01Configure the Form.io TriggerThe Form.io Trigger is where the workflow starts. It carries the connection, the form being watched and the list of events, and version 1 of the node works over a webhook, so Form.io pushes to n8n rather than n8n polling Form.io.

The Form.io Trigger is where the workflow starts. It carries the connection, the form being watched and the list of events, and version 1 of the node works over a webhook, so Form.io pushes to n8n rather than n8n polling Form.io.

Key parameters

  • Project Name or ID: required. Choose the Form.io project in the list, or pass its ID with an expression such as {{ $json.field }} when it comes from an earlier node.
  • Form Name or ID: required. Same logic one level down, the form whose submissions feed this workflow.
  • Trigger Events: the events to watch, 2 of them, ticked one by one.
  • Simplify: on, the node returns a simplified version of the response; off, the raw data reaches the next node untouched.
When to use it
every Form.io workflow opens with this node. Set the parameters, activate, then submit a test entry to see the real shape of the data before building the rest.
02Submission CreatedFires when a new entry is sent on the form you selected. One submission, one execution, and the submitted values arrive as the item that the following nodes read.

Fires when a new entry is sent on the form you selected. One submission, one execution, and the submitted values arrive as the item that the following nodes read.

Key parameters

  • Trigger Events: tick Submission Created alone when only new entries matter and a later edit should stay invisible to the workflow.
  • Simplify: leave it on for a quick mapping, turn it off when the next node needs the raw data exactly as it came in.
Use cases
a contact request that has to reach the right person while the visitor is still on the page, an application form that opens a record as soon as it lands, a registration that adds a line to a shared sheet. Each value is read with an expression like {{ $json.field }}, and a test run tells you the exact names to use.
03Submission UpdatedFires when an existing entry is edited. The workflow runs again on the same submission, which is what keeps a copy stored elsewhere aligned with what Form.io holds.

Fires when an existing entry is edited. The workflow runs again on the same submission, which is what keeps a copy stored elsewhere aligned with what Form.io holds.

Key parameters

  • Form Name or ID: the edited entries only come from this form, so a second form under review needs its own trigger.
  • Trigger Events: tick it next to Submission Created when one workflow should handle both the arrival and the correction.
Use cases
a request corrected by the person who sent it, a case file completed later by an operator, a form reopened after a review. With both events on, add a branch that compares the values you care about, using {{ $json.field }}, so the workflow reacts to a real change rather than to every save.
Need help

Need help automating Form.io with n8n?

A person reads every message.

FAQ

Form.io and n8n: common questions

01Is the Form.io n8n integration free?
Yes on the n8n side. The Form.io Trigger ships with n8n, so there is nothing to install and nothing extra to pay for the node itself. It behaves the same on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance under the Community Edition and its Sustainable Use license. The workflow you build is identical in both cases, which matters if you prototype on Cloud and move to your own server later. What a Form.io plan costs on its own side is a separate question and is not covered here.
02What credentials does the Form.io Trigger need?
A Form.io credential, created once in the Credentials menu of n8n and then reused by every workflow on the instance. You never paste it into the node itself: the Form.io Trigger shows the saved credentials in a dropdown and you pick one. Once the credential is selected, the two required parameters become usable, since Project Name or ID and Form Name or ID are dropdowns filled from the connection. Both are required, so the node refuses to run while either one is empty, and both also accept an identifier passed through an expression.
03What if a workflow needs more than these 2 events?
Then it goes through the HTTP Request node. This is the standard answer in n8n whenever something sits outside the catalog of a dedicated node: HTTP Request calls any endpoint of the Form.io API and reuses the same credential through predefined authentication, so there is no second connection to manage. In practice a workflow often mixes both, with the Form.io Trigger as the entry point and one HTTP Request step further down the chain. The trigger itself watches one project and one form at a time, so several forms mean several triggers.
04Does the Form.io Trigger react in real time?
Yes. The node works over a webhook, which means a URL that Form.io calls on its own as soon as an event happens on the watched form. There is no polling and no interval to configure, and each event reaches n8n in a matter of seconds. The URL is registered with Form.io when the workflow is activated, so activation is the moment the connection actually starts to listen. One practical consequence: a submission sent while the workflow is switched off does not queue up somewhere waiting for you to turn it back on.
05n8n or Make for Form.io?
It depends on four criteria, and both tools handle the job. Hosting comes first: n8n runs on your own server through Docker or npm, or on n8n Cloud, while Make is hosted only. Data control follows from that, since a self-hosted instance keeps submission content inside your own perimeter. The cost model differs too: Make is billed per operation, which shows up quickly on forms that fire often. Visual logic is the fourth, and it is mostly a matter of habit. Try the trigger on one form in each tool before committing the whole process.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations