# Salesmate integrations

> Call the Salesmate API from any Tray.ai workflow with the HTTP Connector.

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

## Overview

Salesmate is a CRM for sales and service teams that tracks contacts, companies, deals, and activities through a sales pipeline. Tray.ai connects to Salesmate through the HTTP Connector, so your workflows can call the Salesmate API alongside the rest of your stack.

## Use cases

### Contacts

Read, create, update, and delete contacts in Salesmate from any Tray.ai workflow. The Salesmate API covers calls such as get a contact and add a contact.

- Get a contact
- Add a contact
- Update a contact

### Companies

Read, create, update, and delete companies in Salesmate from any Tray.ai workflow. The Salesmate API covers calls such as get a company and add a company.

- Get a company
- Add a company
- Update a company

### Deals

Read, create, update, and delete deals in Salesmate from any Tray.ai workflow. The Salesmate API covers calls such as get a deal and add a deal.

- Get a deal
- Add a deal
- Update a deal

### Activities

Read, create, update, and delete activities in Salesmate from any Tray.ai workflow. The Salesmate API covers calls such as get an activity and add an activity.

- Get an activity
- Add an activity
- Update an activity

### Notes

Create, update, and delete notes in Salesmate from any Tray.ai workflow. The Salesmate API covers calls such as add a note and update a note.

- Add a note
- Update a note
- Pin a note

## Challenges Tray.ai solves

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

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

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

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

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