--- title: "Formspree Integration" description: "Work with Formspree form submissions. Agents submit entries to a form endpoint and read stored submissions and forms through the management API." url: https://flowrunner.ai/integrations/formspree date_modified: 2026-08-04T10:04:16-07:00 --- # Formspree [Forms](https://flowrunner.ai/integrations/category/documents-forms) Work with Formspree form submissions. Agents submit entries to a form endpoint and read stored submissions and forms through the management API. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 3 actions · API key · available [Formspree website](https://formspree.io/) · [Platform Documentation](https://help.formspree.io/hc/en-us) · Capability data verified 2026-07-28 1. A batch of captured leads sits in a spreadsheet, collected from an event or a partner handoff 2. The agent reads the pending rows and maps each one to the form's field names 3. Each mapped entry is validated for a well-formed email and the required fields before anything sends 4. The ops owner reviews a rendered sample of the batch, including the \_subject and \_replyto values, and approves the run 5. Submit Form relays each entry to the Formspree endpoint, firing the form's configured notifications and integrations 6. The agent inspects each response, treating ok as success and routing any errors array to a retry queue 7. A run summary posts to the team channel with counts of sent, failed, and retried entries ## What This Integration Enables Formspree's whole premise is that the form backend should be someone else's problem: point a form at an endpoint and the notifications, integrations, and spam filtering are handled. This connector extends that premise to your agents. Anything a workflow captures, a chat conversation, a spreadsheet of event leads, a record assembled from three other systems, can be relayed through Submit Form and picked up by everything the form already triggers. One honest caveat, stated plainly because it matters to how you build: Submit Form is the core, reliable operation. List Submissions and List Forms use Formspree's management API, which is limited and lightly documented, so verify them against your own account and plan before a workflow depends on them. Build your flows submission-first. - Relay data from any workflow into a Formspree endpoint, with Formspree special keys like \_subject, \_cc, and \_replyto supported, plus the \_gotcha honeypot for spam discipline - Fall back to a configured Default Form ID so flows do not hard-code endpoints, and swap target forms per environment without touching the flow logic - Handle validation failures explicitly instead of losing them - Read stored submissions and list forms where your plan exposes the management API ### Without FlowRunner **Form plumbing rebuilt per source**: The Formspree form has notifications, integrations, and spam protection configured, and every non-website lead source bypasses all of it **Batch relays as an act of faith**: Someone posts entries at an endpoint and assumes they arrived, with no record of which succeeded **Submissions stranded in the dashboard**: Stored entries live in Formspree and reach the CRM only when someone exports them ### With FlowRunner **One endpoint, every source**: Chat leads, sheet imports, and workflow output all relay through Submit Form and inherit the form's configured behavior **Every response accounted for**: ok and errors are handled explicitly, failures retry, and the run summary says exactly what happened **Stored entries pulled into the flow**: Where your plan exposes the management API, agents read submissions back and sync them onward ## Use Case Scenarios ### The event lead list that flows through the real pipeline After a conference, three hundred scanned leads sit in [Google Sheets](https://flowrunner.ai/integrations/google-sheets). Instead of importing them into the CRM cold, the agent relays each row through Submit Form so every lead fires the form's configured notification and downstream integrations, exactly like an organic website inquiry. The ops owner approves the mapped batch before it runs, each response's ok flag is logged back to the sheet, and the handful of rows with malformed emails come back as an errors array instead of vanishing. ### The static site that gained a workflow A marketing microsite built on a static host uses Formspree as its form backend. FlowRunner watches for new entries, on plans exposing the management API via List Submissions, or via the form's notification email parsed from [Gmail](https://flowrunner.ai/integrations/gmail-service), and syncs each submitter into [HubSpot](https://flowrunner.ai/integrations/hubspot) as a contact. A summary of the day's inquiries posts to [Slack](https://flowrunner.ai/integrations/slack). The microsite stays static and simple; the intelligence lives in the flow behind it. ### Internal tools that file reports through a form An internal agent that monitors infrastructure or reconciles data needs somewhere to file structured findings where people already look. Submit Form gives it one: the agent posts each finding with a descriptive \_subject and the details as fields, and Formspree's notification routing delivers it to the right inbox. When a finding is resolved, a confirmation entry follows. No new notification system to build, no distribution list to maintain, no webhook receiver to host; the form backend the team already trusts carries the traffic, and changing who gets notified stays a Formspree setting rather than a code change. ## Human-in-Loop Highlight Submit Form dispatches email the instant Formspree accepts it: the form's notification recipients, any \_cc addresses in the payload, and, on forms with autoresponders, a reply straight to the submitted \_replyto address. None of that can be pulled back, and at batch scale a bad mapping multiplies into hundreds of misdirected messages, some landing in the inboxes of the very leads you meant to impress. That is why FlowRunner batch relays stage first: the agent maps every row, sends nothing, and presents rendered samples with the special keys visible to the ops owner through a [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step. Approval releases the run; each response is then checked and logged individually. A single entry generated by a live workflow flows straight through, because that is the organic case the form was built for. Volume waits for a person, because volume is where an error stops being a typo and becomes an incident. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 3 actions ### Submissions 1 - **Submit Form** Submits data to a Formspree form endpoint. Pass the form fields as a JSON object, arbitrary fields plus Formspree special keys such as \_subject, \_cc, \_replyto, and \_gotcha. The Form ID falls back to the configured Default Form ID when omitted. Returns ok and next on success; validation problems return an errors array. This is the core, reliable Formspree operation and the one to build flows around. ### Management 2 - **List Submissions** Retrieves stored submissions for a form via Formspree's read and management API, authenticated with your API key. Best-effort: the management API is limited and lightly documented, and the exact endpoint and response shape may differ by account and plan, so verify against a live account before a workflow relies on it. - **List Forms** Lists the forms in your Formspree account via the read and management API, authenticated with your API key. Best-effort with the same caveat: confirm behavior on your plan before depending on it. ## Frequently Asked Questions ### What can FlowRunner do with Formspree? FlowRunner agents can run Submit Form, List Submissions, and List Forms in Formspree. ### Does connecting Formspree to FlowRunner require OAuth? No. Formspree connects to FlowRunner with an API key, no OAuth flow required. ### Can Formspree trigger a FlowRunner workflow automatically? Formspree doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Formspree?** This integration exposes Formspree 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/formspree. Site index: https://flowrunner.ai/llms.txt