Reference · Tools
Formstack Trigger
Starts workflow when a Formstack form is submitted
The Formstack Trigger node fires a workflow the moment someone submits a Formstack form, passing along every field value, field type, the form ID, and a unique submission ID. Use it to build things like automatic lead routing when a contact form is submitted or instant Slack alerts when a survey response comes in. A simplify mode (on by default) flattens nested field objects into plain key-value pairs so downstream nodes can read data without extra transformation steps.
- Node type
- Webhook trigger
- Parameters
- 2
- Outputs
- Output
- Credentials
- Formstack
Formstack Trigger
Trigger on Formstack form submission
Overview
Triggers a workflow when a respondent submits a Formstack form. Receives the webhook payload from Formstack containing form submission data with field values, field types, the Form ID, and the unique submission ID. Supports a simplify mode that flattens nested field value objects into plain key-value pairs for easy downstream processing. Formstack registers webhooks via its REST API v2 with JSON content type, standardized field values, and field type metadata included.
Category: Utility
Tool Name: formstack_trigger
Version: 1
Appearance: Icon: si-formstack | Color: #21b573
Node Type
Trigger — webhook (receives incoming HTTP callbacks)
Input / Output
| Direction | Port(s) |
|---|---|
| Input | None (trigger node) |
| Output | Output |
Credentials
This tool requires Formstack credentials. See the Credentials Guide for setup instructions.
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| Form ID | string | Yes | — | The ID of the Formstack form to monitor for new submissions. Find the form ID in your Formstack dashboard URL or form settings. |
| Simplify | boolean | No | true | Whether to return a simplified version of the response instead of the raw data. When enabled, nested field value objects like { value: “John”, type: “text” } are flattened to just the value (“John”). |
Output Data
Each submission delivered by Formstack produces one output item. The submitted answers are copied onto the item as top-level properties, and four fields are added:
_trigger— alwaysformstack_webhook_timestamp— ISO 8601 timestamp of when the request arrived_webhookEvent— alwaysform_submission_formId— the submitted form’s ID, taken from the payload’sFormID_submissionId— the unique submission ID, taken from the payload’sUniqueID
Answer keys are the form’s field labels wherever the label is known; otherwise they stay in Formstack’s raw field_<id> form.
With Simplify on (the default) each answer is the plain value, so a name field reads {{ $json["Full Name"] }}. With Simplify off the answer stays as the object Formstack sent — { "value": "John", "type": "text" } — and is read as {{ $json["Full Name"].value }}.
File-upload fields pass through as the storage URL Formstack recorded; they are not downloaded as binary data.
Usage Examples
- Trigger a workflow when someone submits a contact form on Formstack
- Capture Formstack form submissions and store responses in a database
- Start a workflow when a new application is submitted via Formstack
- Collect form data from Formstack and send notification emails
Example Configuration
Fire on every submission of one form, with flattened answers:
{
"type": "formstack_trigger",
"parameters": {
"formId": "5551234",
"simple": true
}
}
Keep the raw field objects, including each answer’s field type:
{
"type": "formstack_trigger",
"parameters": {
"formId": "5551234",
"simple": false
}
}
Trigger Behavior
- Activation: When the workflow is activated, a webhook endpoint is registered with the service.
- Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
- Payload: The incoming webhook payload is parsed and output as workflow items.
- Verification: Supports signature verification where applicable.
Tips
Connects to Formstack via webhook. When a respondent submits the specified form, Formstack sends the submission data to this trigger. Configure the Form ID to watch. Enable Simplify mode (default) to flatten nested field value objects into plain values. The trigger receives JSON payloads with standardized field values and field type metadata.
Frequently asked questions
What data does the node actually receive when a form is submitted?
The node receives a JSON webhook payload from Formstack containing the submitted field values, the type of each field, the Form ID, and a unique submission ID. With Simplify mode enabled (the default), nested field value objects are flattened into plain key-value pairs. With it disabled, you get the raw nested structure Formstack sends.
What credentials do I need to connect this node to Formstack?
You need a Formstack credential configured in BusyBot using the formstackApi credential type. This allows BusyBot to register the webhook with Formstack's REST API v2 on your behalf — you don't have to manually set up the webhook endpoint in Formstack yourself.
Do I need to configure anything in Formstack's own dashboard to make this work?
No. BusyBot registers the webhook automatically with Formstack via the REST API v2 when you activate the workflow. The webhook is set up to use JSON content type with standardized field values and field type metadata included. You only need to supply the Form ID inside the node configuration.
When should I turn off Simplify mode?
Turn off Simplify mode if you need access to the full nested field value structure that Formstack sends — for example, if you need to distinguish between a field's raw value and its display label, or if a downstream node expects the original Formstack payload shape. For most straightforward use cases like writing values to a spreadsheet or database, Simplify mode on is the easier path.
Does this node support multiple forms, or only one at a time?
Each Formstack Trigger node watches a single form, identified by the Form ID parameter you configure. If you need to trigger workflows from multiple Formstack forms, add a separate Formstack Trigger node for each form.
Build with the Formstack Trigger node
Drop it into a workflow, wire it to an agent, or call it on a schedule. You'll need Formstack credentials first.
Open BusyBotLast updated . Spotted something wrong? Tell us.