Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Wufoo

Wufoo integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Wufoo with Flows360

Wufoo integration for Flows360 workflows.

Use the Wufoo connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 5 actions and 2 triggers.

Available actions

  • Create Form Entry
  • Find Form by Name or Hash
  • Find Submission by Field Value
  • Get Entry Details
  • Custom API Call

Available triggers

  • New Form Entry
  • New Form Created

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Wufoo
  • Package: @activepieces/piece-wufoo@0.2.0
  • Exact artifact digest: sha256:f9d4a3162f574fdf86b3531bb8a03317b7416f5e2b19283bd12df7c6d4c9c8ea
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Form Entry (create-form-entry), Submit a new entry to a Wufoo form with dynamic field selection. Classification: read.
  • Find Form by Name or Hash (find-form), Get details about a Wufoo form including settings, entry counts, and metadata. Classification: read.
  • Find Submission by Field Value (find-submission-by-field), Search for form submissions by field value for deduplication and lookup operations. Classification: read.
  • Get Entry Details (get-entry-details), Get form entries with filtering, sorting, and pagination options. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Form Entry, webhook.
  • New Form Created, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects7
Supported actionsNot published
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential
  • Subdomain Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Form Entry Yes No Submit a new entry to a Wufoo form with dynamic field selection.
Find Form by Name or Hash Yes No Get details about a Wufoo form including settings, entry counts, and metadata.
Find Submission by Field Value Yes No Search for form submissions by field value for deduplication and lookup operations.
Get Entry Details Yes No Get form entries with filtering, sorting, and pagination options.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Form Entry Yes No webhook trigger declared by the pinned package.
New Form Created Yes No polling trigger declared by the pinned package.

Triggers

New Form Entry · Webhook

Triggers when someone submits a new entry to your Wufoo form.

Inputs

  • formIdentifier · string
  • handshakeKey · string
  • includeMetadata · boolean
  • responseFormat · string
New Form Created · Poll

Triggers when a new form is created in your Wufoo account.

Inputs

  • pollingInterval · string
  • nameFilter · string
  • includeInactive · boolean
  • responseFormat · string

Setup

Setup

  1. Add the Wufoo connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • API Key (apiKey), required; stored as a sensitive connection value.
  • Subdomain (subdomain), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-wufoo@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Wufoo connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-wufoo@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com