amplitude-automation

What This Skill Does

The amplitude-automation skill provides an interface to the Amplitude product analytics platform via the Rube MCP (Composio) framework. It allows OpenClaw users to programmatically interact with their event data, user profiles, and activity streams without manually navigating the Amplitude dashboard. By leveraging the underlying Rube MCP, this skill acts as a middleware, ensuring that authentication is managed securely and that event ingestion, user identification, and history retrieval are executed through standard API flows. It is designed to bridge the gap between AI-driven task automation and complex product analytics infrastructures.

Installation

To install this skill, use the command: clawhub install openclaw/skills/skills/sohamganatra/amplitude-automation. After installation, ensure you have the Rube MCP server configured at https://rube.app/mcp within your OpenClaw settings. You must initialize the connection by calling RUBE_MANAGE_CONNECTIONS with the toolkit parameter set to 'amplitude'. Ensure the status returns 'ACTIVE' before proceeding with any automation tasks.

Use Cases

• Real-time Event Tracking: Developers can pipe application events directly from their AI workflow into Amplitude to maintain a consistent data stream for product teams.
• User Journey Analysis: Support teams can quickly investigate a specific user's friction points by pulling their recent event history through the Find and Get Activity workflow.
• User Profile Management: Automatically update user segments or properties during onboarding flows to trigger personalized experiences within Amplitude cohorts.

Example Prompts

1. "Send a 'sign_up' event for user_id 'user_12345' with property 'source' set to 'organic' to Amplitude."
2. "Look up the user activity for user_id 'customer_99' and show me their last 10 actions."
3. "Identify the user 'u_778' and update their 'subscription_tier' property to 'premium' in Amplitude."

Tips & Limitations

• Always Search First: The API surface for Amplitude can change; always invoke RUBE_SEARCH_TOOLS at the start of a session to ensure the schema matches the current MCP toolkit capabilities.
• Schema Strictness: When sending events, remember that the time parameter must be in milliseconds (13-digit epoch). Providing standard UNIX seconds will cause ingestion errors.
• Identifier Mapping: Remember that AMPLITUDE_GET_USER_ACTIVITY requires the internal Amplitude ID. You must use AMPLITUDE_FIND_USER first to map your application-specific user_id to the internal format. Failure to do so will result in lookup failures.
• Rate Limiting: Amplitude imposes batch limits; avoid sending excessively large arrays of events in a single call to prevent throttling.