Wufoo
Read Wufoo forms, fields and entries, submit entries and manage webhooks (Wufoo API v3).
OCNORA ships 8 typed Wufoo operations and 1 trigger. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Wufoo
- Authentication
- Username & password, API key — any one of these.
- Credential
- {"api_key": "…"} — the 16-character Wufoo API key
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
- Prerequisites
- The API key must belong to a user who can administer the form; Wufoo refuses the webhook PUT otherwise. Publishing also needs MANTLE_APP_PUBLIC_BASE_URL set to a URL Wufoo can reach — it is the address written into the form's webhook.
Prerequisites are taken from the connection notes in this provider’s node contracts; each node’s reference page says which apply to it.
What you can do with Wufoo
Operations, grouped by what they do to your data, plus 1 trigger that start a run.
Create and send 2
Read and search 5
Delete and cancel 1
A sample Wufoo workflow
- 1Form Entrytrigger.wufoo_eventStart a run when someone submits an entry to a Wufoo form.
- 2Count Entrieswufoo.count_entriesCount the entries stored for a form, with the same filters as a list.
- 3Create Webhookwufoo.create_webhookAdd a webhook so Wufoo posts every new entry on a form to a URL, which is how a Mantle webhook trigger receives them.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 8
- Count EntriesCount the entries stored for a form, with the same filters as a list.wufoo.count_entries
- Create WebhookAdd a webhook so Wufoo posts every new entry on a form to a URL, which is how a Mantle webhook trigger receives them.wufoo.create_webhook
- Delete WebhookRemove one webhook from a form, by the hash its creation returned.wufoo.delete_webhook
- Get FormRetrieve one form's settings by its hash or its title.wufoo.get_form
- List EntriesList a form's stored entries, optionally filtered and sorted.wufoo.list_entries
- List Form FieldsList a form's fields with the Field ids that entry writes and entry filters address them by.wufoo.list_fields
- List FormsList the forms this API key can reach, with their hashes and counts.wufoo.list_forms
- Submit EntrySubmit a new entry to a form, exactly as if someone had filled it in, using the Field ids wufoo.list_fields returns.wufoo.submit_entry
Wufoo questions
- How does OCNORA authenticate with Wufoo?
- With a stored Username & password or API key credential, shaped {"api_key": "…"} — the 16-character Wufoo API key. A connection test can check it when you add it.
- What can I automate with Wufoo?
- 8 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.
- What if the Wufoo operation I need is not listed?
- Where Wufoo has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Wufoo?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Wufoo calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
More in Business apps
See your first Wufoo workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.