Fillout Forms

Overview

Connect Fillout Forms with Flows360

Create interactive forms and automate workflows with Fillout

Use the Fillout Forms 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 4 actions and 1 trigger.

Available actions

• Get Form Responses
• Get Single Response
• Find Form by Title
• Custom API Call

Available triggers

• New Form Response

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: Fillout Forms
• Package: @activepieces/piece-fillout-forms@0.2.0
• Exact artifact digest: sha256:d872650881b4812029082e2cb3798bdf85ec3f673ae7dac8083bcd6aed5a0d65
• Runtime: Activepieces-compatible deterministic worker
• Source: the exact reviewed Activepieces source

Authentication

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

Action contracts

• Get Form Responses (getFormResponses), Fetch all responses for a Fillout form, with optional filters. Classification: read.
• Get Single Response (getSingleResponse), Retrieves a specific submission from a form. Classification: read.
• Find Form by Title (findFormByTitle), Finds an existing forms by title. Classification: read.
• Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

• New Form Response, webhook.

Verification

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

Capability summary

Authentication

Authentication method: custom

Authentication profiles

Supported objects

Triggers

Setup

Setup

1. Add the Fillout Forms 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:

• No provider credential fields are declared by the pinned package.

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-fillout-forms@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
• Only the 4 actions and 1 trigger 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

Related documentation