# SuiteCRM integrations: module records

> Create a record in SuiteCRM. Connect SuiteCRM to the rest of your sales stack with Tray.ai.

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

## Overview

SuiteCRM is an open source CRM that companies host themselves or in the cloud, tracking accounts, contacts, leads, opportunities, cases, and marketing campaigns. Tray.ai connects to SuiteCRM through the HTTP Connector, so your workflows can call the SuiteCRM API alongside the rest of your stack.

## Use cases

### Module records

Read, create, update, and delete module records in SuiteCRM from any Tray.ai workflow. The SuiteCRM API covers calls such as list records and get a record.

- List records
- Get a record
- Create a record

### Relationships

Read relationships in SuiteCRM from any Tray.ai workflow. The SuiteCRM API covers calls such as list related records and link two records.

- List related records
- Link two records
- Unlink records

### Metadata

Read metadata in SuiteCRM from any Tray.ai workflow. The SuiteCRM API covers calls such as list all modules and list module fields.

- List all modules
- List module fields
- Get list view columns

### Users

Read users in SuiteCRM from any Tray.ai workflow. The SuiteCRM API covers calls such as get the current user and get user preferences.

- Get the current user
- Get user preferences

## Challenges Tray.ai solves

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

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

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

The SuiteCRM API uses OAuth 2.0 and a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated SuiteCRM connector?

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