Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Deftform

Build powerful forms and automate your workflow with Deftform.

CategoryForms And Surveys
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Deftform with Flows360

Build powerful forms and automate your workflow with Deftform.

Use the Deftform 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 1 trigger.

Available actions

  • Get Workspace Details
  • Get All Forms and Fields
  • Get Form Fields
  • Get Form Responses
  • Get Submission PDF
  • Add Form Response
  • Update Form Settings
  • 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: Deftform
  • Package: @activepieces/piece-deftform@0.1.0
  • Exact artifact digest: sha256:02af784d3bf181bd4aa6379ed8b9365b4e696be916bb4217d387e61c45307928
  • 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 Workspace Details (get_workspace_details), Retrieves all information about your Deftform workspace. Useful as a connection test. Classification: read.
  • Get All Forms and Fields (get_all_forms), Lists all forms in your workspace, including their fields. Classification: read.
  • Get Form Fields (get_form_fields), Retrieves only the fields of a specific form. Great for understanding the structure before building automations. Classification: read.
  • Get Form Responses (get_form_responses), Retrieves all submissions (responses) for a specific form. Useful for reporting and data exports. Classification: read.
  • Get Submission PDF (get_submission_pdf), Generates a PDF download link for a specific form submission by its unique response UUID. Classification: read.
  • Add Form Response (add_form_response), Submits a new response programmatically to a form.

Note: This does not trigger email notifications to the form admin, unlike regular public submissions. Classification: read.

  • Update Form Settings (update_form_settings), Updates any combination of form settings via a single call, from title and status to integrations, SEO, and security. 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

Authenticationcustom
Supported objects9
Supported actionsNot published
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Get Workspace Details Yes No Retrieves all information about your Deftform workspace. Useful as a connection test.
Get All Forms and Fields Yes No Lists all forms in your workspace, including their fields.
Get Form Fields Yes No Retrieves only the fields of a specific form. Great for understanding the structure before building automations.
Get Form Responses Yes No Retrieves all submissions (responses) for a specific form. Useful for reporting and data exports.
Get Submission PDF Yes No Generates a PDF download link for a specific form submission by its unique response UUID.
Add Form Response Yes No Submits a new response programmatically to a form. n**Note:** This does **not** trigger email notifications to the form admin, unlike regular public submissions.
Update Form Settings Yes No Updates any combination of form settings via a single call u2014 from title and status to integrations, SEO, and security.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Form Response Yes No webhook trigger declared by the pinned package.

Triggers

New Form Response · Webhook

Triggers instantly when a new response is submitted to a Deftform form.

Inputs

  • instructions · string

Setup

Setup

  1. Add the Deftform 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-deftform@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 8 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

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Deftform 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-deftform@0.1.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