Form.io

Overview

Connect Form.io with Flows360

Build and manage forms and their submissions on Form.io, hosted or self-hosted

Use the Form.io 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 8 actions and 2 triggers.

Available actions

• Create Submission
• Get Submission
• Find Submissions
• Update Submission
• Delete Submission
• List Forms
• Get Form
• Custom API Call

Available triggers

• New Submission
• Updated Submission

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: Form.io
• Package: @activepieces/piece-formio@0.1.0
• Exact artifact digest: sha256:c8e9047fd9010fd7254ae77cc5ca472ed82dd5bd3b4d2ce957a9bd0bec4888aa
• 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 Submission (create_submission), Submit data to a Form.io form Classification: read.
• Get Submission (get_submission), Read one submission by its id Classification: read.
• Find Submissions (find_submissions), Search a form for submissions matching field filters Classification: read.
• Update Submission (update_submission), Replace the data on an existing submission Classification: read.
• Delete Submission (delete_submission), Delete a submission by its id Classification: read.
• List Forms (list_forms), List the forms in the Form.io project Classification: read.
• Get Form (get_form), Read one form definition, including its components Classification: read.
• Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

• New Submission, webhook.
• Updated Submission, 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 Form.io 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:

• Project URL (projectUrl), required.
• API Key (apiKey), 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-formio@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
• Only the 8 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

Related documentation