Short answer: Drop the "Taiga → Create Issue" 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 |
|---|---|---|---|
Project ID project | number | Required | Project ID |
Subject subject | string | Required | Message subject line. |
Description description | string | Optional | Description |
{"project": "{{trigger.project}}","subject": "e.g. Quick update","description": "{{trigger.description}}"}
{"id": 123,"ref": 42,"project": 1,"subject": "New Issue"}
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.