# Accelo integrations: companies, contacts and jobs

> Create a company, create a contact and create a job in Accelo, and start a workflow when Accelo sends “Task created”.

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

## Overview

Accelo is professional services automation software that runs client work for agencies and consultancies, from sales and quotes through projects, support tickets, time tracking and invoicing. Tray.ai connects to Accelo through the HTTP Connector, so your workflows can call the Accelo API alongside the rest of your stack.

## Use cases

### Companies

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

- List companies
- Get a company
- Create a company

### Contacts

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

- List contacts
- Get a contact
- Create a contact

### Jobs

Read, create, update, and delete jobs in Accelo from any Tray.ai workflow. The Accelo API covers calls such as list jobs and get a job.

- List jobs
- Get a job
- Create a job

### Issues

Read, create, update, and delete issues in Accelo from any Tray.ai workflow. The Accelo API covers calls such as list issues and get an issue.

- List issues
- Get an issue
- Create an issue

### Activities

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

- List activities
- Create an activity
- Update an activity

### Invoices

Read invoices in Accelo from any Tray.ai workflow. The Accelo API covers calls such as list invoices and get an invoice.

- List invoices
- Get an invoice
- Count invoices

## Challenges Tray.ai solves

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

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

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

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

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