# CircleCI integrations: pipelines and workflows

> Approve a pending job and create a context in CircleCI, and start a workflow when CircleCI sends “Workflow completed”.

**Canonical page:** https://tray.ai/connectors/circleci-integrations/
**Categories:** Developer tools
**Connects through:** HTTP Connector

## Overview

CircleCI is a continuous integration and delivery service that builds, tests and deploys code through pipelines, workflows and jobs defined in a project's config file. Tray.ai connects to CircleCI through the HTTP Connector, so your workflows can call the CircleCI API alongside the rest of your stack.

## Use cases

### Pipelines

Read and create pipelines in CircleCI from any Tray.ai workflow. The CircleCI API covers calls such as list pipelines and get a pipeline.

- List pipelines
- Get a pipeline
- Trigger a pipeline

### Workflows

Read and delete workflows in CircleCI from any Tray.ai workflow. The CircleCI API covers calls such as get a workflow and list workflow jobs.

- Get a workflow
- List workflow jobs
- Rerun a workflow

### Jobs

Read and delete jobs in CircleCI from any Tray.ai workflow. The CircleCI API covers calls such as get job details and cancel a job.

- Get job details
- Cancel a job

### Contexts

Read, create, update, and delete contexts in CircleCI from any Tray.ai workflow. The CircleCI API covers calls such as list contexts and create a context.

- List contexts
- Create a context
- Delete a context

### Insights

Read insights in CircleCI from any Tray.ai workflow. The CircleCI API covers calls such as get workflow metrics and get flaky tests.

- Get workflow metrics
- Get flaky tests
- Get an org summary

### Webhooks

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

- List webhooks
- Create a webhook
- Update a webhook

## Challenges Tray.ai solves

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

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

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

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

### Can I get a dedicated CircleCI connector?

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