Short answer: Drop the "Tableau → List Projects" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Page Size page_size | number | Optional | Max projects per page |
{"page_size": "{{trigger.page_size}}"}
{"projects": {"project": [{"id": "proj-1","name": "Default","description": "Default project","contentPermissions": "ManagedByOwner"}]}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.