# ClickMeeting integrations

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

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

## Overview

ClickMeeting is a webinar and online meeting platform for running live and automated events, with registration, attendee tracking, recordings, and reports. Tray.ai connects to ClickMeeting through the HTTP Connector, so your workflows can call the ClickMeeting API alongside the rest of your stack.

## Use cases

### Conferences

Read, create, update, and delete conferences in ClickMeeting from any Tray.ai workflow. The ClickMeeting API covers calls such as list conferences and create a conference.

- List conferences
- Create a conference
- Get a conference

### Invitations and access

Create invitations and access in ClickMeeting from any Tray.ai workflow. The ClickMeeting API covers calls such as send email invitations and generate access tokens.

- Send email invitations
- Generate access tokens
- Create an auto-login URL

### Sessions

Read sessions in ClickMeeting from any Tray.ai workflow. The ClickMeeting API covers calls such as list sessions and get a session.

- List sessions
- Get a session
- List session attendees

### Registrations

Read registrations in ClickMeeting from any Tray.ai workflow. The ClickMeeting API covers calls such as register a participant and list registrations.

- Register a participant
- List registrations

### Recordings

Read recordings in ClickMeeting from any Tray.ai workflow. The ClickMeeting API covers calls such as list recordings and publish a recording.

- List recordings
- Publish a recording

### File library

Read, create, and delete file library in ClickMeeting from any Tray.ai workflow. The ClickMeeting API covers calls such as list files and upload a file.

- List files
- Upload a file
- Download a file

## Challenges Tray.ai solves

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

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

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

The ClickMeeting API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated ClickMeeting connector?

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