How PostHog Power User Identification Agent Profiles

Your team runs this workflow every week: pull records from Posthog, Notion, Slack, cross-reference with a second source, apply judgment, format the output, and route it to 3 different stakeholders. Last Tuesday it took 30–60 minutes per cycle. This Tuesday the person who usually runs it is out sick, and nobody else knows the exact steps. The output varies by who runs it and when.

The core issue is data fragmentation. The information exists, but assembling it into actionable intelligence requires manual effort that does not scale with headcount. PostHog Power User Identification Agent closes that gap by automating the product analytics and user research workflow from data extraction through structured output delivery.

Four Agents. Weekly Power User Analysis. Top 10% Behavioral Fingerprints.

The PostHog Power User Identification Agent pipeline runs 4 agents in sequence. The Fetcher pulls data from Posthog and Notion and Slack, and The Formatter delivers the output. Here is what happens at each stage and why it matters.

• The Fetcher (Code-only): Queries PostHog API for user-level activity data — event counts, feature usage breadth, session frequency, session depth, and engagement patterns.
• The Assembler (Code-only): Segments users into power users (top 10% by composite activity score) and baseline users (bottom 50%).
• The Analyst (Tier 2 Classification): Identifies what differentiates power users from baseline: aha moment features, onboarding paths that lead to power usage, feature combinations that correlate with retention, and activation patterns.
• The Formatter (Tier 3 Creative): Generates a Notion power user analysis report with behavioral fingerprints, segment comparison tables, and aha moment identification, plus a Slack digest with top 3 actionable insights for improving activation..

When the pipeline completes, you get structured output that is ready to act on. The blueprint bundle includes everything needed to deploy, configure, and customize the workflow:

• 24-node main workflow + 3-node scheduler
• Weekly power user behavioral analysis from PostHog user data
• Top 10% vs bottom 50% behavioral comparison
• Power user fingerprints: most-used features, session patterns, engagement cadence
• Aha moment identification — features that correlate with power user conversion
• Onboarding path analysis showing which early actions predict power usage
• Feature combination analysis revealing sticky feature clusters
• Activation pattern identification for growth team experiments
• Segment profile cards with behavioral characteristics
• Notion power user analysis report with fingerprints and segment comparison
• Slack digest with top 3 actionable insights for improving activation
• Configurable: power user threshold, activity metrics, lookback window
• Full technical documentation + system prompts

All scoring criteria, output formats, and routing rules are configurable in the system prompts — no workflow JSON edits required. This means PostHog Power User Identification Agent adapts to your specific process, terminology, and integration requirements without forking the entire workflow.

Understanding how the pipeline works helps you customize it for your environment and troubleshoot issues when they arise. Here is a step-by-step walkthrough of the PostHog Power User Identification Agent execution flow.

Step 1: The Fetcher

Tier: Code-only

The pipeline starts here. Queries PostHog API for user-level activity data — event counts, feature usage breadth, session frequency, session depth, and engagement patterns. Retrieves the full user activity distribution for percentile analysis.

This stage ensures all downstream agents receive clean, validated input. If this step returns incomplete data, every downstream agent works with a degraded picture.

Step 2: The Assembler

Tier: Code-only

Segments users into power users (top 10% by composite activity score) and baseline users (bottom 50%). Computes behavioral fingerprints: most-used features, session patterns, feature adoption sequence, time-to-first-value, and engagement cadence for each segment.

Why this step matters: The result is a prioritized action queue, not just a data dump.

Step 3: The Analyst

Tier: Tier 2 Classification

Identifies what differentiates power users from baseline: aha moment features, onboarding paths that lead to power usage, feature combinations that correlate with retention, and activation patterns. Generates actionable insights for product and growth teams.

Every field in the output is structured for the next agent to consume without parsing.

Step 4: The Formatter

Tier: Tier 3 Creative

This is the final deliverable — what lands in your inbox or dashboard. Generates a Notion power user analysis report with behavioral fingerprints, segment comparison tables, and aha moment identification, plus a Slack digest with top 3 actionable insights for improving activation.

The entire pipeline executes without manual intervention. From trigger to output, every decision point follows a documented path. Every execution produces a traceable audit trail.

All nodes have been validated during Independent Test Protocol (ITP) testing on n8n v2.7.5. The error handling matrix in the bundle documents the recovery path for each failure mode.

n8n strips error prefixes during message propagation. An error thrown as "VALIDATION_ERROR: Missing required field" arrives at the error handler as "Missing required field." Every error handler matches on content that survives the pipeline — forbidden phrases, field names, status codes — not on prefixes that get stripped.

— ForgeWorkflows Engineering

Weekly power user behavioral analysis with top 10% vs bottom 50% comparison, aha moment identification, onboarding path analysis, and activation pattern insights delivered via Notion and Slack.

The primary operating cost for PostHog Power User Identification Agent is the per-execution LLM inference cost. Based on Independent Test Protocol (ITP) testing, the measured cost is: Cost per Run: $0.03–$0.10 per run. This figure includes all API calls across all agents in the pipeline — not just the primary reasoning step, but every classification, scoring, and output generation call.

To put this in context, consider the manual alternative. A skilled team member performing the same work manually costs $50–75/hour for an operations analyst at a fully loaded rate (salary, benefits, tools, overhead). If the manual version of this workflow takes 30–60 minutes per cycle, the per-execution cost in human labor is significant. The blueprint executes the same pipeline for a fraction of that cost, with consistent quality and zero fatigue degradation.

Infrastructure costs are separate from per-execution LLM costs. You will need an n8n instance (self-hosted or cloud) and active accounts for the integrated services. The estimated monthly infrastructure cost is ~$0.03-0.10 per weekly run + PostHog subscription., depending on your usage volume and plan tiers.

