What gets indexed
- Dashboards - Names, descriptions, and dashboard tiles
- Insights - Saved charts and queries with their filter configurations
- Feature flags - Flag keys, names, rollout percentages, and targeting rules
- Experiments - A/B tests with parameters and feature flag associations
- Surveys - Survey configurations, questions, and targeting
- Annotations - Date markers and notes on your analytics
The connector indexes your PostHog configuration and metadata, not raw event data. Event data is queried directly via the HogQL tool (see below).
HogQL query tool
In addition to indexing configuration, the PostHog connector enables direct querying of your event data using HogQL (PostHog’s SQL-like query language).What you can query
- Events - All tracked events with properties
- Persons - User profiles and properties
- Sessions - Session data and metrics
Example HogQL queries
Setup
1
Generate a Personal API Key
- In PostHog, go to Settings > Personal API Keys
- Click Create Personal API Key
- Give it a descriptive name (e.g., “Grapevine Integration”)
- Copy the generated key
Personal API keys provide access based on your user permissions. Ensure you have access to the projects you want to index.
2
Connect to Grapevine
- In Grapevine, go to Integrations and click on PostHog
- Enter your Personal API Key
- Enter your PostHog Host:
- US Cloud:
https://us.posthog.com - EU Cloud:
https://eu.posthog.com - Self-hosted: Your PostHog instance URL
- US Cloud:
- Click Connect
3
Select projects
- After connecting, Grapevine will fetch your accessible projects
- Select which projects you want to index
- Click Save to confirm your selection
4
Indexing begins
Grapevine will begin indexing your PostHog configuration from the selected projects. The initial sync may take time depending on the number of dashboards, insights, and feature flags.
Required permissions
Your Personal API Key needs read access to the following resources:| Resource | Purpose |
|---|---|
| Annotations | Index date markers |
| Dashboards | Index dashboard configurations |
| Experiments | Index A/B test configurations |
| Feature Flags | Index flag configurations |
| Insights | Index saved charts and queries |
| Projects | List and access project data |
| Query API | Execute HogQL queries on event data |
| Surveys | Index survey configurations |
Personal API keys inherit your user permissions. If you can access a resource in the PostHog UI, your API key can access it too.
Sync behavior
- Initial sync - Indexes all dashboards, insights, feature flags, experiments, surveys, and annotations from selected projects
- Ongoing syncs - Runs periodically to capture changes
- Deletions - Deleted and archived items are removed from the index
Rate limits
PostHog enforces API rate limits on different endpoint categories:| Endpoint Type | Rate Limit |
|---|---|
| Analytics endpoints | 240/min, 1,200/hour |
| Query endpoint (HogQL) | 2,400/hour |
| CRUD operations | 480/min, 4,800/hour |
| Feature flag evaluation | 600/min |
For high-volume workspaces, rate limits may slow the initial sync. The connector implements automatic retry with exponential backoff.
Limitations
- Raw event data is not indexed (query it via HogQL instead)
- HogQL queries are read-only
- Self-hosted instances must be accessible from Grapevine’s infrastructure
- Personal API keys are scoped to user permissions