Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Teable

No-code database built on PostgreSQL

CategoryProductivity
AuthenticationOAuth 2.0, custom
Version0.2.0
Published scopes7 published scopes
Last updatedSeptember 30, 2026

Overview

Connect Teable with Flows360

No-code database built on PostgreSQL

Use the Teable 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 Record
  • List Records
  • Get Record
  • Update Record
  • Delete Record
  • Upload Attachment
  • 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: Teable
  • Package: @activepieces/piece-teable@0.2.0
  • Exact artifact digest: sha256:c62c0f5611203ce34f46d83dec76c4d7d213fabc73acd3f697b339f6aa722bea
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2, 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 Record (teable_create_record), Creates a new record in a Teable table. Classification: read.
  • List Records (teable_list_records), Retrieves a list of records from a table with optional filtering, sorting, and pagination. Classification: read.
  • Get Record (teable_get_record), Retrieves a single record from a table by its ID. Classification: read.
  • Update Record (teable_update_record), Updates an existing record in a Teable table. Classification: read.
  • Delete Record (teable_delete_record), Deletes a record from a Teable table by its ID. Classification: read.
  • Upload Attachment (teable_upload_attachment), Uploads a file as an attachment to a field in a Teable record. 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

Runtime execution evidence is managed separately from package metadata.

Capability summary

AuthenticationOAuth 2.0, custom
Supported objects7
Supported actions7
TriggersNone published

Authentication

Authentication method: OAuth 2.0, custom

Required scopes

base|readtable|readfield|readrecord|readrecord|createrecord|updaterecord|delete

Authentication profiles

connection · oauth2

OAuth scopes: base|read, table|read, field|read, record|read, record|create, record|update, record|delete

connection_2 · custom
  • Personal Access Token Required · protected credential
  • Base URL Optional

Supported objects

ObjectReadWriteNotes
Create Record Yes No Creates a new record in a Teable table.
List Records Yes No Retrieves a list of records from a table with optional filtering, sorting, and pagination.
Get Record Yes No Retrieves a single record from a table by its ID.
Update Record Yes No Updates an existing record in a Teable table.
Delete Record Yes No Deletes a record from a Teable table by its ID.
Upload Attachment Yes No Uploads a file as an attachment to a field in a Teable record.
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Create Record · Read

Creates a new record in a Teable table.

teable_create_record · Risk: low · Retry: safe

Inputs

  • base_id · string · Required
  • table_id · string · Required, The table inside the selected base.
  • fields · object · Required, The fields to add to the record.
List Records · Read

Retrieves a list of records from a table with optional filtering, sorting, and pagination.

teable_list_records · Risk: low · Retry: safe

Inputs

  • base_id · string · Required
  • table_id · string · Required, The table inside the selected base.
  • filter · string · Optional, A filter expression for the records. Use the visual query builder at https://app.teable.ai/developer/tool/query-builder to build one.
  • cellFormat · string · Optional, The format of the cell values in the response.
  • take · number · Optional, The record count you want to take, maximum is 1000.
  • skip · number · Optional, The records count you want to skip.
  • selectedRecordIds · array · Optional, Filter selected records by record ids.
Get Record · Read

Retrieves a single record from a table by its ID.

teable_get_record · Risk: low · Retry: safe

Inputs

  • base_id · string · Required
  • table_id · string · Required, The table inside the selected base.
  • record_id · string · Required, The record to act on.
  • cellFormat · string · Optional, The format of the cell values in the response.
Update Record · Read

Updates an existing record in a Teable table.

teable_update_record · Risk: low · Retry: safe

Inputs

  • base_id · string · Required
  • table_id · string · Required, The table inside the selected base.
  • record_id · string · Required, The record to act on.
  • fields · object · Required, The fields to add to the record.
Delete Record · Read

Deletes a record from a Teable table by its ID.

teable_delete_record · Risk: low · Retry: safe

Inputs

  • base_id · string · Required
  • table_id · string · Required, The table inside the selected base.
  • record_id · string · Required, The record to act on.
Upload Attachment · Read

Uploads a file as an attachment to a field in a Teable record.

teable_upload_attachment · Risk: low · Retry: safe

Inputs

  • base_id · string · Required
  • table_id · string · Required, The table inside the selected base.
  • record_id · string · Required, The record to act on.
  • field_id · string · Required, The attachment field to upload the file to.
  • file · object · Required, The file to upload. Accepts a URL or a binary file.
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 Teable 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:
  • Personal Access Token (token), required; stored as a sensitive connection value.
  • Base URL (baseUrl), optional.

OAuth scopes

  • base|read
  • table|read
  • field|read
  • record|read
  • record|create
  • record|update
  • record|delete
  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-teable@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.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Teable 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-teable@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