TriggerTaigaReal-timeUpdated September 2026

How do I trigger when a Taiga issue changes?

Short answer: In TinyCommand, add the Taiga Issue Updated trigger to a workflow and publish. It listens through a Taiga webhook and fires your workflow within seconds of the event, with no polling and no code. Add a filter if you only want some events to continue past the trigger.

Trigger workflows on Issue Updated in Taiga — start free All 6 Taiga triggers

Trigger workflows on Issue Updated in Taiga — start free

Anatomy

What this trigger looks like in a workflow.

Drop it on the canvas. Configure a couple of fields. Publish.

In the builder

Trigger

Issue Updated

When the matching event happens

issue changedwhen an issue is updated in taigaon issue updatednew issue updatedwhen issue updatedwatch for issue updatedissue modified

What this trigger returns

for the curious

You don’t need to read this. TinyCommand auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.

{
  "id": 123,
  "event": "issue.change",
  "subject": "Sample issue"
}

Output shape

Fields available to downstream nodes.

Every field below can be referenced by name in any action or filter that comes after this trigger.

Field	Type	Example
id	number	123
event	string	"issue.change"
subject	string	"Sample issue"

Pairs with

Drop these actions after Issue Updated.

Add Labels to Message

Gmail · Email

Raw API Request

Slack · Communication

Add Sheet Tab

Google Sheets · Spreadsheets & Databases

Create Company

HubSpot · CRM & Sales

FAQ

Questions about Issue Updated.

How does the Issue Updated trigger work in Taiga?

Fires whenever any field on a Taiga issue changes (status, assignee, severity, comments). Combine with a status filter to react only when an issue is closed or escalated.

Is the Issue Updated trigger real-time?

Yes. Issue Updated uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Taiga.

What data does Issue Updated return?

The full event payload from Taiga. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.

Can I filter Issue Updated so only some events start a workflow?

Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.

Do I need Taiga admin permissions to use Issue Updated?

For most Taiga accounts a standard user can authorize the trigger. Some Taiga plans require an admin to enable third-party webhooks. Check Taiga's docs if the trigger fails to register.

More triggers

Other Taiga triggers.

Trigger

New Issue

Fires whenever a new issue is opened in the connected Taiga project. Use it to bridge bug reports into Slack, kick off a triage workflow, or mirror to another tracker.

Trigger

New Sprint

Fires whenever a new sprint (milestone) is created in the Taiga project. Useful for announcing sprint kickoffs or seeding a stand-up channel automatically.

Trigger

New Task

Fires when a new task is added under a Taiga user story. Use it to notify the assignee, append to a project log, or mirror the task to another planning tool.

Trigger

Task Updated

Fires whenever a task in Taiga is edited, reassigned, or moved between statuses. The payload carries the new field values so you can branch on what actually changed.

Trigger

New User Story

Fires whenever a new user story enters the Taiga backlog. Use it to copy stories into a roadmap tool, ping product, or auto-tag based on the related epic.

Trigger workflows on Issue Updated in Taiga — start free