Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Clicdata

ClicData enables True Performance with an end-to-end data analytics platform: connect, transform, automate, visualize and share data from 300+ sources.

CategoryBusiness Intelligence
AuthenticationOAuth 2.0, custom
Version0.0.9
Published scopes5 published scopes
Last updatedSeptember 29, 2026

Overview

Connect Clicdata with Flows360

ClicData enables True Performance with an end-to-end data analytics platform: connect, transform, automate, visualize and share data from 300+ sources.

Use the Clicdata 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 2 actions and no declared triggers.

Available actions

  • Insert Row
  • Refresh Table

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: Clicdata
  • Package: @activepieces/piece-clicdata@0.0.9
  • Exact artifact digest: sha256:a94716f70aadbb09a86100ec7a0f4f6083848654332c9066c7693b4447353dfb
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2, SECRET TEXT, 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

  • Insert Row (insert_row), Insert rows into a ClicData table (maximum 500 rows) Classification: read.
  • Refresh Table (refresh_table), Refresh the selected table depending on the refresh mode 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 objects2
Supported actions2
TriggersNone published

Authentication

Authentication method: OAuth 2.0, custom

Required scopes

account_readdata_readdata_writetable_readtable_write

Authentication profiles

connection · oauth2

OAuth scopes: account_read, data_read, data_write, table_read, table_write

connection_2 · custom
  • API Key Required · protected credential
connection_3 · custom
  • Client ID Required
  • User Email Required
  • User Password Required · protected credential

Supported objects

ObjectReadWriteNotes
Insert Row Yes No Insert rows into a ClicData table (maximum 500 rows)
Refresh Table Yes No Refresh the selected table depending on the refresh mode

Supported actions

Insert Row · Read

Insert rows into a ClicData table (maximum 500 rows)

insert_row · Risk: low · Retry: safe

Inputs

  • table_id · string · Required, Select the table to insert data into
  • data · object · Required, Array of objects representing rows to insert. Each object should have column names as keys. Maximum 500 rows.
  • apiVersion · string · Optional, Defaults to 2022.01
Refresh Table · Read

Refresh the selected table depending on the refresh mode

refresh_table · Risk: low · Retry: safe

Inputs

  • table_id · string · Required, Select the table to insert data into
  • mode · string · Required, Select the refresh mode for the table
  • apiVersion · string · Optional, Defaults to 2022.01

Setup

Setup

  1. Add the Clicdata 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:
  • Client ID (clientId), required.
  • User Email (userEmail), required.
  • User Password (userPassword), required; stored as a sensitive connection value.

OAuth scopes

  • account_read
  • data_read
  • data_write
  • table_read
  • table_write
  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-clicdata@0.0.9; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 2 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 Clicdata 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-clicdata@0.0.9 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