# Celoxis integrations: projects and tasks

> Create a project, create a task and create a time entry in Celoxis. Connect Celoxis to the rest of your operations stack with Tray.ai.

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

## Overview

Celoxis is project and portfolio management software for PMOs, covering project plans, resource capacity, budgets, time tracking and portfolio reporting, in the cloud or self-hosted. Tray.ai connects to Celoxis through the HTTP Connector, so your workflows can call the Celoxis API alongside the rest of your stack.

## Use cases

### Projects

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

- List projects
- Get a project
- Create a project

### Tasks

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

- List tasks
- Create a task
- Update a task

### Time entries

Read, create, update, and delete time entries in Celoxis from any Tray.ai workflow. The Celoxis API covers calls such as list time entries and create a time entry.

- List time entries
- Create a time entry
- Update a time entry

## Challenges Tray.ai solves

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

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

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

The Celoxis 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 Celoxis connector?

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