Skip to content
One platform. From customer conversation to completed work.Take a closer look
All connections
Monitoring · CONNECTION

PostHog + NodeHub

Capture events with a project token, or read exact people, recent activity and recording metadata with a separate private-read connection.

Explore 8 workflow actions for PostHog, including account permissions and operation limits.

3 read actions5 write actions
WORKFLOW ACTIONS

What you can configure.

Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.

Create alias

Write

Merge one distinct ID into another, so both belong to the same person.

Permissions and limits

Account permissions

  • The project token

Operation limits

  • PostHog takes no idempotency key, so a lost answer stays uncertain and is never resent automatically; a repeat would record the event twice.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Create event

Write

Capture a custom event for a person.

Permissions and limits

Account permissions

  • The project token

Operation limits

  • PostHog takes no idempotency key, so a lost answer stays uncertain and is never resent automatically; a repeat would record the event twice.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Identify person

Write

Set person properties.

Permissions and limits

Account permissions

  • The project token

Operation limits

  • PostHog takes no idempotency key, so a lost answer stays uncertain and is never resent automatically; a repeat would record the event twice.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Look up person by distinct ID

Read

Read the person whose native distinct IDs contain the explicit exact identifier in the saved project.

Permissions and limits

Account permissions

  • Personal API key with person:read in the selected project

Operation limits

  • Uses the saved US or EU private API host and project ID. Those bindings cannot be overridden by a workflow or changed by a credential edit; create another connection for another project or region.
  • Returns zero or one exact native match. Multiple results, unresolved pagination, mismatched distinct IDs and partial responses fail explicitly. Provider next URLs are never followed.
  • Person properties and undeclared provider fields are excluded. Local limits: one result, 1000 distinct IDs of up to 512 characters, 2000-character display name, safe integer person ID and existing 2 MB transport response cap.
  • This lookup does not read activity, session recordings, send capture events, or merge customer profiles.

Read recent person events

Read

Read a bounded first page of activity for an exact distinct ID, after verifying its native person and aliases.

Permissions and limits

Account permissions

  • Personal API key with person:read and query:read in the selected project

Operation limits

  • First page only, a 30-second total read budget, at most 100 events in an explicit absolute window of at most 24 hours. hasMore is the native limit+1 completeness signal; narrow the window when true. No cursor or URL is followed.
  • The server fixes EventsQuery, person UUID, columns and ordering. No HogQL, properties, arbitrary query, host, project or filter inputs are accepted.
  • Native person ID, UUID and exact alias set are checked again after the query. Events may use any exact alias from that verified set. Changed identity, partial results, warnings and asynchronous tasks fail explicitly.
  • Returns only event UUID, name, timestamp and distinct ID. It does not read session recordings, capture events or merge customer profiles.

Read recent person recordings

Read

Read a bounded first page of recording metadata for a verified exact person and aliases. No playback or download content is retrieved.

Permissions and limits

Account permissions

  • Personal API key with person:read and query:read in the selected project for this operation.

Operation limits

  • Metadata only: at most 100 recordings in a window of at most 24 hours, a 30-second total budget, first page only. Native has_next becomes hasMore; narrow the window when true. No cursor or provider URL is followed.
  • Server-owned RecordingsQuery uses the verified person UUID and exact alias set. No email inference, arbitrary filters, global recording list, query expressions or region/project overrides are accepted.
  • Recording IDs are exact nonempty UTF-8 strings of at most 512 bytes. Every returned distinct ID must belong to the verified alias set. Missing/null IDs and unknown aliases, changed identity, warnings, asynchronous tasks and inconsistent completeness evidence fail instead of returning a filtered partial list.
  • Bounds apply inclusively to native recording segment starts. Recording end metadata may extend beyond the requested start window. Playback data, downloads, URLs, person properties, viewers and generated queries are excluded.

Track page

Write

Capture a pageview.

Permissions and limits

Account permissions

  • The project token

Operation limits

  • PostHog takes no idempotency key, so a lost answer stays uncertain and is never resent automatically; a repeat would record the event twice.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Track screen

Write

Capture a mobile screen view.

Permissions and limits

Account permissions

  • The project token

Operation limits

  • PostHog takes no idempotency key, so a lost answer stays uncertain and is never resent automatically; a repeat would record the event twice.

A repeated request may repeat the external action. Review the previous result before retrying a write.

SETUP

Start with a controlled test.

01Connect the intended account

Use the account and permissions required for your process. Review the connection check before configuring a workflow action.

02Review inputs and access

Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.

03Confirm the result

Inspect step outputs and confirm the result in PostHog. A saved workflow is not a completed provider action.

Follow the workflow quickstart
EXPLORE YOUR STACK

More in Monitoring.

PostHog integration | NodeHub