Skip to main content
The PostHog integration connects one PostHog project to a Felan team. Its current automation support includes log-alert lifecycle events. Felan does not create automations for you: create an automation and choose the alert event and filters it should handle.

​
Connect

1

Open Integrations

Select the Felan team that should receive PostHog alert events, then open Integrations.
2

Authorize PostHog

Find PostHog, select Connect, and approve the least-privilege OAuth request.
3

Select a project

Choose the PostHog project Felan should use. Felan also makes its current Logs alerts available as automation events through webhook destinations.
4

Create an automation

Open Automations, create an event automation, select a PostHog log-alert event, and add the filters and instructions you need.
The connection supports PostHog Cloud regions us, us.i, eu, and eu.i.

​
Alert events

Felan receives these lifecycle events: The normalized event data includes alert_id, alert_name, counts and threshold values, window_minutes, service_names, severity_levels, and PostHog alert/log URLs. The event ID from PostHog is preserved for delivery idempotency.

​
Filtering automations

Event filters use JSONPath against the normalized event. Examples:
PostHog can notify repeatedly while an alert remains breached, depending on its notification cooldown. Use the alert ID in filters or make the automation idempotent rather than assuming every firing notification is a new incident.

​
Reconcile and disconnect

The initial project selection subscribes the alerts that exist at that time. If a new alert is created later, open the connected PostHog integration and choose Sync project. Existing subscriptions are skipped and only new alerts are attached. Disconnecting PostHog removes Felan’s managed alert destinations before the OAuth connection and local credentials are disabled. Felan does not read or stream the project’s general analytics event firehose through this integration.