Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

PostHog

Open-source product analytics

CategoryBusiness Intelligence
Authenticationcustom
Version0.6.0
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect PostHog with Flows360

Open-source product analytics

Use the PostHog connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 5 actions and 1 trigger.

Available actions

  • Capture Event
  • Create Project
  • Get Feature Flags
  • List Persons
  • Custom API Call

Available triggers

  • New Event

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: PostHog
  • Package: @activepieces/piece-posthog@0.6.0
  • Exact artifact digest: sha256:d278bf1fdb80fd644be025932017e61e0c057128b91230405f64c2e20b9fa794
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Capture Event (create_event), Capture a custom event in PostHog Classification: read.
  • Create Project (create_project), Create a new PostHog project in your organization Classification: read.
  • Get Feature Flags (get_feature_flags), List all feature flags in your PostHog project Classification: read.
  • List Persons (list_persons), Get a list of identified users in your PostHog project Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Event, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects6
Supported actions5
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Personal API Key Required · protected credential
  • Project ID Required
  • API Host Optional
  • Ingestion Host Optional

Supported objects

ObjectReadWriteNotes
Capture Event Yes No Capture a custom event in PostHog
Create Project Yes No Create a new PostHog project in your organization
Get Feature Flags Yes No List all feature flags in your PostHog project
List Persons Yes No Get a list of identified users in your PostHog project
Custom API Call Yes No Make a custom API call to a specific endpoint
New Event Yes No polling trigger declared by the pinned package.

Supported actions

Capture Event · Read

Capture a custom event in PostHog

create_event · Risk: low · Retry: safe

Inputs

  • event · string · Required, The name of the event to capture
  • distinct_id · string · Required, Unique identifier for the user performing the action (e.g. user ID or email address)
  • properties · object · Optional, Additional event properties as key/value pairs
Create Project · Read

Create a new PostHog project in your organization

create_project · Risk: low · Retry: safe

Inputs

  • organization_id · string · Required, The organization to create the project in
  • name · string · Required, The name of the new project
  • anonymize_ips · boolean · Optional, Whether to anonymize incoming IP addresses
Get Feature Flags · Read

List all feature flags in your PostHog project

get_feature_flags · Risk: low · Retry: safe

Inputs

  • limit · number · Optional, Maximum number of feature flags to return (default: 100)
List Persons · Read

Get a list of identified users in your PostHog project

list_persons · Risk: low · Retry: safe

Inputs

  • limit · number · Optional, Maximum number of persons to return (default: 100)
  • search · string · Optional, Filter persons by email or name
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Event · Poll

Triggers when a new event is captured in PostHog

Inputs

  • event_name · string

Setup

Setup

  1. Add the PostHog connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Personal API Key (personal_api_key), required; stored as a sensitive connection value.
  • Project ID (project_id), required.
  • API Host (api_host), optional.
  • Ingestion Host (ingestion_host), optional.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-posthog@0.6.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required PostHog connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-posthog@0.6.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com