TriggerTaigaReal-timeUpdated May 2026
How do I trigger when a Taiga user story is created?
Short answer: Drop the "Taiga → New User Story" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Taiga, not on a polling schedule.
Anatomy
What this trigger looks like in a workflow.
Drop it on the canvas. Configure a couple of fields. Publish.
In the builder
Trigger
New User Story
When the matching event happens
user story addedwhen a new user story is createdwhen user story createdwatch for user story creatednew user story creatednew user storyon user story created
What this trigger returns
for the curiousYou don’t need to read this. Tiny Command 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": "userstory.create","subject": "Sample userstory"}
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 | "userstory.create" |
| subject | string | "Sample userstory" |
Pairs with
Drop these actions after New User Story.
FAQ
Questions about New User Story.
How does the New User Story trigger work in Taiga?
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.
Is the New User Story trigger real-time?
Yes. New User Story uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in Taiga.
What data does New User Story 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 New User Story 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 New User Story?
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.
TriggerIssue Updated
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.
TriggerNew 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.
TriggerNew 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.
TriggerTask 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.
Build a workflow on this trigger.
One trigger. 2+ downstream actions. Zero glue.
