# Basecamp integrations

> Call the Basecamp API from any Tray.ai workflow with the HTTP Connector.

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

## Overview

Basecamp is a project management app from 37signals that keeps each project's to-dos, message boards, schedules, documents, and group chat in one place. Tray.ai connects to Basecamp through the HTTP Connector, so your workflows can call the Basecamp API alongside the rest of your stack.

## Use cases

### Projects

Read, create, and update projects in Basecamp from any Tray.ai workflow. The Basecamp API covers calls such as list projects and get a project.

- List projects
- Get a project
- Create a project

### To-dos

Read, create, and update to-dos in Basecamp from any Tray.ai workflow. The Basecamp API covers calls such as list to-dos and create a to-do.

- List to-dos
- Create a to-do
- Update a to-do

### Messages

Read, create, and update messages in Basecamp from any Tray.ai workflow. The Basecamp API covers calls such as list messages and create a message.

- List messages
- Create a message
- Update a message

### Comments

Read, create, and update comments in Basecamp from any Tray.ai workflow. The Basecamp API covers calls such as list comments and create a comment.

- List comments
- Create a comment
- Update a comment

### Webhooks

Create, update, and delete webhooks in Basecamp from any Tray.ai workflow. The Basecamp API covers calls such as create a webhook and update a webhook.

- Create a webhook
- Update a webhook
- Delete a webhook

### Basecamp events

Start a Tray.ai workflow the moment something happens in Basecamp. Basecamp sends events such as message created and comment created to a Tray.ai webhook trigger.

- Message created
- Comment created
- To-do completed

## Challenges Tray.ai solves

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

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

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

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

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