# OnePageCRM integrations: contacts and deals

> Create a contact, create a deal and create an action in OnePageCRM, and start a workflow when OnePageCRM sends “Contact created”.

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

## Overview

OnePageCRM is an action-focused CRM for small sales teams, where every contact has a next action and deals, notes, calls and meetings sit alongside it. Tray.ai connects to OnePageCRM through the HTTP Connector, so your workflows can call the OnePageCRM API alongside the rest of your stack.

## Use cases

### Contacts

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

- List contacts
- Get a contact
- Create a contact

### Deals

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

- List deals
- Get a deal
- Create a deal

### Actions

Read, create, update, and delete actions in OnePageCRM from any Tray.ai workflow. The OnePageCRM API covers calls such as list actions and create an action.

- List actions
- Create an action
- Update an action

### Notes

Read, create, update, and delete notes in OnePageCRM from any Tray.ai workflow. The OnePageCRM API covers calls such as list notes and get a note.

- List notes
- Get a note
- Create a note

### OnePageCRM events

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

- Contact created
- Contact updated
- Contact deleted

## Challenges Tray.ai solves

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

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

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

The OnePageCRM API uses basic authentication 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 OnePageCRM connector?

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