# Tomba integrations: email finder and leads

> Create a lead, create a lead list and create a bulk job in Tomba, and start a workflow when Tomba sends “Bulk job completed”.

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

## Overview

Tomba finds and verifies business email addresses and phone numbers, and stores the results as leads you can sort into lists. Tray.ai connects to Tomba through the HTTP Connector, so your workflows can call the Tomba API alongside the rest of your stack.

## Use cases

### Email finder

Read email finder in Tomba from any Tray.ai workflow. The Tomba API covers calls such as find an email address and search a domain.

- Find an email address
- Search a domain
- Verify an email address

### Leads

Read, create, update, and delete leads in Tomba from any Tray.ai workflow. The Tomba API covers calls such as list leads and create a lead.

- List leads
- Create a lead
- Get a lead

### Lead lists

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

- List lead lists
- Create a lead list
- Update a lead list

### Bulk jobs

Read and create bulk jobs in Tomba from any Tray.ai workflow. The Tomba API covers calls such as create a bulk job and launch a bulk job.

- Create a bulk job
- Launch a bulk job
- Check bulk job progress

### Tomba events

Start a Tray.ai workflow the moment something happens in Tomba. Tomba sends events such as bulk job completed and bulk job failed to a Tray.ai webhook trigger.

- Bulk job completed
- Bulk job failed
- Lead created

## Challenges Tray.ai solves

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

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

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

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

### Can I get a dedicated Tomba connector?

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