List Workbooks: Tableau action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Filter filter	string	Optional	Tableau filter expression (e.g. name:eq:Sales)
Page Size page_size	number	Optional	Max workbooks per page

Sample request

{
  "filter": "name:eq:Sales",
  "page_size": "{{trigger.page_size}}"
}

Returns

{
  "workbooks": {
    "workbook": [
      {
        "id": "wb-123",
        "name": "Sales Dashboard",
        "owner": {
          "id": "user-1"
        },
        "project": {
          "id": "proj-1",
          "name": "Default"
        },
        "updatedAt": "2026-04-15T10:00:00Z",
        "contentUrl": "SalesDashboard"
      }
    ]
  },
  "pagination": {
    "pageSize": "25",
    "pageNumber": "1",
    "totalAvailable": "1"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Workbooks.

What does the List Workbooks action do in Tableau?

Lists every workbook on the Tableau site with its project, owner, and tags. The standard starting point for any Tableau automation that operates on workbooks.

What inputs does List Workbooks require?

List Workbooks has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Tableau returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Workbooks support batch operations?

Yes. Run List Workbooks inside a Loop node to process arrays. Tiny Command handles Tableau's rate limits automatically so you don't have to throttle manually.

More actions