# Yodiz integrations

> Call the Yodiz API from any Tray.ai workflow with the HTTP Connector.

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

## Overview

Yodiz is an agile project management tool for planning sprints, tracking user stories, issues and tasks, and managing product backlogs. Tray.ai connects to Yodiz through the HTTP Connector, so your workflows can call the Yodiz API alongside the rest of your stack.

## Use cases

### Projects

Read projects in Yodiz from any Tray.ai workflow. The Yodiz API covers calls such as list projects and get a project backlog.

- List projects
- Get a project backlog
- List project users

### User stories

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

- List user stories
- Get a user story
- Create a user story

### Issues

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

- List issues
- Get an issue
- Create an issue

### Tasks

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

- Get a task
- Create a task
- Update a task

### Attachments

Read and create attachments in Yodiz from any Tray.ai workflow. The Yodiz API covers calls such as list attachments and upload an attachment.

- List attachments
- Upload an attachment

## Challenges Tray.ai solves

### Keeping Yodiz 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 Yodiz 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 Yodiz 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 Yodiz 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 Yodiz?

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

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

The Yodiz API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Yodiz connector?

Yodiz runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Yodiz connector from the Yodiz 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/