# UpLead integrations: companies, people and lists

> Convert a company name to domain, run a combined search and create a list in UpLead. Connect UpLead to the rest of your sales stack with Tray.ai.

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

## Overview

UpLead is a B2B contact and company database for finding prospects, enriching records with firmographic data, and verifying email addresses. Tray.ai connects to UpLead through the HTTP Connector, so your workflows can call the UpLead API alongside the rest of your stack.

## Use cases

### Companies

Read and create companies in UpLead from any Tray.ai workflow. The UpLead API covers calls such as search for a company and convert a company name to domain.

- Search for a company
- Convert a company name to domain
- Get a company logo

### People

Read and create people in UpLead from any Tray.ai workflow. The UpLead API covers calls such as search for a person and run a combined search.

- Search for a person
- Run a combined search
- Search prospects by title

### Lists

Read, create, and delete lists in UpLead from any Tray.ai workflow. The UpLead API covers calls such as create a list and get a list.

- Create a list
- Get a list
- Delete a list

### Account

Read account in UpLead from any Tray.ai workflow. The UpLead API covers calls such as check credit balance and list industries.

- Check credit balance
- List industries

## Challenges Tray.ai solves

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

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

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

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

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