Data & Storage · Integration
Wufoo
Add Wufoo to your product for your customers, and give your AI agents governed access to it.
Wufoo is a form builder, so what an integration touches is a form, the fields on it and the entries people submit. The awkward detail is naming. Wufoo identifies fields as Field1, Field2 and onwards per form, and a multi part field such as a name or an address occupies several of those ids at once, so the label a customer sees and the id your code receives are not the same thing. That makes field discovery and mapping the actual integration work, and it has to be redone whenever a customer edits their form. An embedded Wufoo integration lists forms, reads their field definitions, pulls entries with filters and paging, submits entries, and registers webhooks so a submission reaches your product immediately rather than on the next sweep. fastn holds each customer's API key per tenant and paces the reads.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Wufoo account so submissions reach your product without anybody exporting a spreadsheet.
Read a form's field definitions at setup and map them once, so raw field ids never appear in your own code.
Pull entries with filters and paging for a backfill, then keep current through webhooks instead of repeated reads.
Submit an entry from your product when the form is the record a customer wants to keep.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent summarises what this week's submissions to a form actually said.
An agent finds the entries matching a condition and reports them with the labels a human recognises.
An agent flags a form whose fields have changed since your mapping was made.
Example prompt
Summarise the entries submitted to this Wufoo form this week and tell me which need a reply.
Set up Wufoo in 4 steps
- 01Enable the Wufoo connector in your fastn dashboard.
- 02Have each customer supply their own Wufoo API key so reads are metered against their account.
- 03Read each form's field definitions and map the ids to your own model, then register the webhooks you want.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Wufoo integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Wufoo integration without building it. Your customers connect their own Wufoo account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Wufoo update is not your on-call problem.
- One integration serves your product and your agents. The same governed Wufoo connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
Typeform
Gravity Forms
SurveyMonkeyOften used alongside
Tools the same teams tend to run next to Wufoo, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceWufoo integration FAQ
How do I add a Wufoo integration to my product?
Enable the Wufoo connector in your fastn dashboard, then let each customer authenticate their own Wufoo account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Wufoo client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Wufoo account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Wufoo account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Wufoo integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent summarises what this week's submissions to a form actually said.
Who maintains the Wufoo integration?
fastn does. When Wufoo changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Wufoo integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Wufoo reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Wufoo integration?
A common starting point: let each customer connect their own Wufoo account so submissions reach your product without anybody exporting a spreadsheet. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Wufoo integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Wufoo does not change your per-connector cost. You can start free with 3 connected accounts.
Add Wufoo to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.