Reference · Tools
Wufoo Trigger
Starts workflow when a new Wufoo form entry is submitted
The Wufoo Trigger fires when a new entry is submitted to the form you monitor, delivering the parsed entry to the workflow. A typical build is routing each form submission into a CRM or spreadsheet with the answers already parsed.
- Node type
- Webhook trigger
- Parameters
- 2
- Outputs
- Output
- Credentials
- Wufoo
Wufoo Trigger
Triggers when a new entry is submitted on a Wufoo form
Overview
Receives webhook notifications from Wufoo when a new form entry is submitted. The incoming payload is form-encoded and includes a FieldStructure JSON descriptor that maps field IDs to human-readable titles and types. The trigger parses field values by type (text, file, address, checkbox, likert, shortname) and outputs a clean key-value object keyed by field title. When Only Answers is disabled, the output includes full metadata: createdBy, entryId, dateCreated, formId, formStructure, fieldStructure, and the parsed entries. Wufoo verifies webhook authenticity via a HandshakeKey that must match the value registered during webhook creation. Useful for automating form response processing, data collection workflows, survey analysis, and CRM integrations triggered by Wufoo form submissions.
Category: Productivity
Tool Name: wufoo_trigger
Version: 1
Appearance: Icon: lucide-ClipboardList | Color: #d44b32
Node Type
Trigger — webhook (receives incoming HTTP callbacks)
Input / Output
| Direction | Port(s) |
|---|---|
| Input | None (trigger node) |
| Output | Output |
Credentials
This tool requires Wufoo credentials. See the Credentials Guide for setup instructions.
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| Form | string | Yes | — | The hash identifier of the Wufoo form to monitor for new submissions. You can find the form hash in your Wufoo account by listing forms via the API (GET /api/v3/forms.json) or in the form URL. |
| Only Answers | boolean | No | true | Whether to return only the answers of the form and not any of the other data. When disabled, the output includes createdBy, entryId, dateCreated, formId, formStructure, fieldStructure, and entries. |
Output Data
Each submission produces one output item. Every item carries:
_trigger— alwayswufoo_webhook_timestamp— ISO 8601 timestamp of when the submission was received_webhookEvent— alwaysform_submission
With Only Answers on (the default), the parsed answers sit directly on the item, one key per field using the field’s title as the key.
With Only Answers off, the answers move under entries and the item also carries:
createdBy— the Wufoo user recorded on the entryentryId— the Wufoo entry IDdateCreated— the entry’s creation timestampformId— the ID of the form the entry belongs toformStructure— the parsed form descriptor Wufoo sentfieldStructure— the parsed field descriptor Wufoo sententries— the parsed answers, keyed by field title
Answer values are shaped by field type: file fields become the uploaded file’s URL, address / likert / short-name fields become objects keyed by sub-field label, checkbox fields become an array of the ticked values, and everything else is the submitted value.
Reference the payload downstream by expression, e.g. {{ $json["Email Address"] }}.
Usage Examples
- Start a workflow when someone submits a Wufoo contact form
- Capture survey responses from Wufoo and sync to a spreadsheet
- Trigger a notification when a Wufoo registration form is submitted
- Automate data collection from Wufoo forms into a CRM
Example Configuration
Answers only — the simplest shape to work with:
{
"type": "wufoo_trigger",
"parameters": {
"form": "abc123def",
"onlyAnswers": true
}
}
Full metadata envelope, when you need the entry ID and form structure as well:
{
"type": "wufoo_trigger",
"parameters": {
"form": "abc123def",
"onlyAnswers": false
}
}
Trigger Behavior
- Activation: When the workflow is activated, a webhook endpoint is registered with the service.
- Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
- Payload: The incoming webhook payload is parsed and output as workflow items.
- Verification: Supports signature verification where applicable.
Tips
Entry point that fires when Wufoo sends a webhook for a new form submission. Configure the Form ID (hash) to monitor and optionally set Only Answers to false to include full metadata (createdBy, entryId, dateCreated, formStructure, fieldStructure) alongside parsed entries. Wufoo sends form-encoded data with a HandshakeKey for verification and a FieldStructure JSON that describes all form fields. The trigger parses values by field type (text, file URL, address, checkbox, likert, shortname) into a clean object keyed by field title.
Frequently asked questions
How do I get the full submission metadata?
Set Only Answers to false to include createdBy, entryId, dateCreated, formStructure and fieldStructure alongside the parsed entries.
What identifies the form?
The Form ID hash from Wufoo, configured on the trigger — one trigger per form you want to watch.
How does Wufoo verify the delivery?
It sends form-encoded data with a HandshakeKey, along with a FieldStructure JSON describing the form's fields.
Which credential does it need?
A Wufoo credential.
Build with the Wufoo Trigger node
Drop it into a workflow, wire it to an agent, or call it on a schedule. You'll need Wufoo credentials first.
Open BusyBotLast updated . Spotted something wrong? Tell us.