Clerk Tools

Clerk is an authentication and user management platform. Use these tools in your workflows to programmatically manage users, organizations, and sessions — for example, syncing new sign-ups to a CRM, automating user provisioning, or revoking sessions on security events.

Overview

Operations

Configuration

clerk_list_users

GET https://api.clerk.com/v1/users

clerk_get_user

GET https://api.clerk.com/v1/users/{userId}

clerk_create_user

POST https://api.clerk.com/v1/users

clerk_update_user

PATCH https://api.clerk.com/v1/users/{userId}

clerk_delete_user

DELETE https://api.clerk.com/v1/users/{userId}

clerk_list_organizations

GET https://api.clerk.com/v1/organizations

clerk_get_organization

GET https://api.clerk.com/v1/organizations/{organizationId}

clerk_create_organization

POST https://api.clerk.com/v1/organizations

clerk_list_sessions

GET https://api.clerk.com/v1/sessions

clerk_revoke_session

POST https://api.clerk.com/v1/sessions/{sessionId}/revoke

Outputs

clerk_list_users

• users (array) — Array of Clerk user objects matching the query
• totalCount (number) — Total number of users matching the query (from x-total-count response header)

clerk_get_user

• id (string) — User ID
• username (string) — Username
• firstName (string) — First name
• lastName (string) — Last name
• emailAddresses (array) — List of email address objects associated with the user

clerk_create_user

• id (string) — Created user ID
• emailAddresses (array) — Email addresses associated with the new user

clerk_update_user

• id (string) — Updated user ID
• emailAddresses (array) — Email addresses associated with the user

clerk_delete_user

• id (string) — Deleted user ID
• deleted (boolean) — Whether the user was successfully deleted

clerk_list_organizations

• organizations (array) — Array of Clerk organization objects
• totalCount (number) — Total number of organizations

clerk_get_organization

• id (string) — Organization ID
• name (string) — Organization name

clerk_create_organization

• id (string) — Created organization ID
• name (string) — Organization name
• slug (string) — Organization slug

clerk_list_sessions

• sessions (array) — Array of Clerk session objects
• totalCount (number) — Total number of sessions (from x-total-count response header)

clerk_revoke_session

• id (string) — Session ID
• status (string) — Session status after revocation (revoked)

YAML Example

clerk_1:
  type: clerk
  name: "Clerk"
  inputs:
    operation: "clerk_list_users"
    secretKey: "{{CLERK_SECRET_KEY}}"
    limit: 50
    query: "{{trigger.searchQuery}}"
  connections:
    outgoing:
      - target: next-block-id

Tips

• Your Clerk Secret Key starts with sk_live_ (production) or sk_test_ (development). Store it as an environment variable and reference it as {{CLERK_SECRET_KEY}} — never hardcode it in a workflow.
• When filtering list endpoints with comma-separated values (e.g. emailAddress, userId), the tool splits them automatically and sends each as a separate query parameter, which is what the Clerk API expects.
• To revoke all sessions for a user during a security incident, first call clerk_list_sessions with the userId filter and status: active, then loop over the results and call clerk_revoke_session for each session ID using {{clerkListSessions.sessions}}.