# Octave integrations: agents and agent runs

> Create an agent, run an agent asynchronously and create a persona in Octave, and start a workflow when Octave sends “Entity created”.

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

## Overview

Octave is a go-to-market platform that stores your personas, products, segments, and competitors in one library and runs AI agents that research, qualify, and write outreach from it. Tray.ai connects to Octave through the HTTP Connector, so your workflows can call the Octave API alongside the rest of your stack.

## Use cases

### Agents

Read, create, update, and delete agents in Octave from any Tray.ai workflow. The Octave API covers calls such as list agents and get an agent.

- List agents
- Get an agent
- Create an agent

### Agent runs

Read agent runs in Octave from any Tray.ai workflow. The Octave API covers calls such as enrich a company and enrich a person.

- Enrich a company
- Enrich a person
- Qualify a person

### Personas

Read, create, and update personas in Octave from any Tray.ai workflow. The Octave API covers calls such as list personas and get a persona.

- List personas
- Get a persona
- Create a persona

### Products

Read, create, update, and delete products in Octave from any Tray.ai workflow. The Octave API covers calls such as list products and get a product.

- List products
- Get a product
- Create a product

### Segments

Read, create, update, and delete segments in Octave from any Tray.ai workflow. The Octave API covers calls such as list segments and get a segment.

- List segments
- Get a segment
- Create a segment

### Entity webhooks

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

- List webhook endpoints
- Create a webhook endpoint
- Update a webhook endpoint

## Challenges Tray.ai solves

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

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

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

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

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