POSTHOG n8n INTEGRATION: AUTOMATE POSTHOG WITH N8N

The Create Event action is the backbone of PostHog tracking in n8n. It allows you to send custom events to PostHog from any trigger in your workflow, giving you complete flexibility over what user interactions and system events get logged in your analytics.

Key parameters:

• Event (required): A text field where you define the name of the event being tracked. Use descriptive, consistent naming conventions like purchase_completed, feature_activated, or support_ticket_opened.
• Distinct ID (required): The unique identifier for the user associated with this event. This is crucial for accurate user behavior tracking and should match the ID you use across all your PostHog integrations.
• Additional Fields: Optional key-value pairs that add context to your event. Add properties like plan_type, revenue_amount, referral_source, or any custom data relevant to your analysis.

Use cases:

• Track subscription_upgraded events when a Stripe webhook fires
• Log form_submitted events from Typeform responses with form field data as properties
• Record task_completed events from project management tools like Asana or Monday.com

The Track Page action records page view events in PostHog, essential for understanding user navigation patterns and content engagement. This action is particularly valuable when you're tracking page views from server-side applications or external systems that don't have PostHog's JavaScript snippet installed.

Key parameters:

• Name (optional): A text input field where you specify the name of the page being tracked, such as "Product Page", "Checkout", or "Blog Article". If left empty, you can use expressions to dynamically pull the page name from incoming data.
• Distinct ID (optional): The unique identifier for the user viewing the page. While optional, providing this ensures accurate user journey mapping.
• Additional Fields: Add custom properties like URL, referrer, UTM parameters, or page category. This section accepts key-value pairs and is invaluable for detailed page analytics.

Use cases:

• Track page views from headless CMS webhooks when content is accessed
• Log documentation page visits from your knowledge base API
• Record landing page views with full UTM tracking from marketing automation platforms

The Track Screen action is designed specifically for mobile and application screen tracking. If you're building mobile apps or desktop applications, this action ensures your screen views are properly logged in PostHog with all the relevant metadata.

Key parameters:

• Name (optional): The name of the screen being tracked. Use consistent naming like HomeScreen, ProfileSettings, or OnboardingStep3 to maintain clean analytics.
• Distinct ID (optional): The unique user identifier associated with this screen view. Essential for tracking individual user journeys through your app.
• Additional Fields: Add custom properties such as screen_category, previous_screen, session_id, or app-specific metadata. Click "Add Field" to define key-value pairs for granular data collection.

Use cases:

• Track mobile app screen transitions when your backend receives app analytics
• Log screen views from React Native or Flutter apps via your API
• Record kiosk or embedded application screen navigation

The Create Identity action establishes or updates user profiles in PostHog, allowing you to attach properties and metadata to specific users. This is fundamental for user segmentation, cohort analysis, and personalized analytics.

Key parameters:

• Distinct ID (required): The unique identifier for the identity being created. This should be consistent with the IDs you use throughout your PostHog tracking—typically a user ID from your database or authentication system.
• Additional Fields: Add user properties like email, name, plan_type, company, signup_date, or any custom attributes. These properties power PostHog's user profiles and enable advanced segmentation.

Use cases:

• Automatically create PostHog identities when users sign up via Auth0 or Firebase
• Update user properties when CRM data changes in HubSpot or Salesforce
• Sync user profile information from your database when records are modified

This action is particularly powerful when combined with event tracking—create the identity first, then all subsequent events with that distinct ID automatically inherit the user context.

The Create Alias action links multiple identifiers to the same user, solving one of the trickiest problems in analytics: identity resolution. When users interact with your product before and after authentication, their actions may be tracked under different IDs. This action merges those identities.

Key parameters:

• Alias (required): The new alias to be created—typically the anonymous or temporary identifier you want to link to the main user profile.
• Distinct ID (required): The primary user identifier that the alias should be connected to. This is usually the authenticated user ID from your database.
• Additional Fields: Add custom properties relevant to the alias creation event, such as alias_type, merge_timestamp, or source_platform.

Use cases:

• Link anonymous session IDs to authenticated user IDs after login
• Merge user identities when accounts are consolidated
• Connect marketing automation IDs to your internal user database for attribution tracking

💡 Pro tip: Set up an alias creation workflow that triggers immediately after user authentication. This ensures all pre-login activity (landing page views, feature exploration, signup form interactions) gets properly attributed to the authenticated user profile.