Resources · n8n integration

Wufoo n8n integrationAutomate Wufoo with n8n.

A form entry should not wait in a dashboard for someone to notice it. The Wufoo n8n integration is a trigger node: 1 webhook trigger that fires when a new entry lands on the form you select, with 0 action operations in the catalog. For teams who collect answers in Wufoo and want them working somewhere else.

Try the Wufoo integration on n8n

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Wufoo n8n integration actually do?

Wufoo collects the entry. n8n decides what happens next. The integration is one node, the Wufoo Trigger, which watches a single form and hands each new entry to the rest of the workflow. The catalog declares no Wufoo action node, so the shape of every build is the same: Wufoo starts the run, the nodes after it do the work.

The trigger runs on a webhook, which is a URL that Wufoo calls the moment something happens. n8n registers that URL when you activate the workflow, so a new entry reaches your workflow in seconds. Nothing is checked on a schedule, and there is no delay to tune.

Take a demo request form. The entry arrives, the answers go straight into a Slack message for whoever is on duty, and the same run appends a row to Google Sheets so the week's requests stay countable. Sales sees it before the visitor closes the tab.

Event signups behave the same way. Each new entry becomes a record in Airtable, and the Only Answers option keeps the payload down to what people actually typed, which makes the field mapping shorter to build and easier to read six months later.

Internal forms are the quiet win. An equipment request, a leave request, a bug report: the entry lands, the workflow files it and notifies the right person, and nobody keeps a browser tab open on the Wufoo dashboard.

When you need more from Wufoo than an incoming entry, the HTTP Request node calls any endpoint of the Wufoo API and reuses the same credential through its predefined authentication. That is the standard route in n8n for anything outside the catalog, and it keeps the API key in one place instead of two.

Worth knowing before you build: the catalog lists 1 trigger, 0 operations and no list of events to select, so the whole integration comes down to choosing a form and shaping what the node returns. If you are new to this kind of build, the n8n training covers the trigger-to-action pattern that every one of these workflows uses.

Connect

How do you connect Wufoo to n8n?

  1. 01

    Get your API key from the Form Manager

    You need a Wufoo account first. Open the Wufoo Form Manager, and to the right of the form you want to automate, select More, then API Information. That screen holds the API key n8n will use. A credential in n8n is just a saved set of connection details: you create it once, and every node that talks to Wufoo picks it from a dropdown.

  2. 02

    Read your subdomain off your Wufoo URL

    The credential also asks for a subdomain. It is the part of your Wufoo URL that sits after https:// and before wufoo.com, so for https://n8n.wufoo.com the subdomain is n8n. Admins can also read it in the Wufoo Account Manager. Type that one word, nothing around it.

  3. 03

    Save the credential and activate the workflow

    In n8n, create a Wufoo credential with the API key and the subdomain, then drop a Wufoo Trigger on the canvas and select it there. Choose your form in Forms Name or ID, save, and activate the workflow. Activation is what registers the webhook on the Wufoo side, so a workflow left inactive receives nothing.

Triggers

What starts a Wufoo workflow?

Wufoo Trigger is the node that starts a workflow each time Wufoo receives a new submission. Pick the form, activate the workflow: n8n registers the webhook on your Wufoo account.

What you see in n8n

Configuration notes

01Wufoo TriggerThe Wufoo Trigger is the starting node of the workflow, the one that decides when the run happens. It waits for a new entry on the form you select and passes that entry to the nodes that follow. Version 1 of the node handles Wufoo events through webhooks, so there is no schedule to set and no list of events to tick.

The Wufoo Trigger is the starting node of the workflow, the one that decides when the run happens. It waits for a new entry on the form you select and passes that entry to the nodes that follow. Version 1 of the node handles Wufoo events through webhooks, so there is no schedule to set and no list of events to tick.

Key parameters

  • Forms Name or ID: required. The form that fires the node when a new entry is made. Choose it from the list n8n loads from your account, or specify an ID with an expression, the small {{ }} syntax that reads a value instead of hard-coding it, for example {{ $json.field }} when the value comes from an earlier node.
When to use it
whenever the work starts with someone submitting the form, rather than with a clock or a manual click.
Use cases
a contact form that has to reach a channel within seconds, or a registration form whose entries belong in a spreadsheet the moment they exist.
02Only AnswersAn entry carries the answers people typed, plus other data that travels with the submission. Only Answers narrows what the node returns down to the answers alone, so the items coming out of the trigger hold the form content and nothing around it.

An entry carries the answers people typed, plus other data that travels with the submission. Only Answers narrows what the node returns down to the answers alone, so the items coming out of the trigger hold the form content and nothing around it.

Key parameters

  • Only Answers: optional, a switch. Turned on, the node returns only the answers of the form and not any of the other data.
When to use it
leave it off while you build, run one real submission, and look at what the trigger actually returns before you map anything. Turn it on once you know you only ever use the answers.
Use cases
a form feeding a spreadsheet or a database record, where every extra key in the payload is one more thing to scroll past while you wire the fields.
Need help

Need help automating Wufoo with n8n?

A person reads every message.

FAQ

Wufoo and n8n, answered

01Is the Wufoo integration free in n8n?
Yes, on the n8n side. The Wufoo Trigger ships with n8n, so there is nothing to install and no extra cost to unlock it, and it behaves the same on n8n Cloud and on a self-hosted instance running the Community Edition under the Sustainable Use licence. A workflow built on one runs on the other without changes. What a Wufoo account itself costs is a separate question and not one this page answers. The only thing you need on the Wufoo side is an account that lets you open the Form Manager and read the API information for your form.
02What credentials does the Wufoo Trigger need?
An API key, and the subdomain that identifies your Wufoo account. The key comes from the Wufoo Form Manager: to the right of a form, select More, then API Information. The subdomain is the part of your Wufoo URL that sits just before wufoo.com, so a full domain of n8n.wufoo.com gives a subdomain of n8n, and an admin can also read it in the Account Manager. Save both in a Wufoo credential in n8n once, and every workflow that touches Wufoo reuses it from the node's dropdown instead of storing the key again.
03What are the limits of the Wufoo n8n integration?
It is deliberately narrow. The catalog declares 1 trigger, 0 operations and 0 resources, and the trigger exposes no list of events to choose from, so the node is there to receive entries rather than to act on Wufoo. For anything outside the catalog, the HTTP Request node calls any endpoint of the Wufoo API and reuses the same credential through its predefined authentication, which keeps one set of connection details for the whole workflow. Plan the build around that split and the integration stops feeling thin.
04Does the Wufoo Trigger fire in real time?
Yes. The trigger receives submissions by webhook, meaning Wufoo calls an n8n URL as soon as an entry is made, rather than n8n asking Wufoo whether anything is new. n8n registers that URL with Wufoo when you activate the workflow, and each submission arrives within seconds, with no polling and nothing to schedule. The practical consequence is the activation step: a workflow you saved but never activated has no registered webhook, so entries submitted in the meantime do not reach it.
05n8n or Make for Wufoo forms?
It depends on where you want the data to live and how you want to pay. Make is hosted by Make, with no self-hosting option, and it bills by operation, so cost tracks volume. n8n runs on n8n Cloud or on your own server through Docker or npm, which matters when form answers carry personal data you would rather keep on infrastructure you control, and the same workflow behaves identically either way. Both are visual. Try the form trigger in each and keep the one whose logic reads faster to you.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations