Step 1: Connect your stack
27 native integrations. 3,200+ tools via managed connectors. Most are one-click OAuth, some use API keys - Viktor handles auth and starts working. No webhooks, no Zapier zaps.
PostHog AI employee
Viktor is an AI employee that connects to PostHog and helps you track product usage and feature adoption, running 300 PostHog actions for you like Role get, User get, and Query run. Ask in plain English from your workspace; Viktor does the work in PostHog and reports back. Viktor connects natively.
Works in Slack & Microsoft Teams
What is a PostHog AI agent?
A PostHog AI agent is an AI that connects to your PostHog account and completes work in it - it doesn't just answer questions about PostHog, it takes the actions. Viktor is an AI employee that works in PostHog on your behalf and delivers the finished result to your workspace.
Unlike workflow builders such as Zapier or Make, there is nothing to configure - no triggers to map, no workflows to maintain. You describe the outcome in plain English, and Viktor picks the right PostHog actions, chains them with the other 3,200+ tools it connects to, and asks for approval before anything sensitive runs.
About PostHog
Product analytics and feature flags (US cloud)
You ask in your workspace
Describe what you need in plain English
Viktor picks the actions
Selects from 300 PostHog actions, chains them together
Runs in PostHog
Helps you track product usage and feature adoption - your real data.
Reports back
Delivers the finished result to your workspace
Try asking Viktor
What can you ask Viktor to do in PostHog?
Messages you'd actually send. Paste one into your workspace, swap in your specifics, and Viktor takes it from there.
“Pull this week's activation funnel from PostHog and flag the biggest drop-off.”
— you, to @Viktor
“Investigate why a key metric dropped in PostHog last week and report what you find.”
— you, to @Viktor
“Build a report on the new feature's adoption in PostHog and post it every Monday.”
— you, to @Viktor
“Watch PostHog for a spike in a key metric and alert me with context.”
— you, to @Viktor
How it works
How does Viktor work with PostHog?
Maya Patel11:32 AM
@Viktor check this week's Stripe revenue against HubSpot and flag anything off before the board call.
ViktorApp11:33 AM
On it. Cross-checking Stripe against HubSpot and fixing anything that doesn't line up before your board call.
Step 2: Tell Viktor what you need
Message Viktor in Slack like you'd message a teammate. "Reconcile this month's invoices and flag anything weird." "Pause Meta campaigns above $40 CPA and move the budget to winners." Plain English, any tool.
ViktorApp9:12 AM
📊 Revenue check:
$84,210 (+6.4% WoW).
3 deals didn't match HubSpot.
Fixed 2, one needs your call.
$84,210 (+6.4% WoW).
3 deals didn't match HubSpot.
Fixed 2, one needs your call.
revenue_raport.pdf
Step 3: Viktor operates, you review
Viktor opens the tools, runs the work, and posts back what changed. Sensitive actions wait for your approval. Everything is logged. You stop doing the work and start reviewing it.
Actions
What can Viktor do in PostHog?
Ask in plain English from your workspace. Viktor picks the right PostHog actions, runs the work, and reports back. No workflows to build.
- Analytics
Actions get all
Get actions in the project. Actions are reusable event definitions that can combine multiple trigger conditions (page views, clicks, form submissions) into a single trackable event for use in insights and funnels. Supports pagination with limit and offset, case-insensitive name filtering with search, filtering by creator with createdby (comma-separated user ids), filtering by tag with tags (a JSON-encoded array of tag names), and sorting with ordering. Projects can have thousands of actions, so pass limit plus the relevant filters rather than fetching every action at once.
- Analytics
Dashboards get all
List dashboards in the project. The optional search parameter runs a fuzzy match against name and description using Postgres trigram word similarity (handles typos, transpositions, and prefix-as-you-type) and returns results ranked by relevance — use it to find a specific dashboard by name rather than paging through every dashboard. search is capped at 200 characters; longer queries return a 400 error. Optional filters by tag and pinned status are also supported. Returns name, description, pinned status, tags, and creation metadata. Tiles and insights are not included — use dashboard-get to fetch a dashboard's tiles, then dashboard-insights-run to fetch the actual data for each insight.
- Organization
Org members list
List all members of the current organization with their names, emails, membership levels (member, admin, owner), and last login times.
- Surveys
Surveys get all
List surveys in the project. Use search for fuzzy match against survey name and description (handles typos and prefix-as-you-type). Use type to filter by survey kind (popover, widget, externalsurvey, api). Use archived to filter archived state. Combine with pagination via limit/offset.
- LLM Observability
Llm analytics review queues create
Create a review queue for routing traces that still need review. Queue names must be unique among active queues in the current project.
- LLM Observability
Llm analytics review queue items partial update
Move a pending trace review assignment to a different review queue by updating queueid. Fails if the trace has already been reviewed and can no longer stay queued.
- Organization
Switch organization
Switch the active PostHog organization for subsequent tool calls. Call this proactively whenever the user names an organization they want to operate on. Use organizations-list to resolve an organization name to an id. Default to the active organization when no specific organization is mentioned.
- LLM Observability
Llma skill duplicate
DEPRECATED: renamed to skill-duplicate. This alias forwards to skill-duplicate and will be removed. Call skill-duplicate directly with the same arguments.
- Conversations
Conversations tickets messages retrieve
Return a support ticket's message thread, ordered chronologically. The response is paginated (default 50, max 200 per page) — use the limit and offset query params to page through long threads, and read count/next from the response envelope. Includes all messages from the customer, team members, and AI, as well as private internal notes. Each message contains authortype, authorname, content, and an isprivate flag indicating internal notes.
Works with your stack
Viktor uses PostHog together with your other tools
Ask for outcomes that span tools - Viktor pulls from PostHog, cross-references the rest of your stack, and delivers one finished result.
Related
More Analytics integrations
Viktor connects to 3,200+ tools and works across them in a single run.
Trusted by 60,000+ teams
The moment Viktor becomes part of the team.
PostHog integration FAQ
Yes. PostHog is one of the 3,200+ tools Viktor connects to, as one of Viktor's native, deepest integrations. Once connected, anyone on your team can put Viktor to work in PostHog from their workspace - no workflow builder, no code.
4.9 on G2G2 rating: 4.9 out of 5 stars
One hire. The output of a team.
Viktor works nights, remembers every decision, and connects to 3,200 tools. Start free with $100 in credits, then $50 a month.