--- title: "Tally Integration" description: "Connect AI agents to Tally forms. Agents create and update forms, list questions and submissions, manage webhooks, and react the moment a new submission arrives, routing respondent answers into the rest of your stack." url: https://flowrunner.ai/integrations/tally date_modified: 2026-08-01T02:40:32-07:00 --- # Tally [Forms](https://flowrunner.ai/integrations/category/documents-forms) Connect AI agents to Tally forms. Agents create and update forms, list questions and submissions, manage webhooks, and react the moment a new submission arrives, routing respondent answers into the rest of your stack. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 1 trigger · 15 actions · API key · available [Tally website](https://tally.so/) · [Platform Documentation](https://developers.tally.so/) · Capability data verified 2026-07-22 1. On New Submission fires the moment a respondent completes the intake form 2. List Form Questions maps question IDs to their titles so answers read as data, not hashes 3. The mapped answers land in the destination system, a CRM record, a sheet row, a project task 4. Agent classifies the submission, a qualified lead, a support request, a vendor application 5. The owning team's channel gets the respondent's key answers and the classification 6. Submissions the classifier is unsure about, or that request something sensitive, wait for a person to route 7. The confirmed routing completes, and the flow logs where every submission went ## What This Integration Enables A form is a promise that someone will act on the answer, and most form stacks break that promise at the handoff: submissions pile up in a dashboard nobody watches. Tally's API is unusually complete for a form builder, forms, questions, submissions, and webhooks are all programmable, which lets FlowRunner treat it as a full intake system rather than a data trap. Agents react to submissions in real time, and can even build and publish the forms themselves. - Route new submissions into spreadsheets, CRMs, and databases the moment they arrive - Push respondent answers to team channels for immediate follow-up - Create, publish, and update forms programmatically as campaigns and processes change - Map question IDs to human-readable titles when interpreting responses - Manage webhooks and run supervised submission cleanup across the account The destructive end of that API surface, permanent submission deletion, is exactly where FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step holds the line. ### Without FlowRunner **Submissions wait in the dashboard**: Someone checks Tally when they remember to, and a Tuesday submission gets a Friday reply **Answers arrive as question IDs**: Exports key answers by opaque IDs, so every integration starts with a manual mapping exercise **Old respondent data lingers**: Submissions containing personal data sit in forms indefinitely because purging is manual and scary ### With FlowRunner **Submissions become action in seconds**: The trigger fires on completion, and the answers are in the CRM, the sheet, and the team channel before the respondent closes the tab **Answers arrive labeled**: Agents join responses to question titles automatically, so downstream systems get readable fields **Retention runs as a supervised purge**: Agents propose exactly which submissions age out, and a person approves before anything is permanently deleted ## Use Case Scenarios ### Intake to CRM before the respondent closes the tab A lead-qualification form fires On New Submission. The agent maps the answers via List Form Questions, scores the lead from the responses, writes the record into the CRM, and posts the summary with the signed submission preview link to [Slack](https://flowrunner.ai/integrations/slack). High scorers get routed to a rep immediately; the rest enter the nurture flow. The gap between someone raising a hand and someone shaking it drops from days to minutes. ### The incremental sync that never re-reads everything An operations form collects vendor invoices and requests. On a schedule, the agent calls List Submissions with the after-submission-id filter, so each run picks up only what is new, and appends each mapped submission to [Google Sheets](https://flowrunner.ai/integrations/google-sheets) while archiving the full record to [Notion](https://flowrunner.ai/integrations/notion). Completion-status filters let partial submissions route to a follow-up nudge instead of the main pipeline. ### Forms that build themselves for each campaign A new event needs a registration form. The agent assembles the block structure from the event brief, calls Create Form as a draft in the right workspace via List Workspaces, and posts the preview for review. On approval, Update Form flips the status to Published and Create Webhook wires submissions to the processing endpoint. When registration closes, the same flow unpublishes the form. Nobody clones last event's form and forgets to change the date. ## Human-in-Loop Highlight Delete Submission is permanent: the API cannot restore a deleted response, and unlike Delete Form there is no trash to recover from. The flow that needs it is real, a privacy policy that promises respondent data is purged after ninety days, but a retention sweep that runs unsupervised is one filter bug away from destroying the submissions that were still feeding open work. So the FlowRunner sweep separates selection from destruction. The agent runs List Submissions with the date window, cross-checks that no selected submission is referenced by an open record downstream, and posts the proposal: "Vendor application form, 118 submissions older than 90 days, 3 excluded because their applications are still open. Purge 115?" A person confirms, the agent deletes and logs each ID as evidence the retention promise was kept. The same gate guards Update Form when the status flips to Published, because publishing puts an agent-built form in front of the public under your name. 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 15 actions ### Forms 5 - **List Forms** Retrieves the account's forms with status, submission count, and whether each is closed for responses, paginated up to 500 per page. - **Get Form** Retrieves one form's settings and complete block structure. The starting point for programmatic edits. - **Create Form** Creates a form from an array of Tally blocks, as Published, Draft, or Blank, optionally in a specific workspace. The build step for campaign and intake flows. - **Update Form** Updates a form's name or status. Flipping status to Published makes the form live, which is why that transition is human-approved in FlowRunner flows. - **Delete Form** Moves a form and its submissions to the trash, restorable from the Tally dashboard. ### Questions 1 - **List Form Questions** Retrieves a form's questions with IDs, block types, titles, and field definitions. The mapping layer that turns submission payloads into readable data. ### Submissions 3 - **List Submissions** Retrieves a form's submissions with completion-status filters, date windows, and after-submission-id incremental fetching, including signed preview and PDF links. - **Get Submission** Retrieves one submission with all responses and the form's questions for mapping, plus signed preview and PDF links. - **Delete Submission** Permanently deletes a submission. Cannot be undone. The operation this page's human gate exists for. ### Webhooks 4 - **List Webhooks** Retrieves webhooks across accessible forms and workspaces, with endpoint, event types, headers, and enabled state. - **Create Webhook** Creates a webhook that POSTs each new submission to an endpoint, with optional payload signing and custom headers. For FlowRunner flows, the On New Submission trigger covers this without managing endpoints. - **Update Webhook** Updates a webhook's full configuration, including toggling it off to pause deliveries without deleting it. - **Delete Webhook** Deletes a webhook so submission events stop flowing to its endpoint. ### Account 2 - **Get Current User** Retrieves the API key owner's profile, including subscription plan. Used to verify the connection and plan-dependent capabilities. - **List Workspaces** Retrieves accessible workspaces with members and pending invites. Used to place new forms in the right workspace. ## Triggers 1 triggers ### Event Triggers 1 - **On New Submission** Fires in real time when a form receives a new submission, delivered via Tally's webhook infrastructure. The event that turns every form into a workflow entry point. ## Frequently Asked Questions ### What can FlowRunner do with Tally? FlowRunner agents can run List Forms, Get Form, and Create Form in Tally, plus 12 more actions. ### Does connecting Tally to FlowRunner require OAuth? No. Tally connects to FlowRunner with an API key, no OAuth flow required. ### Can Tally trigger a FlowRunner workflow automatically? Yes. Tally supports 1 trigger that can start a FlowRunner workflow automatically. **Work at Tally?** This integration exposes Tally 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/tally. Site index: https://flowrunner.ai/llms.txt