Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Retable

Turn your spreadsheets into smart database apps

CategoryProductivity
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Retable with Flows360

Turn your spreadsheets into smart database apps

Use the Retable 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 no declared triggers.

Available actions

  • Create Retable Record
  • Get Workspaces
  • Get Projects
  • Get Retables
  • Create a Workspace
  • Create a Project
  • Custom API Call

Available triggers

  • No triggers are declared in this pinned package.

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: Retable
  • Package: @activepieces/piece-retable@0.2.0
  • Exact artifact digest: sha256:e91d19a7b0d13712a25a620f552adeed7b7a2678bc10d8eb526b9d5644f80fdd
  • 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 Retable Record (retable_create_record), Adds a record into a retable Classification: read.
  • Get Workspaces (retable_get_workspaces), Gets all workspaces Classification: read.
  • Get Projects (retable_get_projects), Gets all projects in given workspace Classification: read.
  • Get Retables (retable_get_retables), Gets all retables in given project Classification: read.
  • Create a Workspace (retable_create_workspace), Creates a workspace Classification: read.
  • Create a Project (retable_create_project), Creates a project in the given workspace Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

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

Capability summary

Authenticationcustom
Supported objects7
Supported actions7
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Retable Record Yes No Adds a record into a retable
Get Workspaces Yes No Gets all workspaces
Get Projects Yes No Gets all projects in given workspace
Get Retables Yes No Gets all retables in given project
Create a Workspace Yes No Creates a workspace
Create a Project Yes No Creates a project in the given workspace
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Create Retable Record · Read

Adds a record into a retable

retable_create_record · Risk: low · Retry: safe

Inputs

  • workspace_id · string · Required
  • project_id · string · Required
  • retable_id · string · Required
  • fields · object · Required
Get Workspaces · Read

Gets all workspaces

retable_get_workspaces · Risk: low · Retry: safe

Get Projects · Read

Gets all projects in given workspace

retable_get_projects · Risk: low · Retry: safe

Inputs

  • workspace_id · string · Required
Get Retables · Read

Gets all retables in given project

retable_get_retables · Risk: low · Retry: safe

Inputs

  • workspace_id · string · Required
  • project_id · string · Required
Create a Workspace · Read

Creates a workspace

retable_create_workspace · Risk: low · Retry: safe

Inputs

  • name · string · Required
  • desc · string · Optional
Create a Project · Read

Creates a project in the given workspace

retable_create_project · Risk: low · Retry: safe

Inputs

  • workspace_id · string · Required
  • name · string · Required
  • desc · string · Optional
  • color · string · Optional
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.

Setup

Setup

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