Quality assurance: Blueprint Quality Standard (BQS) audit result is 12/12 PASS. ITP result is 8/8 records, 14/14 milestones. These are not marketing claims — they are test results from structured inspection protocols that you can review in the product documentation.

All cost and performance figures are ITP-measured — tested against real data fixtures on n8n v2.7.5 in March 2026. See the product page for full test methodology.

6 files.

When you purchase PostHog Power User Identification Agent, you receive a complete deployment bundle. This is not a SaaS subscription or a hosted service — it is a set of files that you own and run on your own infrastructure. Here is what is included:

• CHANGELOG.md — Version history
• README.md — Setup and configuration guide
• docs/TDD.md — Technical Design Document
• posthog_power_user_identification_agent_v1_0_0.json — n8n workflow (main pipeline)
• schemas/assembler_output.json — Assembler output schema
• schemas/fetcher_output.json — Fetcher output schema
• system_prompts/analyst_system_prompt.md — Analyst system prompt
• system_prompts/formatter_system_prompt.md — Formatter system prompt
• workflow/phpui_scheduler_v1_0_0.json — Scheduler workflow

Start with the README.md. It walks through the deployment process step by step, from importing the workflow JSON into n8n to configuring credentials and running your first test execution. The dependency matrix lists every required service, API key, and estimated cost so you know exactly what you need before you start.

Every file in the bundle is designed to be read, understood, and modified. There is no obfuscated code, no compiled binaries, and no phone-home telemetry. You get the source, you own the source, and you control the execution environment.

PostHog Power User Identification Agent is built for Product, Growth teams that need to automate a specific workflow without building from scratch. If your team matches the following profile, this blueprint is designed for you:

• You operate in a product or growth function and handle the workflow this blueprint automates on a recurring basis
• You have (or are willing to set up) an n8n instance — self-hosted or cloud
• You have active accounts for the required integrations: PostHog account with user-level event data, Anthropic API key, Notion workspace, Slack workspace (Bot Token with chat:write)
• You have API credentials available: Anthropic API, PostHog API Key, Slack (Bot Token, httpHeaderAuth Bearer), Notion (httpHeaderAuth Bearer)
• You are comfortable importing a workflow JSON and configuring API keys (the README guides you, but basic technical comfort is expected)

This is NOT for you if:

• Does not contact or message power users directly — it identifies patterns for your team to act on
• Does not create user segments in PostHog — it analyzes and reports, your team creates segments based on findings
• Does not work with non-PostHog analytics tools — this is PostHog-specific
• Does not predict individual user behavior — it identifies aggregate patterns across user segments
• Does not guarantee activation improvements — it reveals behavioral patterns that teams must translate into product changes

Review the dependency matrix and prerequisites before purchasing. If you are unsure whether your environment meets the requirements, contact support@forgeworkflows.com before buying.

Every pipeline has boundaries. These are intentional design decisions, not oversights — understanding them helps you deploy with the right expectations and plan for edge cases in your environment.

Does not contact or message power users directly — it identifies patterns for your team to act on

This is intentional. We default to human-in-the-loop for actions that carry reputational or financial risk. Once your team has validated output accuracy over 20+ cycles, you can adjust the pipeline to auto-execute — the workflow JSON supports it, but the default is conservative.

Does not create user segments in PostHog — it analyzes and reports, your team creates segments based on findings

We scoped this boundary after ITP testing revealed inconsistent results when the pipeline attempted this. The agents handle what they handle well — extending beyond this scope requires custom prompt engineering specific to your data shape.

Does not work with non-PostHog analytics tools — this is PostHog-specific

This keeps the pipeline focused on a single workflow. Adding this capability would introduce branching logic that varies by organization, and the tradeoff between complexity and reliability was not worth it for a reusable blueprint. Fork the workflow JSON if your use case demands it.

Deployment follows a structured sequence. The PostHog Power User Identification Agent bundle is designed for the following tools: n8n, Anthropic API, PostHog, Notion, Slack. Here is the recommended deployment path:

1. Step 1: Import workflows and configure credentials. Import both workflow JSON files into n8n (main + scheduler). Configure PostHog API key (httpHeaderAuth), Notion API token (httpHeaderAuth with Bearer prefix), Slack Bot Token (httpHeaderAuth with Bearer prefix, chat:write scope), and Anthropic API key following the README.
2. Step 2: Configure power user analysis parameters. Set POSTHOG_PROJECT_ID, POWER_USER_THRESHOLD (default 0.1 for top 10%), ACTIVITY_METRICS (event names for composite scoring), LOOKBACK_DAYS (default 28), NOTION_DATABASE_ID, and SLACK_CHANNEL in the scheduler Payload Builder node.
3. Step 3: Activate scheduler and verify. Update the webhook URL in the scheduler to match your main workflow webhook path. Activate both workflows. Send a test POST with _is_itp: true and sample user data. Verify the analysis report appears in Notion and the digest appears in Slack.

Before running the pipeline on live data, execute a manual test run with sample input. This validates that all credentials are configured correctly, all API endpoints are reachable, and the output format matches your expectations. The README includes test data examples for this purpose.

Once the test run passes, you can configure the trigger for production use (scheduled, webhook, or event-driven — depending on the blueprint design). Monitor the first few production runs to confirm the pipeline handles real-world data as expected, then let it run.

For technical background on how ForgeWorkflows blueprints are built and tested, see the Blueprint Quality Standard (BQS) methodology and the Inspection and Test Plan (ITP) framework. These documents describe the quality gates every blueprint passes before listing.

Ready to deploy? View the PostHog Power User Identification Agent product page for full specifications, pricing, and purchase.