Resources · n8n integration

Formstack n8n integrationAutomate Formstack with n8n.

A form submission is an event, so treat it like one. The Formstack n8n integration ships as a trigger node, version 1, with 2 fields to fill and 0 events to pick from. Submissions are the signal. What happens next is whatever the rest of your workflow does with them.

Try the Formstack integration on n8n

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Formstack n8n integration give you?

Formstack is a workplace productivity platform that helps organizations streamline digital work through no-code online forms, documents, and signatures. The n8n side of it is a single trigger node: it starts a workflow on a Formstack form submission, and the submission data becomes the first item every following node reads.

Take a lead capture form on a marketing site. The submission reaches n8n a few seconds after the visitor hits send, and the node right after the trigger writes a row into Google Sheets. The sales team reads one sheet instead of digging through a shared inbox.

Second pattern, internal requests. An equipment request or a day off form comes in, an If node reads one answer from the submission, the urgent ones get posted to a channel through Slack, and the rest land in a base in Airtable for someone to pick up later that day.

Third pattern, long free text. Research and support forms collect paragraphs nobody has time to read on arrival. Send the submission to OpenAI, ask for a two line summary and a category, then store both next to the original answer.

Worth knowing before you build: the catalog lists Formstack as a trigger node with 0 operations and 0 resources. When a workflow needs to call the Formstack API for anything beyond receiving submissions, the HTTP Request node reaches any endpoint and reuses the same predefined credential, so you stay in one workflow instead of scripting around it.

The field names inside a submission come from the form you built, not from a fixed list, and that shapes how you work. Map them once against one real submission that you send yourself and then reference them as {{ $json.field }} in the nodes that follow. If you are still sizing up the platform itself, the n8n review covers where it fits, and the n8n training walks through building a first workflow end to end.

Connect

How do you connect Formstack to n8n?

  1. 01

    Create the credential once

    In n8n, open the Credentials menu and create a credential for the Formstack Trigger node. A credential is the stored authentication n8n uses on your behalf: you save it one time, and it shows up in the dropdown of every workflow that needs it afterward. Nothing to install first, the node ships with n8n on Cloud and on a self hosted instance alike.

  2. 02

    Point the trigger at a form

    Drop the Formstack Trigger on the canvas, select the credential you just saved, then open Form Name or ID. Choose the form from the list n8n loads for you, or specify an ID with an expression, an expression being a small piece of code like {{ $json.field }} that reads a value from the item coming in. This field is required, so the node stops if it stays empty.

  3. 03

    Activate and send a test entry

    Save, then flip the workflow to active. n8n registers a webhook at that moment, which is a URL Formstack calls on its own whenever a form is submitted. Fill in the form yourself once and watch the execution appear a few seconds later. From there you know the exact shape of the data and can map the rest of the workflow against something real.

Triggers

What starts a workflow from Formstack ?

Formstack Trigger is the node that starts a workflow each time Formstack receives a new submission. Pick the form, activate the workflow: n8n registers the webhook on your Formstack account.

What you see in n8n

Configuration notes

01Form Name or IDThe trigger watches one form at a time, and this field decides which one. n8n queries the connected account and lists the forms so you can pick by name, which saves you from hunting for an identifier in the Formstack interface.

The trigger watches one form at a time, and this field decides which one. n8n queries the connected account and lists the forms so you can pick by name, which saves you from hunting for an identifier in the Formstack interface.

Key parameters

  • Form Name or ID: required, the Formstack form to monitor for new submissions. Choose from the list, or specify an ID using an expression such as {{ $json.field }} when an earlier node decides which form matters for this run.
Use cases
one workflow per form is the readable option when each form feeds a different process, a contact form to sales, an application form to recruiting. The expression route pays off in the opposite case, when a parent workflow already knows the form identifier and calls a shared routine with it.
02SimplifySubmissions can arrive two ways. Left off, the trigger hands over the raw data as it comes. Switched on, Simplify returns a simplified version of the response instead, which is usually what you want when the next node only needs the answers.

