# Clerk integrations: organization memberships

> Create an organization membership, create an invitation and create a session in Clerk, and start a workflow when Clerk sends “User created”.

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

## Overview

Clerk is a user authentication and account management service for web and mobile apps, handling sign-up, sign-in, sessions, and organizations with roles and invitations. Tray.ai connects to Clerk through the HTTP Connector, so your workflows can call the Clerk API alongside the rest of your stack.

## Use cases

### Users

Read, create, update, delete, and manage users in Clerk from any Tray.ai workflow. The Clerk API covers calls such as list all users and create a user.

- List all users
- Create a user
- Update a user

### Organizations

Read, create, update, and delete organizations in Clerk from any Tray.ai workflow. The Clerk API covers calls such as list organizations and create an organization.

- List organizations
- Create an organization
- Update an organization

### Organization memberships

Read and create organization memberships in Clerk from any Tray.ai workflow. The Clerk API covers calls such as list organization members and create an organization membership.

- List organization members
- Create an organization membership

### Invitations

Read, create, and update invitations in Clerk from any Tray.ai workflow. The Clerk API covers calls such as list all invitations and create an invitation.

- List all invitations
- Create an invitation
- Create multiple invitations

### Sessions

Read and create sessions in Clerk from any Tray.ai workflow. The Clerk API covers calls such as list all sessions and create a session.

- List all sessions
- Create a session
- Create a session token

### Clerk events

Start a Tray.ai workflow the moment something happens in Clerk. Clerk sends events such as user created and user updated to a Tray.ai webhook trigger.

- User created
- User updated

## Challenges Tray.ai solves

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

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

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

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

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