--- title: "AidaForm Integration" description: "AidaForm is a form, survey, quiz and landing page builder from Bonn, Germany. Agents list the forms in an account, pull submissions with their answers, render a submission to PDF, Excel, CSV or JSON, and delete entries when a retention rule says so." url: https://flowrunner.ai/integrations/aidaform date_modified: 2026-09-04T19:08:45-07:00 --- # AidaForm [Forms](https://flowrunner.ai/integrations/category/documents-forms) AidaForm is a form, survey, quiz and landing page builder from Bonn, Germany. Agents list the forms in an account, pull submissions with their answers, render a submission to PDF, Excel, CSV or JSON, and delete entries when a retention rule says so. 2 triggers · 11 actions · API key · available [AidaForm website](https://aidaform.com/) · [Platform Documentation](https://aidaform.com/) · Capability data verified 2026-08-26 1. On New Response fires when an application form receives a submission 2. Get Response returns the answers as JSON, using the field names set in the form editor 3. Agent checks the required fields are present and the file uploads arrived 4. Export Response renders the submission as a PDF into FlowRunner file storage 5. The record and the PDF link are filed in \[Airtable\](/integrations/airtable) against the campaign 6. The reviewer receives the rendered application in a \[Slack\](/integrations/slack) thread 7. The reviewer decides whether this application advances or gets declined ## What This Integration Enables AidaForm is built for teams that design their forms once and then want the data out of the way. The vendor's API reflects that intent honestly: forms, quizzes, surveys, and landing pages are all built in the AidaForm editor, and the API publishes four routes whose entire purpose is to let the collected data leave. There is no create, no update, and no publish route for a form. There is exactly one write in the whole surface, and it is a delete. That shape decides what agents are good for here. FlowRunner agents list the account's forms, resolve one by title when the name arrives from a spreadsheet or a person rather than a picker, walk every page of a form's submissions, count entries in a window before deciding whether to process them, and render any single submission as a PDF, Excel workbook, CSV, HTML page, or JSON file into FlowRunner file storage. Those [connectors](https://flowrunner.ai/concepts/connectors) are built and verified against the vendor's official API, including the fact that AidaForm answers an unauthorized read with an empty body rather than an error, which is why every read here checks the shape of the response instead of trusting the status code. The one destructive call is where FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) discipline earns its place. ### Without FlowRunner **Data trapped behind the editor**: Responses live in AidaForm and reach the rest of the stack only when someone exports them by hand **Archiving is a manual habit**: Turning a submission into a filed PDF is a task that gets skipped whenever the week is busy **Retention by intention**: The policy says purge after a fixed window, but the purge only happens when someone remembers ### With FlowRunner **Responses leave on arrival**: Each submission is read, mapped, and routed to the system that acts on it as it lands **Archiving happens by default**: Every submission is rendered and filed before anyone looks at it, so the record exists first **Retention runs as a process**: The purge sweep runs on schedule, exports first, and stops at the one call that cannot be undone ## Use Case Scenarios ### The submission is filed before anyone reads it An application form receives an entry. On New Response fires, and the agent calls Get Response to pull the answers, then Export Response to render the same submission as a PDF carrying the questions alongside the answers. The PDF goes to FlowRunner file storage, the structured answers go into [Airtable](https://flowrunner.ai/integrations/airtable) as a record, and the reviewer gets the PDF attached to a message through [Gmail](https://flowrunner.ai/integrations/gmail-service). By the time a person opens it, the archival copy already exists, the record already has a row, and the reviewer's only job is the judgment call. ### A weekly export nobody has to run On a schedule, the agent calls Count Responses with a From date to see whether the campaign form collected anything worth processing this week. If it did, Get All Responses walks the marker cursor across every page and returns the week's entries as one array. Each entry appends to a reporting sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets), and a summary posts to the channel that owns the campaign. Nobody exports a CSV by hand, and the numbers come from the live account rather than a download that aged three days in someone's downloads folder. ### A retention sweep that exports before it destroys The data protection policy says candidate submissions are purged after a fixed window. On a schedule, the agent resolves the form with Find Form By Name, uses Get All Responses with a From boundary to identify everything past the window, and calls Export Response on each one so a rendered copy lands in [Dropbox](https://flowrunner.ai/integrations/dropbox-service) before anything is removed. Then it stops. The list of what would be deleted goes to the owner, along with the count and the archive location, and the agent waits. Delete Responses runs only after a person has looked at the list. ## Human-in-Loop Highlight Delete Response is the only write AidaForm's API offers, and it takes the submission, its answers, and every file uploaded with it. There is no restore, and the vendor answers a delete with an empty body whether or not anything was removed, so nothing downstream can confirm what happened after the fact. So the retention agent does the whole sweep and then stops one call short. It posts: "218 responses on Candidate Intake are past the 24 month window. All 218 are archived as PDFs in the shared drive. Deleting also removes the uploaded resumes, and AidaForm returns no confirmation either way. 12 of these are linked to cases still marked open. Purge all 218, purge 206 and hold the open cases, or hold everything for now?" The data protection owner answers in one reply, and Delete Responses runs against exactly that list. The agent did the identifying, the counting, and the archiving. The irreversible part belonged to a person. 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 11 actions ### Forms 3 - **List Forms** Returns every form, quiz, survey, and landing page in the account with its identifier, creation time, and title. Used at the start of any workflow that has to work out which forms exist before it acts on one. - **Get Form** Returns one form by its identifier. AidaForm has no single form route, so this reads the account list and selects the match, which means a wrong identifier raises a clear error instead of quietly returning nothing. - **Find Form By Name** Resolves a form by its title rather than its identifier, ranked best match first. Used when the form name arrives from a message, a spreadsheet, or a person, which is most of the time in practice. ### Responses 4 - **List Responses** Returns one page of a form's submissions with the count, total, and cursor for the next page. From and To narrow the window by submission time and accept an ISO date or an epoch value in either unit, because sending the wrong unit to AidaForm matches nothing rather than failing. - **Get All Responses** Walks every page of a form's submissions and returns them as a single array, following the cursor for you. Used for exports and reporting runs. Setting From to the last run is far cheaper than pulling the whole history each time. - **Count Responses** Reports how many submissions a form holds without downloading any of them. Used as the cheap first step of a scheduled workflow, so a run that has nothing to process can end immediately. - **Get Response** Returns one submission with its answers as JSON, ready to map onto the next step. The field names inside come from the form editor, so they differ from form to form. ### Export and Retention 3 - **Export Response** Renders one submission as a PDF, Excel workbook, CSV, HTML page, or JSON file, stores it in FlowRunner file storage, and returns a URL the next step can attach to an email, push to a drive, or hand to a signature service. The PDF carries the questions alongside the answers, which is what makes it usable as an archival record. - **Delete Response** Permanently removes one submission and every file uploaded with it. This is the only write in the AidaForm API and it cannot be undone, which is why it belongs behind a human decision rather than inside an unattended branch. - **Delete Responses** Removes several submissions of the same form in one step, which is what a retention policy needs. Each identifier is deleted individually because AidaForm has no bulk route, and the result reports what succeeded and what failed rather than stopping at the first problem. ### Direct Access 1 - **Make API Call** Sends an authorized request to any AidaForm API path for routes this connector does not name. Kept because the vendor's published specification covers only four routes and has been extended before without a new document. ## Triggers 2 triggers ### Event Triggers 2 - **On New Response** Fires when a form receives a new submission. AidaForm publishes no webhook management API, so this trigger polls the form and remembers what it has already emitted, which means a submission is delivered once even if AidaForm restates it. The first cycle records a baseline and fires nothing, so an existing backlog is never replayed. - **On New Form** Fires when a new form, quiz, survey, or landing page is created in the account. Used to register a newly built form with the rest of the stack automatically, for example by creating its destination sheet and its notification route before the first response arrives. ## Frequently Asked Questions ### What can FlowRunner do with AidaForm? FlowRunner agents can run List Forms, Get Form, and Find Form By Name in AidaForm, plus 8 more actions. ### Does connecting AidaForm to FlowRunner require OAuth? No. AidaForm connects to FlowRunner with an API key, no OAuth flow required. ### Can AidaForm trigger a FlowRunner workflow automatically? Yes. AidaForm supports 2 triggers that can start a FlowRunner workflow automatically. **Work at AidaForm?** This integration exposes AidaForm 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/aidaform. Site index: https://flowrunner.ai/llms.txt