# Clientify integrations: contacts and companies

> Create a contact, create a company and create a deal in Clientify. Connect Clientify to the rest of your sales stack with Tray.ai.

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

## Overview

Clientify is a CRM and marketing automation suite covering contacts, companies, sales pipelines, tasks, email campaigns and automations. Tray.ai connects to Clientify through the HTTP Connector, so your workflows can call the Clientify API alongside the rest of your stack.

## Use cases

### Contacts

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

- List contacts
- Create a contact
- Update a contact

### Companies

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

- List companies
- Create a company
- Update a company

### Deals

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

- List deals
- Create a deal
- Update a deal

### Tasks

Read, create, and update tasks in Clientify from any Tray.ai workflow. The Clientify API covers calls such as list tasks and add a task.

- List tasks
- Add a task
- Edit a task

### Campaigns

Read and create campaigns in Clientify from any Tray.ai workflow. The Clientify API covers calls such as list campaigns and send a campaign.

- List campaigns
- Send a campaign
- Schedule a campaign

### Automations

Read and create automations in Clientify from any Tray.ai workflow. The Clientify API covers calls such as list automations and add a contact to an automation.

- List automations
- Add a contact to an automation

## Challenges Tray.ai solves

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

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

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

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

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