Short answer: Drop the "Taiga → 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 |
|---|---|---|---|
Member ID member | string | Optional | Member ID |
{"member": "{{trigger.member}}"}
[{"id": 1,"name": "My Project","slug": "my-project","members": 5,"is_private": false}]
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.