Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Coda

Coda integration for Flows360 workflows.

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

Overview

Connect Coda with Flows360

Coda integration for Flows360 workflows.

Use the Coda 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

  • Create Row
  • Update Row
  • Upsert Row
  • Find Row(s)
  • Get Row
  • List Table(s)
  • Get Table
  • Custom API Call

Available triggers

  • New Row Created

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: Coda
  • Package: @activepieces/piece-coda@0.2.0
  • Exact artifact digest: sha256:66efb5bda3257ec53d868036659f6798b2f6433c012a36a579edfee16041518a
  • 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 Row (create-row), Creates a new row in the selected table. Classification: read.
  • Update Row (update-row), Updates an existing row in the selected table. Classification: read.
  • Upsert Row (upsert-row), Creates a new row or updates an existing one if it matches key columns. Classification: read.
  • Find Row(s) (find-row), Find specific rows in the selected table using a column match search. Classification: read.
  • Get Row (get-row), Retrieves a single row by specified ID. Classification: read.
  • List Table(s) (list-tables), List tables in a selected document. Classification: read.
  • Get Table (get-table), Get structure and details of a specific table (e.g., columns, schema). Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Row Created, 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 objects9
Supported actions8
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Coda API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Row Yes No Creates a new row in the selected table.
Update Row Yes No Updates an existing row in the selected table.
Upsert Row Yes No Creates a new row or updates an existing one if it matches key columns.
Find Row(s) Yes No Find specific rows in the selected table using a column match search.
Get Row Yes No Retrieves a single row by specified ID.
List Table(s) Yes No List tables in a selected document.
Get Table Yes No Get structure and details of a specific table (e.g., columns, schema).
Custom API Call Yes No Make a custom API call to a specific endpoint
New Row Created Yes No polling trigger declared by the pinned package.

Supported actions

Create Row · Read

Creates a new row in the selected table.

create_row · Risk: low · Retry: safe

Inputs

  • docId · string · Required
  • tableId · string · Required
  • rowData · object · Required, Define the data for the new row based on table columns.
Update Row · Read

Updates an existing row in the selected table.

update_row · Risk: low · Retry: safe

Inputs

  • docId · string · Required
  • tableId · string · Required
  • rowIdOrName · string · Required
  • rowData · object · Required, Define the data for the new row based on table columns.
Upsert Row · Read

Creates a new row or updates an existing one if it matches key columns.

upsert_row · Risk: low · Retry: safe

Inputs

  • docId · string · Required
  • tableId · string · Required
  • keyColumns · array · Required
  • rowData · object · Required, Define the data for the new row based on table columns.
Find Row(s) · Read

Find specific rows in the selected table using a column match search.

find_row · Risk: low · Retry: safe

Inputs

  • docId · string · Required
  • tableId · string · Required
  • searchColumn · string · Required
  • searchValue · string · Required
Get Row · Read

Retrieves a single row by specified ID.

get_row · Risk: low · Retry: safe

Inputs

  • docId · string · Required
  • tableId · string · Required
  • rowIdOrName · string · Required
List Table(s) · Read

List tables in a selected document.

list_tables · Risk: low · Retry: safe

Inputs

  • docId · string · Required
  • max · number · Required, Maximum number of results to return.
Get Table · Read

Get structure and details of a specific table (e.g., columns, schema).

get_table · Risk: low · Retry: safe

Inputs

  • docId · string · Required
  • tableId · string · 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 Row Created · Poll

Triggers when a new row is added to the selected table.

Inputs

  • docId · string
  • tableId · string

Setup

Setup

  1. Add the Coda 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-coda@0.2.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 Coda 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-coda@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