Automate your Clerk support lookups with an AI agent

Look up a Clerk user by email

You ask by email address.

Clerk has no fetch-by-email endpoint, so the companion calls the list-users tool with the `query` parameter, which matches name, email, username, phone or id, then pulls sessions for that user id. Sessions cannot be listed globally: the tool returns 422 without a user or client id, so that ordering is the only route through.

Back comes what the ticket asked for. Two active sessions, one on a client last seen Thursday, an invitation created eleven days ago that nobody accepted. Revoking the stale session and re-issuing the invite are two calls, both waiting on your approval. The reply is assembled from records rather than from a guess about what usually goes wrong.

What can a companion do in Clerk?

Users, sessions and invitations, all the way through.

Search and read a user, create, update, ban or unban one, list and revoke sessions, list, create and revoke invitations. Organizations can be listed, fetched and created.

Configuration stays with you at the dashboard. JWT templates, instance settings, domains, webhook endpoints, allowlists and SSO connections have no tools here, because those change how authentication behaves for every user at once.

• Users: list with search, get, create, update, delete, ban, unban.
• Sessions: list for one user or client, revoke a single session.
• Invitations: list by status, create, revoke.
• Organizations: list, get, create. No update, no delete, no membership tools.

Why does creating an invitation need a flag?

Because by default it sends a real email the moment it runs.

Set `notify` to false and the tool creates the invite and hands back the URL without sending anything. Two calls that look identical in a transcript, two very different blast radii across a list of forty addresses.

The quiet version is usually the one you want. A companion creates the forty silent invites, collects the URLs, and delivers them where the conversation already is: a reply in the thread, a message to the channel, a row in the onboarding sheet, in wording you approved. That is the operations chore that otherwise eats a morning.

Keep the destructive Clerk calls gated

The connection is a single Clerk Secret Key.

A key that can read users can also delete them, because that is Clerk’s key model rather than a decision this integration made. The control you have is which key you hand over, and a test key against a development instance answers most questions without touching a live account.

The destructive calls are marked and confirmed before they run: delete, ban, revoke session, revoke invitation. Banning is reversible and the tools prefer it, so a companion asked to get rid of an account proposes the recoverable option first.

The reading half holds most of the value and asks far less. Paging the user list with a search term and a sort order turns a signup question into a table, which is ordinary data extraction.

Frequently asked questions