123FormBuilder
FormsBring 123FormBuilder responses into your workflows: agents list account forms, inspect a form's field structure, and retrieve submissions to sync entries into CRMs, spreadsheets, and notification flows.
What This Integration Enables
123FormBuilder makes publishing a form fast, which is exactly why accounts accumulate dozens of them: contact forms, event registrations, order forms, surveys, each collecting quietly. The operational problem is never form creation; it is that every form is another place answers go to wait. FlowRunner agents put the whole account on one discipline: List Forms enumerates what exists, Get Form retrieves each form's field definitions so numeric field IDs resolve to real labels, and List Submissions with Get Submission moves entries into the systems where work actually happens. The label resolution deserves emphasis, because it is the part manual exports get wrong repeatedly. A submission is a set of values keyed by numeric field IDs, and every downstream system wants those values under names a human recognizes. An agent that reads the form definition before every load does the translation once, correctly, and keeps doing it correctly when the form changes, which is exactly when a hand-maintained mapping fails. - Sync form entries into CRMs, spreadsheets, and databases with fields mapped to labels, not IDs - Trigger downstream workflows from new survey responses and registrations the same hour they arrive - Pull a single entry by ID with Get Submission when a record needs its original source - Route only the ambiguous entries to a person, with the agent's evidence attached - Cover the whole account with one workflow, since List Forms discovers new forms without a config change
Without FlowRunner
With FlowRunner
Use Case Scenarios
Forty forms, one pipeline
A marketing team runs event registrations, gated-content forms, and a partner inquiry form across one 123FormBuilder account. A single agent sweeps them all: List Forms enumerates the active forms, List Submissions pulls what is new per form, and each entry lands in [HubSpot](/integrations/hubspot) tagged with its source form. The partner inquiries additionally ping a [Slack](/integrations/slack) channel, because a partner lead aging two days is a different kind of loss than a newsletter signup aging two days.
The survey that fed the report without an export
A quarterly customer survey collects two hundred responses. As they arrive, the agent resolves each answer against the field labels from Get Form and appends structured rows to [Google Sheets](/integrations/google-sheets), where the analysis lives. The CX lead watches results accumulate through the quarter instead of receiving a CSV keyed by field IDs after close, and flagged low scores route to the success team while the customer still remembers writing them.
The order form entry, retrieved at the moment of dispute
An operations coordinator handling a fulfillment question needs to see exactly what a customer ordered through the intake form. The workflow takes the submission ID stored on the order record, calls Get Submission, and returns the full entry: every field value, the timestamp, the IP, the status. What the customer actually submitted settles the question in one lookup instead of a dashboard search.
Human-in-Loop Highlight
Get Form is a read, but it guards the most expensive failure this connector can participate in: a bulk sync writing wrong values into hundreds of CRM records. Submissions come back keyed by field ID, and when someone edits a form, adds a question, removes one, reorders the rest, those IDs no longer mean what the saved mapping says they mean. An agent that keeps loading anyway will file budget figures into phone fields across every contact it touches, and unwinding a mis-mapped bulk write in a CRM is archaeology. So the sweep agent diffs the current Get Form output against the mapping it was built on before every batch. On a mismatch it loads nothing, posts the old and new field definitions side by side, and waits for a person to approve the corrected mapping. Holding two hundred submissions for an hour is recoverable. Writing them wrong is a cleanup project, and the person cleaning it up will not be the one who edited the form, which is exactly why the gate belongs in the workflow rather than in a team's memory.
Agent Capabilities
4 actionsForms
2- List Forms Retrieves all forms in the connected 123FormBuilder account with each form's ID, name, and status metadata, paged for large accounts. The discovery step that scopes every other operation.
- Get Form Retrieves a single form by ID including its field definitions: labels, types, and IDs. The mapping authority that lets submissions land downstream with human-readable labels, and the drift check that runs before every bulk load.
Submissions
2- List Submissions Retrieves entries for a specific form with paging, each carrying its submitted field values, submission ID, and timestamp. The sweep operation behind scheduled syncs.
- Get Submission Retrieves a single entry by ID for a form, returning the full set of submitted values plus timestamp, IP, and status. The on-demand lookup for enrichment, routing, and settling what was actually submitted.
Frequently Asked Questions
What can FlowRunner do with 123FormBuilder?
FlowRunner agents can run List Forms, Get Form, and List Submissions in 123FormBuilder, plus 1 more action.
Does connecting 123FormBuilder to FlowRunner require OAuth?
No. 123FormBuilder connects to FlowRunner with an API key, no OAuth flow required.
Can 123FormBuilder trigger a FlowRunner workflow automatically?
123FormBuilder doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with 123FormBuilder
$100 in credits. No card required. Connect in minutes.