Appearance
PostHog
undefined
| Detail | Value |
|---|---|
| Category | Analytics |
| Base URL | https://app.posthog.com/api |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | posthog |
Using PostHog in a workflow
- Go to Connections and click New Connection.
- Pick PostHog from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET | Events |
GET | Persons |
GET | Feature Flags |
GET | Insights |
GET | Dashboards |
GET | Cohorts |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Events
| Detail | Value |
|---|---|
| Operation ID | events_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PostHog connection from the Connection dropdown.
- In the Operation dropdown, select
events_0. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream PostHog API reference.
GET
Persons
| Detail | Value |
|---|---|
| Operation ID | persons_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PostHog connection from the Connection dropdown.
- In the Operation dropdown, select
persons_1. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream PostHog API reference.
GET
Feature Flags
| Detail | Value |
|---|---|
| Operation ID | feature_flags_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PostHog connection from the Connection dropdown.
- In the Operation dropdown, select
feature_flags_2. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream PostHog API reference.
GET
Insights
| Detail | Value |
|---|---|
| Operation ID | insights_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PostHog connection from the Connection dropdown.
- In the Operation dropdown, select
insights_3. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream PostHog API reference.
GET
Dashboards
| Detail | Value |
|---|---|
| Operation ID | dashboards_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PostHog connection from the Connection dropdown.
- In the Operation dropdown, select
dashboards_4. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream PostHog API reference.
GET
Cohorts
| Detail | Value |
|---|---|
| Operation ID | cohorts_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your PostHog connection from the Connection dropdown.
- In the Operation dropdown, select
cohorts_5. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream PostHog API reference.