Wufoo
FormsList Wufoo forms and fields, read and create form entries, work with reports, and manage submission webhooks through the Wufoo REST API.
What This Integration Enables
FlowRunner agents use Wufoo to turn form entries into correct downstream action. Because Wufoo entries are keyed by Field IDs, an agent reads the form fields first, maps IDs to labels, and then writes the labeled data into a CRM, spreadsheet, or database. It can submit entries into a Wufoo form from another system, read report entries and widgets for dashboards, and register a webhook so downstream automations react to each new submission. What it holds back is the entry that needs a decision. When a labeled entry meets a review condition, the agent stops and asks a person before it acts.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Entry-to-CRM Sync
New entries land on a lead form. The agent calls List Entries to pull them, maps the Field IDs to labels with List Form Fields, and writes each applicant into the CRM. It logs the entry in a tracking spreadsheet and posts a labeled summary to the team channel. The entries land where they belong, correctly labeled, without anyone decoding Field IDs.
Submission Volume Digest
A team wants a daily read on submission volume. The agent calls Get Entry Count across the relevant forms, reads report widgets for summarized metrics, and sends a digest email. The summary is current without anyone assembling numbers by hand.
Review-Gated Applications
An application form captures requests that sometimes need a human, such as a request above a threshold or an applicant flagged by the answers. The agent maps each entry and checks it against the review conditions. Routine applications sync automatically. An entry that meets a condition pauses and routes to the owner, who approves, adjusts, or rejects it before the agent moves it downstream.
Human-in-Loop Highlight
When the agent maps an entry whose labeled values meet a review condition, such as a requested amount above a limit or an answer flagged for attention, it does not write it downstream. It pauses and routes to the owner through their preferred channel: "New entry on [Form] from [applicant] meets the review condition [reason]. Labeled values: [summary]. Approve it to continue, adjust it, or reject it?" The owner decides, and only then does the agent move the entry on. The entries that carry a consequence get a human before anything downstream runs.
Agent Capabilities
13 actionsForms
3- List Forms Lists the forms on the account, each identified by its Hash. Used to resolve the form identifier other operations need.
- Get Form Returns a single form. Used to read form details.
- List Form Fields Returns each field id, title, type, and choices for a form. Used to map Field IDs to labels before reading or writing entries.
Entries
3- List Entries Returns the entries for a form, with optional filtering. Used to pull new submissions into other systems.
- Get Entry Count Returns the number of entries on a form. Used to build submission-volume summaries.
- Create Entry Submits an entry to a form, passing values keyed by Field ID. Used to seed a form with records from another system.
Reports
4- List Reports Lists the reports on the account. Used to inventory reports.
- Get Report Returns a single report. Used to read report details.
- Get Report Entries Returns the entries behind a report. Used to read filtered submission data for dashboards.
- Get Report Widgets Returns the widgets on a report. Used to read summarized metrics.
Users and Webhooks
3- List Users Lists the account users and their permissions. Used to audit administration access.
- Add Webhook Registers a webhook on a form so downstream automations react to each submission. Used to wire real-time delivery.
- Delete Webhook Removes a webhook. Used to tear down an integration.
Start building with Wufoo
$100 in credits. No card required. Connect in minutes.