# Taiga integrations: projects and user stories

> Create a project, create a user story and create a task in Taiga, and start a workflow when Taiga sends “User story created”.

**Canonical page:** https://tray.ai/connectors/taiga-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

Taiga is an open-source project management tool for agile teams, with Scrum and Kanban boards, user stories, tasks, issues and wiki pages. Tray.ai connects to Taiga through the HTTP Connector, so your workflows can call the Taiga API alongside the rest of your stack.

## Use cases

### Projects

Read, create, update, and delete projects in Taiga from any Tray.ai workflow. The Taiga API covers calls such as list projects and create a project.

- List projects
- Create a project
- Edit a project

### User stories

Read, create, update, and delete user stories in Taiga from any Tray.ai workflow. The Taiga API covers calls such as list user stories and create a user story.

- List user stories
- Create a user story
- Edit a user story

### Tasks

Read, create, update, and delete tasks in Taiga from any Tray.ai workflow. The Taiga API covers calls such as list tasks and create a task.

- List tasks
- Create a task
- Edit a task

### Issues

Read, create, update, and delete issues in Taiga from any Tray.ai workflow. The Taiga API covers calls such as list issues and create an issue.

- List issues
- Create an issue
- Edit an issue

### Milestones

Read, create, update, and delete milestones in Taiga from any Tray.ai workflow. The Taiga API covers calls such as list milestones and create a milestone.

- List milestones
- Create a milestone
- Edit a milestone

### Webhooks

Read, create, and delete webhooks in Taiga from any Tray.ai workflow. The Taiga API covers calls such as list webhooks and create a webhook.

- List webhooks
- Create a webhook
- Test a webhook

## Challenges Tray.ai solves

### Keeping Taiga credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Taiga credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Taiga API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Taiga API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Taiga?

Yes. Tray.ai connects to Taiga through the HTTP Connector, which calls the Taiga API directly. Any call the Taiga API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Taiga?

The Taiga API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Taiga connector?

Taiga runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Taiga connector from the Taiga API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/
