Skip to content

Connectors / IT · HTTP Connector

Automate Clerk with Tray.ai

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

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.

See all connectors

What can you do with Clerk on Tray.ai?

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.

  • When Clerk sends “User created”, add the new signup to your CRM and welcome email list.
  • Ban a user in Clerk when your trust and safety team confirms abuse on the account.
  • Create an invitation in Clerk when a sales deal closes, so the customer's admin can sign in.
  • When Clerk sends “User updated”, sync the new email address to your billing system.
Connects through
HTTP Connector
Authentication
A bearer token
Base URL
https://api.clerk.com/v1

Set it up

Connect Clerk to Tray.ai

Each step uses Clerk's own API details, from its documentation.

Step 1

Save Clerk's API token

Save the token Clerk issues as a Tray.ai authentication. The HTTP Client sends it as a bearer token on every call. The token stays out of the workflow and out of the logs.

Step 2

Point the HTTP Client at the API

Add an HTTP Client step and use https://api.clerk.com/v1 as the base URL. Or paste a cURL example from Clerk's API docs, and Tray.ai fills in the method, URL, and headers.

Step 3

Start with “List all users”

It's one of 19 documented actions, under Users. The response comes back as data the next step can map into your other apps.

Step 4

Start workflows from Clerk events

Give Clerk the URL of a Tray.ai webhook trigger. “User created” can then start a workflow, and so can 1 other event.

What the Clerk API covers

5 resources and 19 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Connecting it takes a few clicks: here's how.

Users

  • List all users
  • Create a user
  • Update a user
  • Delete a user
  • Ban a user
  • Lock a user

Organizations

  • List organizations
  • Create an organization
  • Update an organization
  • Delete an organization

Organization memberships

  • List organization members
  • Create an organization membership

Invitations

  • List all invitations
  • Create an invitation
  • Create multiple invitations
  • Revoke an invitation

Sessions

  • List all sessions
  • Create a session
  • Create a session token

Events Clerk can send to a Tray.ai webhook trigger

  • User created
  • User updated

Checked against Clerk's own documentation on 2026-10-22

clerk.com/docs/reference/backend-api

Frequently asked questions

What can a Tray.ai workflow do in Clerk?

+

The Clerk API documents 19 actions across 5 resources (Users, Organizations, Organization memberships, Invitations, Sessions). For example: List all users; List organizations; List organization members. A workflow can make any documented call through the HTTP Connector.

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.

Which Clerk events can start a Tray.ai workflow?

+

Clerk sends 2 events to a webhook URL, for example: User created; User updated. A Tray.ai webhook trigger receives them and starts a workflow.

See Clerk working against your stack.

We'll walk through a tailored demo with your systems plugged in.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.