TriggerFormstackReal-timeUpdated May 2026
When does Formstack fire on new submissions?
Short answer: Drop the "Formstack → Formstack Submission (form.io)" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Formstack, not on a polling schedule.
Anatomy
What this trigger looks like in a workflow.
Drop it on the canvas. Configure a couple of fields. Publish.
In the builder
Trigger
Formstack Submission (form.io)
When the matching event happens
when form submittedon form submittednew form submittedwatch for form submittedwhen a new submission is received on form.io
What this trigger returns
for the curiousYou don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"form": "form_456","submission_id": "sub_123"}
Output shape
Fields available to downstream nodes.
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| form | string | "form_456" |
| submission_id | string | "sub_123" |
Pairs with
Drop these actions after Formstack Submission (form.io).
FAQ
Questions about Formstack Submission (form.io).
How does the Formstack Submission (form.io) trigger work in Formstack?
Fires within 5-15 seconds of someone submitting a Formstack form. Payload includes form ID, submission ID, responses keyed by field ID.
Is the Formstack Submission (form.io) trigger real-time?
Yes. Formstack Submission (form.io) uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Formstack.
What data does Formstack Submission (form.io) return?
The full event payload from Formstack. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.
Can I filter Formstack Submission (form.io) so only some events start a workflow?
Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.
Do I need Formstack admin permissions to use Formstack Submission (form.io)?
For most Formstack accounts a standard user can authorize the trigger. Some Formstack plans require an admin to enable third-party webhooks. Check Formstack's docs if the trigger fails to register.
Build a workflow on this trigger.
One trigger. 2+ downstream actions. Zero glue.
