Overview
Connect Tables with Flows360
Tables integration for Flows360 workflows.
Use the Tables 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 9 actions and 3 triggers.
Available actions
- Create Table
- Delete Table
- Create Record(s)
- Delete Record(s)
- Update Record
- Get Record
- Find Records
- Clear Table
- Plus 1 additional declared action.
Available triggers
- New Record Created
- Record Updated
- Record Deleted
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: Tables
- Package:
@activepieces/piece-tables@0.5.1 - Exact artifact digest:
sha256:8bfe23cb586ede89a002ab998bd90547947a39ae83d3abde61ece1b530411450 - Runtime: Activepieces-compatible deterministic worker
- Source: the exact reviewed Activepieces source
Authentication
No connection authentication is declared by the package. 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 Table (
tables-create-table), Create a new table, optionally with fields. Classification: read. - Delete Table (
tables-delete-table), Delete a table and all of its records. Classification: read. - Create Record(s) (
tables-create-records), Insert one or more new records to a table. Classification: read. - Delete Record(s) (
tables-delete-record), Delete record(s) from a table Classification: read. - Update Record (
tables-update-record), Update values in an existing record Classification: read. - Get Record (
tables-get-record), Get single record by its id. Classification: read. - Find Records (
tables-find-records), Find records in a table with filters. Classification: read. - Clear Table (
tables-clear-table), Delete all records from a table Classification: read. - Download Table (
tables-download-table), Export a table as a CSV file. Classification: read.
Trigger contracts
- New Record Created, webhook.
- Record Updated, webhook.
- Record Deleted, webhook.
Verification
Runtime execution evidence is managed separately from package metadata.
Capability summary
Authentication
Authentication method: No authentication required
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Create Table | Yes | No | Create a new table, optionally with fields. |
| Delete Table | Yes | No | Delete a table and all of its records. |
| Create Record(s) | Yes | No | Insert one or more new records to a table. |
| Delete Record(s) | Yes | No | Delete record(s) from a table |
| Update Record | Yes | No | Update values in an existing record |
| Get Record | Yes | No | Get single record by its id. |
| Find Records | Yes | No | Find records in a table with filters. |
| Clear Table | Yes | No | Delete all records from a table |
| Download Table | Yes | No | Export a table as a CSV file. |
| New Record Created | Yes | No | webhook trigger declared by the pinned package. |
| Record Updated | Yes | No | webhook trigger declared by the pinned package. |
| Record Deleted | Yes | No | webhook trigger declared by the pinned package. |
Triggers
New Record Created · Webhook
Triggers when a new record is added to the selected table.
Inputs
table_id· string
Record Updated · Webhook
Triggers when a record is updated in the selected table.
Inputs
table_id· string
Record Deleted · Webhook
Triggers when a record is deleted from the selected table.
Inputs
table_id· string
Setup
Setup
- Add the Tables connector to the workflow in the target Flows360 Studio instance.
- 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.
- Provide the connection fields declared by the pinned package:
- No provider credential fields are declared by the pinned package.
- Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
- Test the workflow in the appropriate environment before enabling production scheduling or event delivery.
Limitations
Limitations and operational notes
- This content describes
@activepieces/piece-tables@0.5.1; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 9 actions and 3 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 Tables 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-tables@0.5.1 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.