--- title: "Formstack Integration" description: "Manage Formstack forms, submissions, fields, folders, and webhooks, and sync new submissions into a CRM, spreadsheet, or database as they arrive." url: https://flowrunner.ai/integrations/formstack date_modified: 2026-08-01T02:40:32-07:00 --- # Formstack [Forms](https://flowrunner.ai/integrations/category/documents-forms) Manage Formstack forms, submissions, fields, folders, and webhooks, and sync new submissions into a CRM, spreadsheet, or database as they arrive. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 1 trigger · 16 actions · API key · available [Formstack website](https://www.formstack.com/) · [Platform Documentation](https://developers.formstack.com/reference/api-overview) · Capability data verified 2026-08-12 1. On New Submission fires when a form receives a new entry 2. Agent calls Get Form to resolve the field-id-to-label mapping 3. Agent maps the raw submission values to their labels 4. Agent checks the mapped values against the conditions that require review 5. Agent writes routine submissions into the CRM, spreadsheet, or database 6. Agent posts the mapped submission to the team channel 7. A submission that meets a review condition is held for an owner before it moves downstream ## What This Integration Enables FlowRunner agents use Formstack to turn a form submission into correct downstream action. Because the V2025 API keys submission data by field id, an agent reads the form definition first, maps ids to labels, and then writes the labeled data where it belongs: a CRM, a spreadsheet, or a database. It can create forms and fields, register webhooks for real-time delivery, and seed a form with records from another system. What it holds back is the submission that needs a decision. When a mapped value meets a review condition, the agent stops and asks a person before it moves the submission on. ### Without FlowRunner **Field ids read by hand**: Staff match each numeric field id to its label to make sense of a submission **Manual downstream entry**: Someone retypes each submission into the CRM or database **No gate on sensitive entries**: Every submission moves downstream, including ones that should be reviewed ### With FlowRunner **Labels resolved automatically**: The agent pairs the submission with the form to map ids to labels **Submissions synced on arrival**: Each new submission is written to downstream systems the moment it fires **Review-worthy entries pause**: Submissions that meet a review condition stop for a human before they move ## Use Case Scenarios ### Submission-to-CRM Sync On New Submission fires. The agent calls Get Form to resolve the field-id-to-label mapping, maps the raw values, and writes a clean record into the CRM. It logs the submission in a tracking spreadsheet and posts a labeled summary to the team channel. The submission lands where it belongs, correctly labeled, without anyone decoding field ids. ### Seed a Form From Another System A list of contacts lives in a spreadsheet or database. The agent reads each row and calls Create Submission with an array of field and value pairs, keyed to the form fields. The records are captured in Formstack consistently, so a batch import does not depend on manual entry. ### Review-Gated Intake A form captures requests that sometimes need approval, such as a spend request above a limit or an intake with sensitive answers. The agent maps each submission and checks it against the review conditions. Routine submissions sync automatically. A submission that meets a condition pauses and routes to the owner, who approves, adjusts, or rejects it before the agent moves it downstream. ## Human-in-Loop Highlight When the agent maps a submission whose values meet a review condition, such as a requested amount above a limit or a field marked sensitive, it does not write it downstream. It pauses and routes to the owner through their preferred channel: "New submission on \[Form\] from \[submitter\] meets the review condition \[reason\]. Mapped values: \[summary\]. Approve it to continue, adjust it, or reject it?" The owner decides, and only then does the agent move the submission on. The entries that carry a consequence get a human before anything downstream runs. 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 16 actions ### Forms 5 - **Copy Form** Duplicates an existing form. Used to create a variant from a standard template. - **Create Form** Creates a new form. Used to provision a form programmatically before collecting submissions. - **Delete Form** Removes a form. Used in lifecycle cleanup. - **Get Form** Returns a form together with its field definitions, including each field id, label, and type. Used to map submission field ids to labels. - **List Forms** Lists the forms on the account. Used to inventory forms. ### Submissions 4 - **Create Submission** Creates a submission from an array of field and value pairs. Used to seed a form with records from another system. - **Delete Submission** Removes a submission. Used in data governance workflows. - **Get Submission** Retrieves a single submission, keyed by field id. Used to read a captured record. - **List Submissions** Returns submissions for a form. Used to pull new entries into downstream systems. ### Fields 2 - **Create Field** Adds a field to a form. Used to extend a form programmatically. - **List Form Fields** Returns the field definitions for a form. Used to build the field id to label mapping submissions need. ### Folders, Webhooks, and Confirmations 5 - **List Folders** Lists the folders that organize forms. Used to navigate the account structure. - **Create Webhook** Registers a webhook on a form so downstream automations react to each submission. Used to wire real-time delivery. - **Delete Webhook** Removes a webhook, given the form id and webhook id. Used to tear down an integration. - **List Webhooks** Lists the webhooks registered on a form. Used to audit delivery targets. - **List Confirmations** Lists the confirmation actions on a form. Used to inspect post-submission behavior. ## Triggers 1 triggers ### Event Triggers 1 - **On New Submission** Polls a form and emits each new submission as it arrives. The first poll records a watermark and emits nothing, so the existing backlog is not replayed. When it fires, agents resolve the field-id-to-label mapping, write the submission downstream, and hold any submission that meets a review condition for a person. ## Frequently Asked Questions ### What can FlowRunner do with Formstack? FlowRunner agents can run List Forms, Get Form, and Create Form in Formstack, plus 13 more actions. ### Does connecting Formstack to FlowRunner require OAuth? No. Formstack connects to FlowRunner with an API key, no OAuth flow required. ### Can Formstack trigger a FlowRunner workflow automatically? Yes. Formstack supports 1 trigger that can start a FlowRunner workflow automatically. **Work at Formstack?** This integration exposes Formstack to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/formstack. Site index: https://flowrunner.ai/llms.txt