# webCRM integrations: organisations and persons

> Create an organisation, create a person and create an opportunity in webCRM, and start a workflow when webCRM sends “Organisation created”.

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

## Overview

webCRM is a sales CRM for tracking organisations, contacts, opportunities, deliveries, activities and meetings in one shared database. Tray.ai connects to webCRM through the HTTP Connector, so your workflows can call the webCRM API alongside the rest of your stack.

## Use cases

### Organisations

Read, create, and update organisations in webCRM from any Tray.ai workflow. The webCRM API covers calls such as list organisations and get an organisation.

- List organisations
- Get an organisation
- Create an organisation

### Persons

Read, create, and update persons in webCRM from any Tray.ai workflow. The webCRM API covers calls such as list persons and get a person.

- List persons
- Get a person
- Create a person

### Opportunities

Read, create, and update opportunities in webCRM from any Tray.ai workflow. The webCRM API covers calls such as list opportunities and get an opportunity.

- List opportunities
- Get an opportunity
- Create an opportunity

### Deliveries

Read, create, and update deliveries in webCRM from any Tray.ai workflow. The webCRM API covers calls such as list deliveries and get a delivery.

- List deliveries
- Get a delivery
- Create a delivery

### Activities

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

- List activities
- Get an activity
- Create an activity

### Meetings

Read, create, update, and delete meetings in webCRM from any Tray.ai workflow. The webCRM API covers calls such as list meetings and get a meeting.

- List meetings
- Get a meeting
- Create a meeting

## Challenges Tray.ai solves

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

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

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

The webCRM API uses 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 webCRM connector?

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