Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Softr

Softr integration for Flows360 workflows.

CategoryContent And Files
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Softr with Flows360

Softr integration for Flows360 workflows.

Use the Softr 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 7 actions and 1 trigger.

Available actions

  • Create App User
  • Create Database Record
  • Delete App User
  • Delete Database Record
  • Find Database Record
  • Update Database Record
  • Custom API Call

Available triggers

  • New Database Record

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: Softr
  • Package: @activepieces/piece-softr@0.2.0
  • Exact artifact digest: sha256:4da596f97c1c0adbdff92629baf9385a6b66cad8eeabeb07f8c2fc1d1e41e436
  • 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

  • Create App User (createAppUser), Creates a new user inside a Softr app. Classification: read.
  • Create Database Record (createDatabaseRecord), Creates a new record. Classification: read.
  • Delete App User (deleteAppUser), Deletes a user from a Softr app. Classification: read.
  • Delete Database Record (deleteDatabaseRecord), Deletes a existing database record. Classification: read.
  • Find Database Record (findDatabaseRecord), Finds a record in table. Classification: read.
  • Update Database Record (updateDatabaseRecord), Updates an existing database record. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Database Record, 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 objects8
Supported actions7
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create App User Yes No Creates a new user inside a Softr app.
Create Database Record Yes No Creates a new record.
Delete App User Yes No Deletes a user from a Softr app.
Delete Database Record Yes No Deletes a existing database record.
Find Database Record Yes No Finds a record in table.
Update Database Record Yes No Updates an existing database record.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Database Record Yes No polling trigger declared by the pinned package.

Supported actions

Create App User · Read

Creates a new user inside a Softr app.

create_app_user · Risk: low · Retry: safe

Inputs

  • email · string · Required, The email address of the new user.
  • full_name · string · Required, The full name of the new user.
  • password · string · Required, The password for the new user.
  • domain · string · Required, The domain or subdomain of the Softr app where the user will be created.
  • generate_magic_link · boolean · Optional, If checked, a magic link will be generated for the user.
Create Database Record · Read

Creates a new record.

create_database_record · Risk: low · Retry: safe

Inputs

  • databaseId · string · Required, Select the database to insert the record into
  • tableId · string · Required, Select the table to insert the record into
  • fields · object · Required
Delete App User · Read

Deletes a user from a Softr app.

delete_app_user · Risk: low · Retry: safe

Inputs

  • email · string · Required, The email address of the user to delete.
  • domain · string · Required, The domain or subdomain of the Softr app (e.g., yourdomain.com or subdomain.softr.app).
Delete Database Record · Read

Deletes a existing database record.

delete_database_record · Risk: low · Retry: safe

Inputs

  • databaseId · string · Required, Select the database to insert the record into
  • tableId · string · Required, Select the table to insert the record into
  • recordId · string · Required
Find Database Record · Read

Finds a record in table.

find_database_record · Risk: low · Retry: safe

Inputs

  • databaseId · string · Required, Select the database to insert the record into
  • tableId · string · Required, Select the table to insert the record into
  • fieldId · string · Required
  • fieldValue · string · Required
Update Database Record · Read

Updates an existing database record.

update_database_record · Risk: low · Retry: safe

Inputs

  • databaseId · string · Required, Select the database to insert the record into
  • tableId · string · Required, Select the table to insert the record into
  • recordId · string · Required
  • fields · object · Required
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 Database Record · Poll

Triggers when a new record is added.

Inputs

  • databaseId · string
  • tableId · string

Setup

Setup

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