ActionTaigaUpdated May 2026

How do I open a Taiga issue from a workflow?

Short answer: Drop the "Taiga → Create Issue" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 2 Taiga actions

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
Project ID project	number	Required	Project ID
Subject subject	string	Required	Message subject line.
Description description	string	Optional	Description

Sample request

{
  "project": "{{trigger.project}}",
  "subject": "e.g. Quick update",
  "description": "{{trigger.description}}"
}

Returns

{
  "id": 123,
  "ref": 42,
  "project": 1,
  "subject": "New Issue"
}

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

Triggered by

Apps that pair well as the trigger for Create Issue.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Taiga

2 Google Sheets triggers

HubSpot → Taiga

18 HubSpot triggers

FAQ

Questions about Create Issue.

What does the Create Issue action do in Taiga?

Creates a new issue in the chosen Taiga project, with subject, description, type, severity, and priority. Typical use: surface form submissions or monitoring alerts as triageable Taiga issues.

What inputs does Create Issue require?

Required: Project ID, Subject. Every input accepts a static value or a variable from any upstream node in your workflow.

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 Taiga 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 Create Issue support batch operations?

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

More actions