Linking FusionAuth as a source
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.
This source is currently in alpha. The interface and available tables may change.
Enter your FusionAuth instance's base URL and an API key to pull your FusionAuth authentication and identity data – users, audit logs, event logs, and login records – into the PostHog data warehouse.
Adding a data source
- Go to the sources tab of the data pipeline section in PostHog.
- Click + New source and then click Link next to FusionAuth.
- Next, gather your FusionAuth credentials:
- Base URL – your FusionAuth instance URL (e.g.
https://your-instance.fusionauth.io). Must use HTTPS. - API key – create one in the FusionAuth admin UI under Settings > API Keys. The key needs read access to the endpoints you want to sync.
- Base URL – your FusionAuth instance URL (e.g.
- Back in PostHog, enter the credentials and click Next.
- Select the tables you want to sync, set the sync method and frequency, then click Import.
Once the syncs are complete, you can start using FusionAuth data in PostHog.
Required API key permissions
The API key needs read access to the resources you want to sync:
/api/user/search/api/system/audit-log/search/api/system/event-log/search/api/system/login-record/search
Available tables
| Table | Description | Sync method |
|---|---|---|
Users | User accounts, including registrations, contact info, and account timestamps | Full refresh |
AuditLogs | Administrative actions taken in the FusionAuth admin UI or API | Incremental |
EventLogs | Internal FusionAuth system events such as errors and informational messages | Incremental |
LoginRecords | Every successful and failed login attempt against a FusionAuth application | Incremental |
Incremental tables sync only new or updated records on each run. Full refresh tables reload all data on each sync.
Sync limitations
- The Users table is full refresh only because the FusionAuth search API has no documented server-side timestamp filter. The search result window is also capped at approximately 10,000 rows.
- AuditLogs, EventLogs, and LoginRecords require Elasticsearch to be configured on your FusionAuth instance.
Configuration
| Option | Type | Required |
|---|---|---|
FusionAuth base URL | text | Yes |
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Users | Full sync only; the search API's result window is capped at ~10,000 rows. | Full refresh | — | — |
AuditLogs | Administrative actions taken in the FusionAuth admin UI or API, such as user or configuration changes. | Incremental, Full refresh | insertInstant | — |
EventLogs | Internal FusionAuth system events, such as errors and informational/debug messages. | Incremental, Full refresh | insertInstant | — |
LoginRecords | A record of every successful and failed login attempt against a FusionAuth application. | Incremental, Full refresh | instant | — |