- Integrations
- /
- Taiga
Taiga
Open-source agile project management Taiga, in workflows
Taiga is the open-source agile project management platform, backlog, sprints, user stories, issues, and tasks, with a kanban or scrum methodology choice per project. Six triggers cover the events worth automating: User Story Created, Task Created, Task Updated, Issue Created, Issue Updated, Sprint Created. Two actions: Create Issue, List Projects. The action surface is small because Taiga's strength is its in-product workflow; the connector's job is mostly to surface events for downstream automation rather than to drive Taiga from outside. The integration uses Taiga's API token from your user account. Common patterns: a Taiga Sprint Created fires a workflow that creates a paired Notion sprint-planning page with the auto-rolled-in user stories listed, or an Issue Created with a "bug" tag auto-creates a corresponding Linear issue in the QA team's backlog with the original Taiga link preserved. Most useful for teams running self-hosted Taiga.
Workflows start when Taiga does.
6 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
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.
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.
Fires whenever a new sprint (milestone) is created in the Taiga project. Useful for announcing sprint kickoffs or seeding a stand-up channel automatically.
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.
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.
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.
Do anything Taiga can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create Issue | 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. |
| List Projects | Lists all Taiga projects the connected account can see along with their slugs and IDs. Use as the first step in any flow that needs to scope work to a specific project. |
Pre-built Taiga workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Taiga once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Taiga field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Taiga integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Taiga to Tiny Command?
What Taiga triggers does Tiny Command support?
What Taiga actions can I run from a workflow?
Is the Taiga integration real-time?
Do I need to write code to use Taiga with Tiny Command?
How much does the Taiga integration cost?
More developer tools apps people connect.
Same category as Taiga, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Taiga.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.