SEGMENT n8n INTEGRATION: AUTOMATE SEGMENT WITH N8N

The Page action sends a page view event to Segment, allowing you to track which pages users visit in your application or website. This is essential for understanding user navigation patterns, measuring content engagement, and triggering page-based personalization in downstream tools.

When you configure the Page action, you're essentially telling Segment: "This user just viewed this specific page." This data then flows to all your connected destinations—Google Analytics, Mixpanel, Amplitude, or your data warehouse—in a standardized format.

Key parameters: Credential to connect with (required dropdown to select your authenticated Segment account), User ID (optional text field for the unique identifier of the user viewing the page), Name (optional text field specifying the name of the page being viewed, supports both fixed values and dynamic expressions), Context (optional section for adding key-value pairs with additional contextual information), Integration (optional section allowing you to control which downstream integrations receive this specific page event), and Properties (optional section for custom key-value pairs describing the page itself).

Typical use cases: Track page views from a headless CMS or custom web application that doesn't have native Segment integration, log "Documentation Viewed" events when users access help articles triggering customer success workflows, and send page data to Segment when users interact with embedded tools or widgets outside your main application.

When to use it: Use the Page action whenever you need to track page views from systems that can trigger n8n workflows—webhooks from your backend, form submissions that indicate page access, or any event that represents a user landing on a specific page.

The Track Event action is the workhorse of Segment's API—it sends custom events that capture specific user actions. Whether someone completes a purchase, clicks a button, uploads a file, or achieves a milestone, the Track Event action records it and sends it to all your downstream destinations.

This action is fundamental for product analytics, behavioral segmentation, and triggered marketing campaigns. Every meaningful user action can become a tracked event that powers your data-driven decisions.

Key parameters: Credential to connect with (required dropdown for selecting your Segment account credentials), Resource (required dropdown set to "Track"), Operation (required dropdown set to "Event"), User ID (optional text field for the unique identifier of the user performing the action), Event (required text field where you specify the event name like "Product Viewed" or "Subscription Started"), Context (optional section for structured contextual data), Integration (optional section for controlling which integrations receive this event), and Properties (optional but highly recommended section for event-specific metadata).

Typical use cases: Fire a "Purchase Completed" event with order details when a Stripe webhook fires, track "Lead Qualified" events when leads meet certain criteria in your CRM, send "Support Ticket Opened" events to Segment when tickets are created in Zendesk or Intercom, and log "Integration Connected" events when users authenticate third-party services in your product.

When to use it: Use Track Event for any discrete user action that matters to your business. If you'd ask "did the user do X?"—that's a track event. The more rich properties you include, the more valuable your analytics and segmentation become.

The Identify action creates or updates user profiles in Segment. This is how you tell Segment who your users are—their email addresses, names, company affiliations, plan types, and any other traits that define them. Every downstream tool connected to Segment then receives this enriched user profile data.

Identification is foundational to customer data infrastructure. Without proper identify calls, your events are just anonymous data points. With them, you can build complete user profiles that power personalized experiences across every tool in your stack.

Key parameters: Credential to connect with (required dropdown to select your Segment account credentials), Resource (required dropdown set to "Identify"), Operation (required dropdown set to "Create"), User ID (text field for the unique identifier of the user being identified), Traits (optional but essential section for user attributes like email, name, company, plan), Context (optional section for contextual information about the identification event), and Integration (optional section for specifying which integrations should receive this identify call).

Typical use cases: Automatically identify users when they sign up through a form (Typeform, JotForm, etc.), update user profiles when subscription status changes in Stripe or Chargebee, sync CRM contact data to Segment when records are created or updated in HubSpot or Salesforce, and enrich user profiles with data from enrichment tools like Clearbit or Apollo.

When to use it: Send an Identify call whenever you learn something new about a user or when user attributes change. Key moments include: signup, login, profile updates, plan changes, and any integration with systems that hold user data.

The Segment action (Group: Add) associates users with groups—typically companies, accounts, or organizations. This is essential for B2B businesses where you need to understand not just individual user behavior, but also account-level behavior and attributes.

When you group users together, you can analyze metrics at the account level, trigger account-based marketing campaigns, and personalize experiences based on company characteristics. Every user in a group shares the group's traits, enabling powerful account-level segmentation.

Key parameters: Credential to connect with (required dropdown for selecting your authenticated Segment account), Resource (required dropdown set to "Group"), Operation (required dropdown set to "Add"), User ID (optional text field for the ID of the user being added to the group), Group ID (optional text field for the unique identifier of the group), Traits (optional section for group-level attributes like company_name, industry, employee_count), Context (optional section for contextual information), and Integration (optional section for controlling which destinations receive this group call).

Typical use cases: Associate users with their companies when they're added to accounts in your CRM, update company traits when deal stages change in Salesforce or HubSpot, group users by organization when they join teams in your product, and sync account data from your billing system to keep MRR and plan traits current.

When to use it: Use the Group action whenever users belong to a larger entity—company, account, team, or organization. B2B SaaS companies especially benefit from robust group tracking, as it enables account-based analytics and marketing.