# Coveo integrations: push source items

> Add or update an item, add or update a security identity and create a field in Coveo.

**Canonical page:** https://tray.ai/connectors/coveo-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Coveo is an AI search and recommendations platform that indexes content from many sources and serves relevant results on websites, commerce stores and support portals. Tray.ai connects to Coveo through the HTTP Connector, so your workflows can call the Coveo API alongside the rest of your stack.

## Use cases

### Push source items

Create and delete push source items in Coveo from any Tray.ai workflow. The Coveo API covers calls such as add or update an item and delete an item.

- Add or update an item
- Delete an item
- Push a batch of items

### Security identities

Create and delete security identities in Coveo from any Tray.ai workflow. The Coveo API covers calls such as add or update a security identity and delete a security identity.

- Add or update a security identity
- Delete a security identity

### Sources

Read and delete sources in Coveo from any Tray.ai workflow. The Coveo API covers calls such as list sources and get a source.

- List sources
- Get a source
- Duplicate a source

### Fields

Read, create, and update fields in Coveo from any Tray.ai workflow. The Coveo API covers calls such as list fields and create a field.

- List fields
- Create a field
- Update a field

### Query pipelines

Read, create, update, and delete query pipelines in Coveo from any Tray.ai workflow. The Coveo API covers calls such as list query pipelines and create a query pipeline.

- List query pipelines
- Create a query pipeline
- Update a query pipeline

## Challenges Tray.ai solves

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

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

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

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

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