# Teamup integrations: sub-calendars and access keys

> Create a sub-calendar and create an access key in Teamup, and start a workflow when Teamup sends “Event created”.

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

## Overview

Teamup is a shared online calendar for groups and organisations, with colour-coded sub-calendars, shareable access links with set permissions, and event sign-ups. Tray.ai connects to Teamup through the HTTP Connector, so your workflows can call the Teamup API alongside the rest of your stack.

## Use cases

### Events

Read, create, and update events in Teamup from any Tray.ai workflow. The Teamup API covers calls such as list events and search events.

- List events
- Search events
- Get an event

### Sub-calendars

Read, create, update, and delete sub-calendars in Teamup from any Tray.ai workflow. The Teamup API covers calls such as list sub-calendars and create a sub-calendar.

- List sub-calendars
- Create a sub-calendar
- Get a sub-calendar

### Access keys

Create and update access keys in Teamup from any Tray.ai workflow. The Teamup API covers calls such as create an access key and update an access key.

- Create an access key
- Update an access key

### Teamup events

Start a Tray.ai workflow the moment something happens in Teamup. Teamup sends events such as event created and event modified to a Tray.ai webhook trigger.

- Event created
- Event modified
- Event removed

## Challenges Tray.ai solves

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

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

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

The Teamup API uses an API key in a request header 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 Teamup connector?

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