# Streak integrations: pipelines, boxes and contacts

> Create a pipeline, create a box and create a contact in Streak, and start a workflow when Streak sends “Box created”.

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

## Overview

Streak is a CRM that lives inside Gmail, tracking deals and processes as boxes moving through pipeline stages alongside contacts, organizations, tasks and comments. Tray.ai connects to Streak through the HTTP Connector, so your workflows can call the Streak API alongside the rest of your stack.

## Use cases

### Pipelines

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

- List pipelines
- Get a pipeline
- Create a pipeline

### Boxes

Read, create, update, and delete boxes in Streak from any Tray.ai workflow. The Streak API covers calls such as create a box and get a box.

- Create a box
- Get a box
- Update a box

### Contacts

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

- Create a contact
- List contact fields
- Update a contact field value

### Tasks and comments

Create tasks and comments in Streak from any Tray.ai workflow. The Streak API covers calls such as create a task and create a comment.

- Create a task
- Create a comment

### Webhooks

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

- Create a webhook
- List pipeline webhooks
- List team webhooks

### Streak events

Start a Tray.ai workflow the moment something happens in Streak. Streak sends events such as box created and box stage changed to a Tray.ai webhook trigger.

- Box created
- Box stage changed
- Box edited

## Challenges Tray.ai solves

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

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

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

The Streak API uses 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 Streak connector?

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