posthog-automationlisted

# PostHog Automation via Rube MCP Automate PostHog product analytics and feature flag management through Composio's PostHog toolkit via Rube MCP. ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active PostHog connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `posthog` - Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas ## Setup **Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. 1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `posthog` 3. If connection is not ACTIVE, follow the returned auth link to complete PostHog authentication 4. Confirm connection status shows ACTIVE before running any workflows ## Core Workflows ### 1. Capture Events **When to use**: User wants to send event data to PostHog for analytics tracking **Tool sequence**: 1. `POSTHOG_CAPTURE_EVENT` - Send one or more events to PostHog [Required] **Key parameters**: - `event`: Event name (e.g., '$pageview', 'user_signed_up', 'purchase_completed') - `distinct_id`: Unique user identifier (required) - `properties`: Object with event-specific properties - `timestamp`: ISO 8601 timestamp (optional; defaults to server time) **Pitfalls**: - `distinct_id` is required for every event; identifies the user/device - PostHog system events use `$` prefix (e.g., '$pageview', '$identify') - Custom