+
Connect Linear to Posthog
Automate Linear and Posthog with AI
Product metrics in PostHog belong on the Linear issue that tracks the feature they measure. Operator.io connects PostHog and Linear through OpenClaw so a funnel drop on an event you watch can open or comment on the linked Linear issue with current counts, Linear completion can note which PostHog event tracks the launch, and chat compares open Linear work against recent PostHog trends. Tell it which shipped features still show a conversion gap and it pulls PostHog and lists matching Linear tickets.
It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.
What your agent can do with Linear and Posthog
What your agent does in Linear
Create attachment
Creates a new attachment and associates it with a specific, existing Linear issue.
Add reaction to comment
Tool to add a reaction to an existing Linear comment. Use when you want to programmatically react to a comment on an issue.
Create a comment
Creates a new comment on a specified Linear issue. This action modifies shared workspace data and is not reversible — confirm the target issue and comment content before executing.
Create linear issue
Creates a new issue in a specified Linear project and team, requiring team_id and title, and allowing optional properties like description, assignee, state, priority, cycle, and due date. All UUID parameters (state_id, assignee_id, cycle...
Create issue relation
Create a relationship between two Linear issues using the issueRelationCreate mutation. Use this to establish connections like 'blocks', 'duplicate', or 'related' between issues.
Create a label
Creates a new label in Linear for a specified team, used to categorize and organize issues. Label names must be unique within each team. If a label with the same name already exists, the existing label will be returned. Both new and exis...
What your agent does in Posthog
Add dashboard collaborators with access level
Add collaborators to a specific project dashboard. Requires 'project_id' and 'dashboard_id'. Supports JSON, form-urlencoded, and multipart data. Returns added collaborator details. Auth: 'PersonalAPIKeyAuth'. IMPORTANT REQUIREMENTS: 1. T...
Add member to organization role
Add a member to an organization role by submitting their details and UUID in JSON/form, using organization and role IDs. Requires PersonalAPIKeyAuth. Success gives a 201 status.
Add persons to static cohort
Add persons to a static cohort by their UUIDs. Use when you need to manually add specific users to a static cohort. Only works with static cohorts (is_static=true), not dynamic cohorts.
Add product intent to project
Tool to add a product intent to a PostHog project. Use when you need to register a project's intention to use a specific PostHog product feature. Product intents help track which features (product analytics, feature flags, data warehouse...
Add project specific member roles
Add members with specific roles to a project by providing their user_uuid and level (member or admin). Requires project_id in the URL. Supports JSON, form-data, and form-urlencoded input. Returns the newly created membership data upon su...
Add session recording to playlist
Add an existing session recording to a playlist. This endpoint associates a specific session recording with a playlist, making it part of that collection. Requires 'project_id' (project identifier), 'short_id' (playlist identifier), and...
How it works
Tell the agent what you want to happen between Linear and Posthog, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Linear, works out what to do, and runs the matching action in Posthog without you mapping a single field.
You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.
Common questions about Linear and Posthog
- How do I connect Linear and Posthog to Operator?
- You authorize Linear and Posthog once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
- What can my agent do across Linear and Posthog?
- Tell it the job and it moves between Linear and Posthog as one task, choosing which actions to run on each side. There is nothing to map and no trigger to configure; you give instructions the way you would to a person.
- Can my agent keep Linear and Posthog in sync?
- Yes. It can watch Linear and act in Posthog, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
- Do I need to build a workflow or write code?
- No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.
Linear and Posthog integrations
Put your agent on Linear and Posthog
Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.
Try for free