What AI Employees can do with PostHog
Example tasks your workforce can handle once PostHog is connected.
Summarize recent activity in PostHog for your team
Create and update records in PostHog from email or chat context
Trigger follow-up work when something changes in reporting and insights
Route exceptions to the right person with full context attached
Why use Odella with PostHog?
AI-native PostHog integration
- Native connection flow: AI Employees work inside PostHog, not through brittle copy-paste
- 520 actions across 11 toolkits, structured for reliable AI Employee execution
- 11 triggers so AI Employees respond when PostHog changes
Managed auth
- Secure OAuth and credential storage, no API keys pasted into prompts
- Central place to connect, scope, and revoke PostHog access per AI Employee
- Per-worker credentials instead of shared keys sitting in workflow configs
Built for AI Employees
- Tools scoped to what each worker actually needs from PostHog
- Fits into broader employee workflows, not isolated one-off automations
- Clear work history so you always know what ran, when, and on whose behalf
Enterprise-grade security
- Control which AI Employees can access PostHog and what they can do
- Scoped, least-privilege permissions per worker
- Human approval gates for sensitive actions before they execute
Capabilities
Toolkits, triggers, and actions available to your AI Employees through PostHog.
Action Performed
Triggers when an event matches one of the saved PostHog Actions you configure. Use this instead of Event Captured when the behaviour you care about spans several event names or element matches, and you want PostHog's Action definition to stay the single place it is described. Deliveries count toward your PostHog data pipelines usage, so it pays to watch just the Actions you act on.
Activity Log Entry Created
Triggers when PostHog records an activity-log entry for the project — any audited change to a feature flag, insight, dashboard, destination, experiment or survey. This is the whole audit stream, so it is high volume; branch on `scope` and `activity` for the changes you care about.
Early Access Feature Updated
Triggers when an early-access feature changes — most usefully when it moves between stages, such as concept to beta to general availability. The payload carries the whole feature both before and after, so compare `previous` with `next` to see what moved.
Error Tracking Issue Assigned
Triggers when an error-tracking issue is assigned to a user, a group or a role. Reassigning an already-assigned issue fires it again; clearing an assignee fires Error Tracking Issue Unassigned instead.
Error Tracking Issue Created
Triggers when PostHog groups an exception into an error-tracking issue it has never seen before. Fires once per issue, on the first occurrence — later occurrences of the same fingerprint do not fire it.
Error Tracking Issues Merged
Triggers when two or more error-tracking issues are merged into one. The payload is the surviving issue; `merged_issue_ids` names the ones that were absorbed, so anything you track against those ids should be repointed.
Error Tracking Issue Split
Triggers when fingerprints are split out of an error-tracking issue into new issues of their own. The payload is the original issue; `split_issue_ids` names the issues that were created.
Error Tracking Issue Status Changed
Triggers when an error-tracking issue is resolved, reopened or suppressed. One trigger covers all three moves because PostHog sends an identical body for each; branch on `previous_status` and `status` to tell them apart.
Error Tracking Issue Unassigned
Triggers when an error-tracking issue's assignee is cleared, leaving it unowned. Reassigning to a different person fires Error Tracking Issue Assigned instead, not this.
Event Captured
Triggers when PostHog captures one of the analytics events you name. Fires on every matching event, including ones your backend or a third-party integration sent, not only browser events. Deliveries count toward your PostHog data pipelines usage, so it pays to name just the events you act on.
Person Updated
Triggers when a person's profile changes in PostHog — a property set, updated or removed, or two people merged into one. Everything the trigger reports is in `person`: PostHog synthesises the event around the updated profile, so `event` carries no properties and `event.distinct_id` holds the person's id rather than a distinct_id. Every profile change in the project is a delivery and deliveries count toward your PostHog data pipelines usage, which is worth knowing if your project updates people in bulk.
Frequently asked questions
Common questions about connecting PostHog to your Odella AI workforce.
How do Odella AI employees connect to third-party apps?
After you hire an AI Employee, connect the integration from their settings in a few clicks. Odella handles authentication securely so your worker can read, write, and act on data in the tools your team already uses.
Can multiple AI Employees use the same integration?
Yes. Connect an integration once per AI Employee who needs it. Each worker gets their own scoped access, so responsibilities stay clear across your AI workforce.
How do triggers work with Odella AI Employees?
Where supported, triggers start work automatically when something happens in a connected app, like a new email, ticket, or record. Your AI Employee picks up the task and follows the workflow you trained them on.
Can I limit what an AI Employee does inside an integration?
Yes. Security policies let you allow or block specific actions per worker. That means you can give a junior AI Employee read-only access while a senior worker handles sends, updates, and approvals.
How quickly can I connect PostHog to an Odella AI Employee?
Most teams connect PostHog in a few minutes through Odella's native integration flow. Choose the AI Employee who needs access, authenticate securely, and define which actions they can perform.
Try PostHog now
Type what you want done, then sign in and connect PostHog to your AI workforce.
Explore other integrations
Connect more of your stack so AI Employees can work across the tools your team relies on.
