Skip to main content
Use the @bijection/connectors/tableau entrypoint to declare Tableau resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Published data sources

pull: Published data sources and their upstream tables

The following example matches configuration standard.

Configuration: standard

Case: tableau/datasources/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: tableau. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Workbooks

pull: Workbooks, their sheets and upstream data sources

The following example matches configuration standard.

Configuration: standard

Case: tableau/workbooks/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: tableau. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. Read-only content inventory over the captured Metadata API (POST <baseUrl>/api/metadata/graphql). The connection setup baseUrl is the Tableau Server or Tableau Cloud origin (Cloud includes the pod). The Metadata API uses the REST API credentials token in X-Tableau-Auth. tableau.credential("TABLEAU_SESSION") names a session_login envelope: the engine signs in with a personal access token, presents the credentials.token it answers as X-Tableau-Auth, and signs in again after the declared lifetime or once after a rejected request. Nothing in the recipe holds the token or writes the header. Store the token’s name as username and its secret as password, and declare the sign-in for the site’s contentUrl (Tableau Cloud requires one; omit it for Tableau Server’s default site):
A token is valid only for the site it signed in to. Tableau Server’s token lasts 240 minutes by default, so a two-hour declared lifetime renews well inside it; the reference states no Tableau Cloud lifetime, and a session that ends sooner is recovered by signing in again after the rejected request. Signing in again with the same personal access token ends its earlier session, so one token should back exactly one credential. Connected-app JWT sign-in is not supported: the JWT must be freshly signed for every sign-in, which the envelope does not do. Identity is tableauSites[0].luid; the reference does not say that tableauSites lists only the signed-in site. datasources.pull walks publishedDatasourcesConnection(first: 100, after:) and workbooks.pull walks workbooksConnection(first: 100, after:), following pageInfo.endCursor while hasNextPage holds. Data sources carry upstreamTables (id, luid, name, fullName, schema, connectionType); workbooks carry sheets and upstreamDatasources (id, luid, name). Interface fields (fields, database) are not selected. Workbook updatedAt is non-null and is the opaque version; data source updatedAt is nullable, so data sources carry no version. No coverage is claimed. Results are scoped to what the token’s user may see. Nothing is withdrawn: removed content just disappears from the connection and the API offers no tombstone. NODE_LIMIT_EXCEEDED and TIME_LIMIT_EXCEEDED are documented warnings that return partial results; the captured response contract admits only data (and extensions), so a page that carries errors is refused rather than published partially. RATE_EXCEEDED (Metadata API throttling, configurable on Tableau Server) has no documented HTTP status or retry header, so no backoff is declared. No write is declared; the Metadata API is read-only. The schema is a reviewed projection transcribed from the published reference, not retrieved by introspection. Regenerate with BIJECTION_GRAPHQL_EXECUTABLE=/path/to/bijection-graphql node dev/graphql-codegen.mjs tableau (--check compares). Nothing here has run against Tableau or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.