Taiga
Project ManagementManage Taiga user stories, tasks, issues, epics, and sprints from your flows, on hosted or self-hosted instances. Agents file and classify inbound work and route high-severity or ambiguous reports to a lead before they land.
What This Integration Enables
FlowRunner agents use Taiga to run intake and triage as decisions, not manual filing. An agent can create user stories, tasks, and issues from inbound tickets, form submissions, or chat, setting the type, priority, and severity pulled from the project's own configuration. It can list and update stories across a sprint, spin up new milestones and epics for release planning, and verify a connection and resolve project context before acting. Because Taiga uses optimistic concurrency, the connector reads the current version before updating so changes never clobber a teammate's edit. The clear cases file themselves. The judgment calls reach a person.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Bug Report to Classified Issue
A support tool forwards a bug report. The agent reads it, maps it to the project's issue type, priority, and severity, and creates the issue with Create Issue. It replies with the new issue reference so the reporter can follow along. When the report reads as high severity or the classification is ambiguous, the agent does not file it silently. It routes the report to an engineering lead to confirm severity before the issue lands in the backlog.
Feature Request to User Story
A feature request comes in through a chat channel. The agent creates a user story with Create User Story, sets its milestone and tags, and replies with the story reference. Because the agent pulls status and milestone options from the live project configuration, the story lands in the right sprint with the right state.
Release-Planning Automation with a Scope Gate
At the start of a release cycle, the agent creates the next milestone with Create Milestone and files the planned epics with Create Epic. It then lists candidate user stories and proposes which to pull into the sprint. Before it commits a sprint plan that changes team commitments, it pauses for the project owner to approve the scope.
Human-in-Loop Highlight
When a bug report reads as high severity, or when the agent cannot map it cleanly to the project's issue type and priority, it does not file a guess into the backlog. It pauses and routes to an engineering lead through their preferred channel: "A report came in that looks like [severity signal]. I mapped it to [type/priority] but I am not certain. File it as-is, reclassify, or hold?" The lead decides, and the agent runs Create Issue with the confirmed classification. Clean reports are filed automatically; the severe and ambiguous ones reach a person before they enter the sprint.
Agent Capabilities
23 actionsProjects
3- List Projects Lists projects visible to the account, optionally filtered by member or looked up by slug. Used to discover which projects a flow can operate on.
- Get Project Retrieves a project by numeric ID with its members, modules, and configured statuses. Used to read classification options before filing work.
- Get Project by Slug Retrieves a project by its slug rather than numeric ID. Used to resolve a project from a URL-style identifier.
User Stories
5- List User Stories Lists stories, optionally filtered by project, status, and milestone. Used to review a sprint or find stories to update.
- Get User Story Retrieves a single story with its version number. Used to read current state before an update.
- Create User Story Creates a story with subject, description, status, milestone, and tags. Used to turn a feature request into tracked work.
- Update User Story Updates a story, passing its current version for optimistic concurrency. Used to progress a story without clobbering a teammate's edit.
- Delete User Story Permanently deletes a story and its tasks. Used in cleanup.
Tasks
5- List Tasks Lists tasks, optionally filtered by project and parent story. Used to review the tasks under a story.
- Get Task Retrieves a single task with its version number. Used to read current state before an update.
- Create Task Creates a task, optionally attached to a story, with a status. Used to break a story into tracked steps.
- Update Task Updates a task, passing its current version for optimistic concurrency. Used to progress a task safely.
- Delete Task Permanently deletes a task. Used in cleanup.
Issues
4- List Issues Lists issues, optionally filtered by project. Used to review the bug queue.
- Get Issue Retrieves a single issue with its version number. Used to read current state before an update.
- Create Issue Creates an issue with priority, severity, type, and status from the project configuration. Used to file a triaged bug.
- Update Issue Updates an issue, passing its current version for optimistic concurrency. Used to reclassify or progress an issue.
Epics
2- List Epics Lists epics, optionally filtered by project. Used to review the epics that group stories across sprints.
- Create Epic Creates an epic with a subject and description. Used to set up a release theme during planning.
Milestones
2- List Milestones Lists milestones (sprints) with dates and roll-up point statistics. Used to review sprint progress.
- Create Milestone Creates a milestone with a name and start and finish dates. Used to stand up the next sprint.
Members
2- Get Me Returns the authenticated user's profile. Used as a connection check to confirm credentials are valid.
- List Memberships Lists project memberships linking users to projects with roles. Used to resolve who can own or be assigned work.
Start building with Taiga
$100 in credits. No card required. Connect in minutes.