# TimeTap integrations: appointments and clients

> Create an appointment, create a client and create a staff member in TimeTap. Connect TimeTap to the rest of your operations stack with Tray.ai.

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

## Overview

TimeTap is online appointment scheduling software for businesses and public agencies, managing bookings, clients, staff calendars, locations and class schedules. Tray.ai connects to TimeTap through the HTTP Connector, so your workflows can call the TimeTap API alongside the rest of your stack.

## Use cases

### Appointments

Read, create, update, and delete appointments in TimeTap from any Tray.ai workflow. The TimeTap API covers calls such as get an appointment and create an appointment.

- Get an appointment
- Create an appointment
- Update an appointment

### Clients

Read and create clients in TimeTap from any Tray.ai workflow. The TimeTap API covers calls such as list clients and get a client.

- List clients
- Get a client
- Create a client

### Staff

Read, create, update, and delete staff in TimeTap from any Tray.ai workflow. The TimeTap API covers calls such as list staff and get a staff member.

- List staff
- Get a staff member
- Create a staff member

### Services

Read, create, update, and delete services in TimeTap from any Tray.ai workflow. The TimeTap API covers calls such as list services and create a service.

- List services
- Create a service
- Update a service

### Locations

Read, create, update, and delete locations in TimeTap from any Tray.ai workflow. The TimeTap API covers calls such as list locations and create a location.

- List locations
- Create a location
- Update a location

## Challenges Tray.ai solves

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

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

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

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

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