Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Formstack

Formstack integration for Flows360 workflows.

CategoryOther
AuthenticationOAuth 2.0
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Formstack with Flows360

Formstack integration for Flows360 workflows.

Use the Formstack 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 Submission
  • Find Form by Name or ID
  • Get Submission Details
  • Find Submission by Field Value
  • Custom API Call

Available triggers

  • New Submission
  • New Form

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: Formstack
  • Package: @activepieces/piece-formstack@0.2.0
  • Exact artifact digest: sha256:6be5f3ba15156559f3fa747d8794542a6f01bf9668f3af192d666b24a59f0bb8
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. 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 (createSubmission), Submit data to a Formstack form Classification: read.
  • Find Form by Name or ID (findFormByNameOrId), Find a form by name or ID Classification: read.
  • Get Submission Details (getSubmissionDetails), Get details of a form submission Classification: read.
  • Find Submission by Field Value (findSubmissionByFieldValue), Search submissions by field values Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Submission, polling.
  • New Form, polling.

Verification

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

Capability summary

AuthenticationOAuth 2.0
Supported objects7
Supported actions5
Triggers2

Authentication

Authentication method: OAuth 2.0

Authentication profiles

connection · oauth2

Supported objects

ObjectReadWriteNotes
Create Submission Yes No Submit data to a Formstack form
Find Form by Name or ID Yes No Find a form by name or ID
Get Submission Details Yes No Get details of a form submission
Find Submission by Field Value Yes No Search submissions by field values
Custom API Call Yes No Make a custom API call to a specific endpoint
New Submission Yes No polling trigger declared by the pinned package.
New Form Yes No polling trigger declared by the pinned package.

Supported actions

Create Submission · Read

Submit data to a Formstack form

create_submission · Risk: low · Retry: safe

Inputs

  • form_id · string · Required
  • user_agent · string · Optional, Browser user agent to record
  • remote_addr · string · Optional, IP address to record
  • payment_status · string · Optional, Payment integration status
  • read · boolean · Optional, Mark submission as read when created
  • encryption_password · string · Optional, Password for encrypted forms
  • form_fields · object · Required, Fill out the form fields
Find Form by Name or ID · Read

Find a form by name or ID

find_form_by_name_or_id · Risk: low · Retry: safe

Inputs

  • search_query · string · Required, Enter form name or ID to search
  • include_folders · boolean · Optional, Organize results by folders
  • exact_match · boolean · Optional, Only exact name matches
Get Submission Details · Read

Get details of a form submission

get_submission_details · Risk: low · Retry: safe

Inputs

  • form_id · string · Required
  • submission_id · string · Required
  • encryption_password · string · Optional, Password for encrypted forms
  • include_metadata · boolean · Optional, Include IP, user agent, and location data
Find Submission by Field Value · Read

Search submissions by field values

find_submission_by_field_value · Risk: low · Retry: safe

Inputs

  • search_value · string · Required, Value to search for (minimum 3 characters)
  • per_page · number · Optional, Number of results per page (1-100)
  • page · number · Optional, Page number to return
  • sort_order · string · Optional, Sort results by submission ID
  • include_form_names · boolean · Optional, Include form names in results
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Submission · Poll

Triggers when a form receives a new submission

Inputs

  • form_id · string
New Form · Poll

Triggers when a new form is created

Setup

Setup

  1. Add the Formstack 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-formstack@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 Formstack 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-formstack@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