Submissions can arrive two ways. Left off, the trigger hands over the raw data as it comes. Switched on, Simplify returns a simplified version of the response instead, which is usually what you want when the next node only needs the answers.

Key parameters

  • Simplify: optional boolean, whether to return a simplified version of the response instead of the raw data.
When to use it
turn it on while you are mapping answers into a spreadsheet or a message, because shorter items are easier to read in the execution view. Leave it off when the workflow needs everything the submission carries, or when you plan to archive the payload exactly as it was received and want nothing dropped on the way in. Switching the box after a workflow is live changes the items the next nodes read, so check the mapping again.
03Activate the Workflow WebhookThere is no schedule behind this trigger and no interval to tune. n8n registers a webhook with Formstack when the workflow is activated, a webhook being a URL the tool calls by itself, and each submission arrives within a few seconds of being sent. Nothing checks for new entries on a timer.

There is no schedule behind this trigger and no interval to tune. n8n registers a webhook with Formstack when the workflow is activated, a webhook being a URL the tool calls by itself, and each submission arrives within a few seconds of being sent. Nothing checks for new entries on a timer.

When to use it
anything where the delay is visible to a human. A confirmation message, a routing decision, a task created for the person on duty. Because activation is what puts the webhook in place, plan a short live test after every change: activate, submit the form once yourself, confirm the execution shows up in the list, then hand the workflow over to the people who will rely on it every day.
Need help

Need help automating Formstack with n8n?

A person reads every message.

FAQ

Formstack and n8n, the questions that come up

01Is the Formstack n8n integration free to use?
Yes on the n8n side. The Formstack Trigger ships with n8n, so there is nothing to install and no extra cost for the node itself, whether you run n8n Cloud or self host it with Docker or npm under the Community Edition and its Sustainable Use license. A workflow behaves the same in both setups, which means you can build on a local instance and move it later without rewriting anything. What a Formstack account costs is a separate question and depends on your plan there, so check it on their side before you plan a rollout across several forms.
02What credentials do you need for the Formstack Trigger?
One credential, created inside n8n before the trigger can list your forms. Open the Credentials menu and add a credential for the Formstack Trigger node: n8n's own form walks you through whatever fields that credential needs, so there is no guessing on your side. Once it is saved, the credential becomes available in the dropdown of every workflow afterward, so several form workflows share the same entry. Selecting it is also the fastest check that the connection works, since the Form Name or ID dropdown then fills with the forms from that account.
03What are the limits of the Formstack node in n8n?
The catalog lists a trigger and 0 operations, so the node is built around one thing: receiving form submissions. For anything else you want to do with the Formstack API inside a workflow, the HTTP Request node calls any endpoint directly and reuses the same predefined credential, which keeps the authentication in one place. The other practical point is the payload itself. Field names depend on the form you designed, so a workflow built against one form does not map automatically onto another. Use a real submission to map your fields, then reference them as {{ $json.field }} downstream.
04Does the Formstack Trigger react in real time?
Yes, it works on a webhook and not on a timer. When you activate the workflow, n8n registers a webhook URL with Formstack, and Formstack calls that URL each time someone submits the form. The execution starts within a few seconds, so there is no polling interval to set and no delay you have to trade against API calls. The condition is activation: a workflow sitting in draft has no registered webhook, so it receives nothing. Deactivate a workflow to edit it and the same rule applies until you switch it back on.
05n8n or Make for automating Formstack?
It depends on three things. Hosting first: n8n runs on your own server with Docker or npm, or on n8n Cloud, while Make is hosted only, so if form answers carry personal data that has to stay on infrastructure you control, that decides it quickly. Cost model second: Make bills per operation, which is predictable when volume is stable and less so when a form goes viral. Visual logic third: both build flows on a canvas, and the fair test is to rebuild your own form routing in each and see which one you read faster a month later.
Same platform

Other docs you might need on this stack.

Browse all integrations