Formcrafts

Formcrafts is a drag and drop form, survey and quiz builder from Dusseldorf, Germany. Agents read workspaces and forms, pull live responses, resolve them against the form definition, download respondent uploads, and react when a response arrives.

2 triggers 14 actions API key available

Formcrafts website Vendor Product Page Capability data verified 2026-08-26

A scheduled reporting load starts for the quarter's form responses

Get All Form Responses walks the date-based pagination until the form is exhausted

Get Form Responses With Labels re-keys the answers by the labels the form's author wrote

Get Form reports the form's own response count for comparison

The agent compares the two figures and reports the gap instead of reconciling it silently

The matched rows load into the reporting table with their visitor context attached

An analyst rules on the gap, because only a person can say whether the missing rows are test traffic

What This Integration Enables

Formcrafts is a form builder from Dusseldorf, and this connector reads it. That is the honest shape of it: fourteen operations, every one of them a read. Nothing here creates a form, edits a field, or writes an answer back. Take that as a feature rather than a gap, because it means a Formcrafts connection can be handed to an agent with no fear that a bad run rewrites a live form, and it means the entire design problem is the one that actually matters for a form tool: getting the responses out in a shape another system can accept.

That is where Get Form Responses With Labels earns its place. Formcrafts identifies fields on the wire by opaque identifiers, so the raw response is unreadable without the form definition beside it. This operation fetches the definition once, joins it against every response, and hands back flat records keyed by the label a person wrote in the builder, with multiple choice answers flattened to their labels, uploads to their file names, tables to rows, and addresses to full address strings. That is the difference between a load that a spreadsheet or a warehouse can accept and a job someone has to hand-map. The connectors resolve the shape; the human-in-the-loop step handles what the shape cannot tell you.

Without FlowRunner

Opaque field identifiers Responses arrive keyed on wire identifiers, and the mapping to real column names lives in someone's head

Pagination by hand Date-based paging means writing the before and after loop, and losing records that share a timestamp

Uploads left in the form tool Identity documents and signed contracts stay where they landed, unattached to any record

With FlowRunner

Answers keyed by label Each response arrives as a flat record named the way the form's author named it

The walk done for you The pagination is followed to exhaustion, deduplicated by identifier, and reported when cut short

Files attached to the record Uploads are downloaded with their original name and type and land beside the data they belong to

Use Case Scenarios

A quarter of responses into the warehouse

A reporting job needs every live response on the customer feedback form for the last quarter. Get All Form Responses walks the date-based pagination until the form is exhausted or the ceiling is reached, deduplicating by identifier so two submissions sharing a timestamp do not appear on both sides of a page boundary. Get Form Responses With Labels returns them keyed by label in readable text mode, and the rows load into Snowflake alongside the visitor context Formcrafts records: country, region, city, time spent on the form, and the page it was submitted from. Get Form supplies the form's own response count so the load can be checked rather than assumed.
Document intake with the file attached

An onboarding form collects an identity document. On New Form Response fires, the agent calls Get Files to find what came in and Download File to pull the upload into storage with its original name and MIME type intact, then attaches it to the customer record and opens a verification ticket in Zendesk with the labeled answers in the body. Get File is called first when the workflow only needs to know a file's type and size before deciding whether it is worth transferring at all.
Knowing when a new form appears

On New Form fires when someone in the organization builds a form, survey, or quiz. The agent calls Get Workspaces to resolve the owning workspace, Get Form Fields to read the field list annotated with the page each field sits on, and posts to the operations channel in Slack with the form name, its owner, and a proposed destination. Because updated_at on a Formcrafts form record is the date it was last published rather than last edited, the digest says published, which is what the record actually means.

Human-in-Loop Highlight

The gate on a read-only connector is not an approval, it is a disagreement between two numbers that only a person can settle. Get Form reports a response count covering live and test responses together. The responses list returns live responses only. So a quarterly load can finish with 198 rows against a form that reports 214, and both figures are correct. The gap is either sixteen test submissions somebody made while building the form, or sixteen live responses the walk did not reach because the ceiling cut it short. Those two readings lead to opposite actions: publish the report, or stop and re-run with a wider window. The agent will not pick. It loads nothing, and posts: "Feedback form Q3 load finished at 198 responses. The form reports 214. Get All Form Responses read 3 pages and was not truncated, so the difference is most likely test-mode submissions. Publish the 198, or hold the load?" The analyst answers, and the reporting table gets a number somebody stands behind.

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

14 actions

Account and Workspaces

Get Account Confirms that the configured key is accepted and returns the account it belongs to. Used as a connection check at the top of a flow, and to record which organization a run read from.
Get Workspaces Lists the workspaces in the organization with their identifiers, names, and creation dates. Workspaces group forms, and a form record carries the workspace identifier this returns.

Forms

Get Forms Lists the forms in the organization with their identifiers, names, owning workspace, enabled flag, creation date, and last published date, up to a page at a time.
Get All Forms Walks the date-based pagination until the account is exhausted or the ceiling is reached, deduplicating by identifier and reporting how many pages were read and whether the walk was cut short.
Get Form Retrieves one form by identifier with its full field list, its page list, and its current response count. Used to discover field identifiers and labels before mapping a submission onto another system.
Find Form By Name Locates forms by name using exact, contains, or starts with matching, ignoring case. Formcrafts publishes no search parameter, so the walk and the comparison run in FlowRunner.
Get Form Fields Returns a form's fields as a flat list, each annotated with the label of the page it sits on rather than a bare page identifier, optionally narrowed to one field type.

Responses

Get Form Responses Lists live submissions for one form with their visitor context, workflow results, and answers, narrowable to a creation date window. Test mode submissions never appear.
Get All Form Responses Walks every live submission for a form until it is exhausted or the ceiling is reached, deduplicating by identifier. Suited to exports and to backfilling a reporting table.
Get Form Responses With Labels Returns submissions as flat records keyed by field label rather than by the wire identifier, joining the form definition against every response. The operation that makes a load acceptable to a spreadsheet, a database, or a CRM.
Get Form Response Retrieves a single submission by the identifier a Formcrafts webhook delivers. Formcrafts publishes no single-response route, so this pages the form and stops as soon as it finds the match.

Files

Get Files Lists the files uploaded through the organization's forms with their identifiers, original names, MIME types, byte sizes, and upload dates.
Get File Retrieves the metadata of one uploaded file without transferring it. Used to check type or size before deciding whether to download.
Download File Downloads a file uploaded through a form and stores it, keeping its original name and MIME type unless overridden. Binary content is transferred without re-encoding.

Triggers

2 triggers

Event Triggers

On New Form Response Fires when a form receives a new live submission, emitting the record with its visitor context and answers. Formcrafts publishes no webhook management API, so this polls the form's responses and remembers what it has delivered. Test mode submissions never appear, and the first cycle records a baseline without firing.
On New Form Fires when a new form, survey, or quiz is created in the organization, emitting the record with its identifier, name, and owning workspace. Used to register a newly built form with the rest of a stack. The first cycle records the forms that already exist without firing.

Frequently Asked Questions

What can FlowRunner do with Formcrafts?

FlowRunner agents can run Get Account, Get Workspaces, and Get Forms in Formcrafts, plus 11 more actions.

Does connecting Formcrafts to FlowRunner require OAuth?

No. Formcrafts connects to FlowRunner with an API key, no OAuth flow required.

Can Formcrafts trigger a FlowRunner workflow automatically?

Yes. Formcrafts supports 2 triggers that can start a FlowRunner workflow automatically.

Start building with Formcrafts

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us