# Myphoner integrations: lists and leads

> Create a list and create a lead in Myphoner, and start a workflow when Myphoner sends “Lead created”.

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

## Overview

Myphoner is a cold-calling tool for sales teams that works through lead lists, logs calls and outcomes, and schedules call-backs. Tray.ai connects to Myphoner through the HTTP Connector, so your workflows can call the Myphoner API alongside the rest of your stack.

## Use cases

### Lists

Read and create lists in Myphoner from any Tray.ai workflow. The Myphoner API covers calls such as list all lists and create a list.

- List all lists
- Create a list
- Get a list

### Leads

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

- Create a lead
- Get a lead
- Update a lead

### Lead outcomes

Update lead outcomes in Myphoner from any Tray.ai workflow. The Myphoner API covers calls such as mark as winner and mark as loser.

- Mark as winner
- Mark as loser
- Mark for call back

### Webhooks

Update and delete webhooks in Myphoner from any Tray.ai workflow. The Myphoner API covers calls such as subscribe to list events and subscribe account-wide.

- Subscribe to list events
- Subscribe account-wide
- Delete a webhook

### Myphoner events

Start a Tray.ai workflow the moment something happens in Myphoner. Myphoner sends events such as lead created and lead updated to a Tray.ai webhook trigger.

- Lead created
- Lead updated
- Lead marked winner

## Challenges Tray.ai solves

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

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

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

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

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