Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Tenzo

Extract data and insights from the Tenzo platform for sales, forecasting, and analytics.

CategoryBusiness Intelligence
AuthenticationOAuth 2.0, custom
Version0.0.8
Published scopes26 published scopes
Last updatedSeptember 30, 2026

Overview

Connect Tenzo with Flows360

Extract data and insights from the Tenzo platform for sales, forecasting, and analytics.

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

Available actions

  • No actions are declared in this pinned package.

Available triggers

  • New Daily Forecast
  • New Summary Payments
  • New Summary Sales

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: Tenzo
  • Package: @activepieces/piece-tenzo@0.0.8
  • Exact artifact digest: sha256:a6112d16ac0c57bb4898e5182032ece58450f61ccb180ab35fbeba9a8581a0d1
  • 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

No actions are declared by this package version.

Trigger contracts

  • New Daily Forecast, polling.
  • New Summary Payments, polling.
  • New Summary Sales, polling.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

AuthenticationOAuth 2.0, custom
Supported objects3
Supported actionsNot published
Triggers3

Authentication

Authentication method: OAuth 2.0, custom

Required scopes

tenzo/area:readtenzo/location:readtenzo/sales:readtenzo/sales/day:readtenzo/sales/day/location:readtenzo/sales/day/area:readtenzo/sales/product:readtenzo/sales/product/category:readtenzo/sales/product/item:readtenzo/sales/product/location:readtenzo/sales/product/area:readtenzo/sales/order:readtenzo/sales/order/location:readtenzo/sales/order/area:readtenzo/sales/time_of_day:readtenzo/sales/time_of_day/location:readtenzo/sales/time_of_day/area:readtenzo/forecast:readtenzo/forecast/day/location:readtenzo/forecast/time_of_day/location:readtenzo/forecast/product/location:readtenzo/schedule/calendar:readtenzo/schedule/calendar:writetenzo/schedule/event:readtenzo/schedule/event:writetenzo/analytics:read

Authentication profiles

connection · oauth2

OAuth scopes: tenzo/area:read, tenzo/location:read, tenzo/sales:read, tenzo/sales/day:read, tenzo/sales/day/location:read, tenzo/sales/day/area:read, tenzo/sales/product:read, tenzo/sales/product/category:read, tenzo/sales/product/item:read, tenzo/sales/product/location:read, tenzo/sales/product/area:read, tenzo/sales/order:read, tenzo/sales/order/location:read, tenzo/sales/order/area:read, tenzo/sales/time_of_day:read, tenzo/sales/time_of_day/location:read, tenzo/sales/time_of_day/area:read, tenzo/forecast:read, tenzo/forecast/day/location:read, tenzo/forecast/time_of_day/location:read, tenzo/forecast/product/location:read, tenzo/schedule/calendar:read, tenzo/schedule/calendar:write, tenzo/schedule/event:read, tenzo/schedule/event:write, tenzo/analytics:read

connection_2 · custom
  • API Key Required · protected credential
connection_3 · custom
  • Application ID Required
  • API Secret Key Required · protected credential

Supported objects

ObjectReadWriteNotes
New Daily Forecast Yes No polling trigger declared by the pinned package.
New Summary Payments Yes No polling trigger declared by the pinned package.
New Summary Sales Yes No polling trigger declared by the pinned package.

Triggers

New Daily Forecast · Poll

Triggers when there is a new daily forecast for a selected location.

Inputs

  • location_id · string
New Summary Payments · Poll

Triggers when there is new daily sales and payments data.

Inputs

  • location_id · string
  • area_id · string
  • include_deleted · boolean
New Summary Sales · Poll

Triggers when there is new daily sales data.

Inputs

  • location_id · string
  • area_id · string

Setup

Setup

  1. Add the Tenzo 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:
  • Application ID (appId), required.
  • API Secret Key (apiSecret), required; stored as a sensitive connection value.

OAuth scopes

  • tenzo/area:read
  • tenzo/location:read
  • tenzo/sales:read
  • tenzo/sales/day:read
  • tenzo/sales/day/location:read
  • tenzo/sales/day/area:read
  • tenzo/sales/product:read
  • tenzo/sales/product/category:read
  • tenzo/sales/product/item:read
  • tenzo/sales/product/location:read
  • tenzo/sales/product/area:read
  • tenzo/sales/order:read
  • tenzo/sales/order/location:read
  • tenzo/sales/order/area:read
  • tenzo/sales/time_of_day:read
  • tenzo/sales/time_of_day/location:read
  • tenzo/sales/time_of_day/area:read
  • tenzo/forecast:read
  • tenzo/forecast/day/location:read
  • tenzo/forecast/time_of_day/location:read
  • tenzo/forecast/product/location:read
  • tenzo/schedule/calendar:read
  • tenzo/schedule/calendar:write
  • tenzo/schedule/event:read
  • tenzo/schedule/event:write
  • tenzo/analytics:read
  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-tenzo@0.0.8; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 0 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 Tenzo 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-tenzo@0.0.8 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