> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Clerk as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/clerk

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://app.posthog.com` (app host for links).

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Clerk connector can link users, organizations, organization memberships, and invitations to PostHog.

To link Clerk:

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.

2.  Click **\+ New source** and then click **Link** next to Clerk.

3.  Next, you need a secret key from Clerk. Go to your [API keys settings](https://dashboard.clerk.com/last-active?path=api-keys) in Clerk. Copy the **Secret key** value.

4.  Back in PostHog, paste the secret key in the `Secret key` field and click **Next**.

5.  On the next page, set up the schemas you want to sync and modify the method and frequency as needed. Once done, click **Import**.

Once the syncs are complete, you can start using Clerk data in PostHog.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Secret key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `users` | A user account in the Clerk instance, including identity and authentication details. | Webhook, Full refresh | — | — |
| `organizations` | An organization in the Clerk instance that groups users into a shared team. | Webhook, Full refresh | — | — |
| `organization_memberships` | A membership linking a user to an organization, with their role in it. | Webhook, Full refresh | — | — |
| `invitations` | An invitation sent to an email address to join the Clerk instance. | Full refresh | — | — |
| `sessions` | A session created when a user signs in, tracking that sign-in until it ends or expires. | Full refresh | — | — |
| `organization_invitations` | An invitation asking a user to join an organization in the Clerk instance. | Full refresh | — | — |
| `organization_domains` | A verified email domain attached to an organization, used to enroll matching users. | Full refresh | — | — |
| `organization_roles` | A role that can be assigned to members of an organization, with the permissions it grants. | Full refresh | — | — |
| `organization_permissions` | A permission that can be granted to an organization role. | Full refresh | — | — |
| `role_sets` | A named set of organization roles, including the default and creator roles it assigns. | Full refresh | — | — |
| `waitlist_entries` | An email address on the instance waitlist, with where it is in the waitlist flow. | Full refresh | — | — |
| `allowlist_identifiers` | An email address, phone number or domain allowed to sign up to the Clerk instance. | Full refresh | — | — |
| `blocklist_identifiers` | An email address, domain, phone number or wallet blocked from signing up to the instance. | Full refresh | — | — |
| `domains` | A primary or satellite domain the Clerk instance is served from. | Full refresh | — | — |
| `saml_connections` | A SAML connection linking the Clerk instance to an external identity provider. | Full refresh | — | — |
| `enterprise_connections` | An enterprise SSO connection (SAML, OIDC or EASIE) configured on the Clerk instance. | Full refresh | — | — |
| `oauth_applications` | An OAuth application registered on the Clerk instance so other apps can sign users in with it. | Full refresh | — | — |
| `machines` | A machine identity that can authenticate to the Clerk instance without a user. | Full refresh | — | — |
| `api_keys` | An API key issued by the Clerk instance to a user, organization or machine. | Full refresh | — | — |
| `m2m_tokens` | A machine-to-machine token minted for a machine identity. | Full refresh | — | — |
| `redirect_urls` | A URL allowed as a redirect target for the Clerk instance's authentication flows. | Full refresh | — | — |
| `jwt_templates` | A template describing the claims Clerk puts into JWTs it mints for your app. | Full refresh | — | — |
| `email_templates` | An email template the Clerk instance sends, either the Clerk default or your override. | Full refresh | — | — |
| `sms_templates` | An SMS template the Clerk instance sends, either the Clerk default or your override. | Full refresh | — | — |
| `commerce_plans` | A billing plan users or organizations can subscribe to through Clerk billing. | Full refresh | — | — |
| `commerce_subscription_items` | A subscription to a Clerk billing plan held by a user or an organization. | Full refresh | — | — |