Overview
Connect Tableau with Flows360
Business intelligence and analytics platform for data visualization
Use the Tableau 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 5 actions and 9 triggers.
Available actions
- Download View
- Run Extract Refresh Task
- Refresh Workbook
- Find View
- Find Workbook
Available triggers
- Workbook Event
- Workbook Refresh Event
- Datasource Event
- Datasource Refresh Event
- User Deleted
- View Deleted
- Plus 3 additional declared triggers.
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: Tableau
- Package:
@activepieces/piece-tableau@0.1.6 - Exact artifact digest:
sha256:982a5a098406c9aa04fae85fa3f1375e5a205f25d300fe3610b32cc1a2d501f7 - Runtime: Activepieces-compatible deterministic worker
- Source: the exact reviewed Activepieces source
Authentication
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
- Download View (
download_view), Download a view from a workbook in the specified format Classification: read. - Run Extract Refresh Task (
run_extract_refresh_task), Runs the specified extract refresh task and returns job information Classification: read. - Refresh Workbook (
refresh_workbook), Refreshes the specified workbook immediately Classification: read. - Find View (
find_view), Finds a view based on name (URL name) Classification: read. - Find Workbook (
find_workbook), Finds a workbook based on ID or content URL Classification: read.
Trigger contracts
- Workbook Event, webhook.
- Workbook Refresh Event, webhook.
- Datasource Event, webhook.
- Datasource Refresh Event, webhook.
- User Deleted, webhook.
- View Deleted, webhook.
- Label Event, webhook.
- New Job, polling.
- List Extract Refresh Tasks, polling.
Verification
Runtime execution evidence is managed separately from package metadata.
Capability summary
Authentication
Authentication method: custom
Authentication profiles
connection · custom
- Server URL Required
- API Version Required
- Site Content URL Optional
- Username Optional
- Password Optional · protected credential
- Personal Access Token Name Optional · protected credential
- Personal Access Token Secret Optional · protected credential
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Download View | Yes | No | Download a view from a workbook in the specified format |
| Run Extract Refresh Task | Yes | No | Runs the specified extract refresh task and returns job information |
| Refresh Workbook | Yes | No | Refreshes the specified workbook immediately |
| Find View | Yes | No | Finds a view based on name (URL name) |
| Find Workbook | Yes | No | Finds a workbook based on ID or content URL |
| Workbook Event | Yes | No | webhook trigger declared by the pinned package. |
| Workbook Refresh Event | Yes | No | webhook trigger declared by the pinned package. |
| Datasource Event | Yes | No | webhook trigger declared by the pinned package. |
| Datasource Refresh Event | Yes | No | webhook trigger declared by the pinned package. |
| User Deleted | Yes | No | webhook trigger declared by the pinned package. |
| View Deleted | Yes | No | webhook trigger declared by the pinned package. |
| Label Event | Yes | No | webhook trigger declared by the pinned package. |
| New Job | Yes | No | polling trigger declared by the pinned package. |
| List Extract Refresh Tasks | Yes | No | polling trigger declared by the pinned package. |
Triggers
Workbook Event · Webhook
Triggers when a workbook event occurs (created, updated, or deleted)
Inputs
eventType· string
Workbook Refresh Event · Webhook
Triggers when a workbook refresh event occurs (started, succeeded, or failed)
Inputs
eventType· string
Datasource Event · Webhook
Triggers when a datasource event occurs (created, updated, or deleted)
Inputs
eventType· string
Datasource Refresh Event · Webhook
Triggers when a datasource refresh event occurs (started, succeeded, or failed)
Inputs
eventType· string
User Deleted · Webhook
Triggers when a user is deleted
View Deleted · Webhook
Triggers when a workbook view is deleted
Label Event · Webhook
Triggers when a label event occurs (created, updated, or deleted)
Inputs
eventType· string
New Job · Poll
Triggers when a job matches the specified criteria
Inputs
jobType· stringstatus· string
List Extract Refresh Tasks · Poll
Lists extract refresh tasks for the site
Setup
Setup
- Add the Tableau 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:
- Server URL (
serverUrl), required. - API Version (
apiVersion), required. - Site Content URL (
siteContentUrl), optional. - Username (
username), optional. - Password (
password), optional; stored as a sensitive connection value. - Personal Access Token Name (
personalAccessTokenName), optional; stored as a sensitive connection value. - Personal Access Token Secret (
personalAccessTokenSecret), optional; stored as a sensitive connection value.
- 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-tableau@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 5 actions and 9 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 Tableau 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-tableau@0.1.6 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.