Form.taxi
FormsForm.taxi is a GDPR-compliant form backend for static websites. Agents submit entries, read stored submissions, create endpoints, and react to each new submission through a verified webhook.
What This Integration Enables
Form.taxi sells a specific absence: you do not run a server, and you do not hold the submission data yourself. That is the whole product, and it is why the API is deliberately small. There is no fetch-one route, no server-side search, and no delete. What Form.taxi does have is a GDPR-compliant endpoint that accepts a post from a page you published to a bucket, and an archive you can read back on the Standard plan and above.
FlowRunner agents work with that shape rather than against it. They read stored submissions a page at a time or walk the whole archive, filter locally on any field, pull attachments into storage before the links expire, and post new entries into the same pipeline from other systems so the notification and delivery rules apply to machine-originated data too. The connectors handle the paging and the signature checks. What they never do is decide what an inbound message means, which is where the human-in-the-loop step belongs.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
One callback URL, many client sites
An agency runs contact forms for a dozen client sites, all of them static. Each form's delivery settings point at the same FlowRunner callback URL, and the trigger fires only when a named field carries the expected client code, which is how one flow serves every site. On each delivery the agent verifies the token or the HMAC signature, reads the inputs map, calls Download Submission Attachments to capture any uploads, then writes the lead into HubSpot under the right client account and posts a summary to the client channel in Slack. Messages that fail verification never reach a downstream system.
-
The archive as a reporting source
On a schedule, the agent calls Get All Submissions with Since set to the previous run, which is the cheapest way to keep an external system in step. Each entry appends to a sheet in Google Sheets with the fields the site's own HTML named, and Get Form Details supplies the submission counters so the sheet can be reconciled against what Form.taxi actually holds. Because the archive is bounded by the plan's retention window, the same run copies attachments into Box rather than storing links that will expire.
-
Relaying entries from another system
A support agent handles a request that arrived somewhere else and should live in the same archive as the website's own messages. It calls Submit Form Entry against the form endpoint exactly as a browser would, so Form.taxi stores it, runs it through spam filtering, and delivers it through the form's configured email, webhook, and WhatsApp channels. Reply To and Subject are overridden for this one entry so the reply thread reaches the right person. When the request carries documents, Submit Form Entry With Files sends them as multipart data alongside the fields.
Human-in-Loop Highlight
Create Form Endpoint is the one operation here that provisions something rather than moving data, and it is unusual in three ways at once. It needs no credential, because the form code in the URL is the credential. The email address it takes doubles as the account username and as the destination for every notification that form will ever send. And an address already registered is refused rather than reused, while nothing anywhere in this connector deletes an endpoint or moves it to another account. So a provisioning agent builds the request and then stops: "About to create a Form.taxi endpoint for the Meridian rebuild, bound to [email protected] with notifications in German. This address becomes the account username permanently and cannot be reassigned from here. Confirm the address and the language?" The account manager confirms or corrects the address, and only then does the endpoint URL go into a page that will be published to a CDN.
Agent Capabilities
10 actionsReading Submissions
5- Get Submissions Reads one page of stored submissions, newest first, with the form details and the pagination counters. Used for incremental reads where a single page is enough.
- Get All Submissions Walks every page into one flat array up to a ceiling, and reports whether the list was exhausted or truncated. Used for exports and for keeping an external system in step.
- Get Submission By ID Returns a single submission by the id a webhook delivers. Form.taxi publishes no fetch-one route, so this searches the list and reports found or not found rather than failing.
- Search Submissions Finds submissions whose field values match a term, across one named field or every field. Matching runs in FlowRunner because Form.taxi has no server-side search.
- Get Form Details Returns the form's code, title, embedded URL, and the account's submission counters. The cheapest way to confirm the key, the form code, and the plan level before heavier steps.
Attachments
2- Download Attachment Fetches one attachment link into storage and returns a URL later steps can use. Attachment links are only valid inside the plan's archive retention window.
- Download Submission Attachments Finds a submission and downloads every file uploaded with it in one step, optionally restricted to a single upload field. Failed downloads are reported individually rather than aborting the rest.
Writing Entries
2- Submit Form Entry Posts a new entry to a form endpoint exactly as a browser would, so it is stored, spam-filtered, and delivered through the form's configured channels. Used to relay data collected elsewhere into the same pipeline.
- Submit Form Entry With Files Posts a new entry with attachments as multipart form data, downloading each file from the URL given for it. Used when a relayed request carries documents.
Provisioning
1- Create Form Endpoint Registers a new form endpoint and, when the address is unknown, the account that owns it. The operation this page's human gate exists for.
Triggers
2 triggersEvent Triggers
2- On New Submission Fires in real time when Form.taxi receives a submission on a form whose webhook delivery points at this flow. Setup is manual because Form.taxi has no webhook management API, and verification through the token or the HMAC signature should be switched on from the start.
- On New Submission (Polling) Checks the submissions API on a schedule and fires once per submission that appeared since the previous check. Use it when the form's single webhook slot is already pointed somewhere else, or when nothing should be pasted into the Form.taxi panel.
Frequently Asked Questions
What can FlowRunner do with Form.taxi?
FlowRunner agents can run Get Submissions, Get All Submissions, and Get Submission By ID in Form.taxi, plus 7 more actions.
Does connecting Form.taxi to FlowRunner require OAuth?
No. Form.taxi connects to FlowRunner with an API key, no OAuth flow required.
Can Form.taxi trigger a FlowRunner workflow automatically?
Yes. Form.taxi supports 2 triggers that can start a FlowRunner workflow automatically.
Other Forms integrations
Start building with Form.taxi
Free plan, no card required. Connect in minutes.