PostHog Tools

The PostHog tools let a workflow send product-analytics events to PostHog, run HogQL queries against a project, and list a project's saved insights. Use these tools when you need to instrument user actions, pull analytics data into a workflow, or surface PostHog dashboards/insights programmatically.

Overview

Operations

Configuration

posthog_capture_event

Capture a single event in PostHog. Sends a POST to {host}/capture/ with the project API key embedded in the request body (no Authorization header).

posthog_query

Execute a HogQL query in a PostHog project. Sends a POST to {host}/api/projects/{projectId}/query with the body { "query": { "kind": "HogQLQuery", "query": "<your query>" } } and a Bearer Authorization header.

posthog_list_insights

List insights in a PostHog project. Sends a GET to {host}/api/projects/{projectId}/insights with a Bearer Authorization header.

Outputs

posthog_capture_event

• data (json) — The PostHog capture response.
• metadata (json) — Capture metadata. Contains:
  • status (string) — Capture status.

posthog_query

• data (json) — The HogQL query result object.
• metadata (json) — Query metadata. Contains:
  • status (string) — Query status.

posthog_list_insights

• data (json) — Array of insight objects.
• metadata (json) — List metadata. Contains:
  • count (number) — Number of insights returned.

YAML Example

posthog_1:
  type: posthog
  name: "PostHog"
  inputs:
    operation: "posthog_capture_event"
    host: "https://us.posthog.com"
    event: "button_clicked"
    distinct_id: "user123"
    properties:
      plan: "pro"
    projectApiKey: "{{POSTHOG_PROJECT_API_KEY}}"
  connections:
    outgoing:
      - target: next-block-id

A query example using the personal API key:

posthog_query_1:
  type: posthog
  name: "PostHog"
  inputs:
    operation: "posthog_query"
    host: "https://us.posthog.com"
    projectId: "12345"
    query: "SELECT event, count() FROM events GROUP BY event"
    apiKey: "{{POSTHOG_PERSONAL_API_KEY}}"
  connections:
    outgoing:
      - target: next-block-id

Tips

• Two different keys are required depending on the operation: event capture (posthog_capture_event) uses the public project API key (phc_...) sent in the request body, while posthog_query and posthog_list_insights use a personal API key (phx_...) sent as a Bearer token. Don't mix them up.
• Always set host to your region's endpoint — https://us.posthog.com for US Cloud or https://eu.posthog.com for EU Cloud (a trailing slash is stripped automatically). Self-hosted instances use their own base URL.
• For HogQL queries, the tool wraps your query string in a HogQLQuery payload automatically — pass only the raw SQL-like statement (e.g. SELECT event, count() FROM events GROUP BY event), not the full JSON envelope.