Segment Automation via Rube MCP
Automate Segment customer data platform operations through Composio's Segment toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Segment connection via
RUBE_MANAGE_CONNECTIONS with toolkit segment
- 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.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit segment
- If connection is not ACTIVE, follow the returned auth link to complete Segment authentication
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Track Events
When to use: User wants to send event data to Segment for downstream destinations
Tool sequence:
SEGMENT_TRACK - Send a single track event [Required]
Key parameters:
userId: User identifier (required if no anonymousId)
anonymousId: Anonymous identifier (required if no userId)
event: Event name (e.g., 'Order Completed', 'Button Clicked')
properties: Object with event-specific properties
timestamp: ISO 8601 timestamp (optional; defaults to server time)
context: Object with contextual metadata (IP, user agent, etc.)
Pitfalls:
- At least one of
userId or anonymousId is required
event name is required and should follow consistent naming conventions
- Properties are freeform objects; ensure consistent schema across events
- Timestamp must be ISO 8601 format (e.g., '2024-01-15T10:30:00Z')
- Events are processed asynchronously; successful API response means accepted, not delivered
2. Identify Users
When to use: User wants to associate traits with a user profile in Segment
Tool sequence:
SEGMENT_IDENTIFY - Set user traits and identity [Required]
Key parameters:
userId: User identifier (required if no anonymousId)
anonymousId: Anonymous identifier
traits: Object with user properties (email, name, plan, etc.)
timestamp: ISO 8601 timestamp
context: Contextual metadata
Pitfalls:
- At least one of
userId or anonymousId is required
- Traits are merged with existing traits, not replaced
- To remove a trait, set it to
null
- Identify calls should be made before track calls for new users
- Avoid sending PII in traits unless destinations are configured for it
3. Batch Operations
When to use: User wants to send multiple events, identifies, or other calls in a single request
Tool sequence:
SEGMENT_BATCH - Send multiple Segment calls in one request [Required]
Key parameters:
batch: Array of message objects, each with:
type: Message type ('track', 'identify', 'group', 'page', 'alias')
userId / anonymousId: User identifier
- Additional fields based on type (event, properties, traits, etc.)
Pitfalls:
- Each message in the batch must have a valid
type field
- Maximum batch size limit applies; check schema for current limit
- All messages in a batch are processed independently; one failure does not affect others
- Each message must independently satisfy its type's requirements (e.g., track needs event name)
- Batch is the most efficient way to send multiple calls; prefer over individual calls
4. Group Users
When to use: User wants to associate a user with a company, team, or organization
Tool sequence:
SEGMENT_GROUP - Associate user with a group [Required]
Key parameters:
userId: User identifier (required if no anonymousId)
anonymousId: Anonymous identifier
groupId: Group/organization identifier (required)
traits: Object with group properties (name, industry, size, plan)
timestamp: ISO 8601 timestamp
Pitfalls:
groupId is required; it identifies the company or organization
- Group traits are merged with existing traits for that group
- A user can belong to multiple groups
- Group traits update the group profile, not the user profile
5. Track Page Views
When to use: User wants to record page view events in Segment
Tool sequence:
SEGMENT_PAGE - Send a page view event [Required]
Key parameters:
userId: User identifier (required if no anonymousId)
anonymousId: Anonymous identifier
name: Page name (e.g., 'Home', 'Pricing', 'Dashboard')
category: Page category (e.g., 'Docs', 'Marketing')
properties: Object with page-specific properties (url, title, referrer)
Pitfalls:
- At least one of
userId or anonymousId is required
name and category are optional but recommended for proper analytics
- Standard properties include
url, title, referrer, path, search
- Page calls are often automated; manual use is for server-side page tracking
6. Alias Users and Manage Sources
When to use: User wants to merge anonymous and identified users, or manage source configuration
Tool sequence:
SEGMENT_ALIAS - Link two user identities together [Optional]
SEGMENT_LIST_SCHEMA_SETTINGS_IN_SOURCE - View source schema settings [Optional]
SEGMENT_UPDATE_SOURCE - Update source configuration [Optional]
Key parameters:
- For ALIAS:
userId: New user identifier (the identified ID)
previousId: Old user identifier (the anonymous ID)
- For source operations:
sourceId: Source identifier
Pitfalls:
- ALIAS is a one-way operation; cannot be undone
previousId is the anonymous/old ID, userId is the new/identified ID
- Not all destinations support alias calls; check destination documentation
- ALIAS should be called once when a user first identifies (e.g., signs up)
- Source updates may affect data collection; review changes carefully
Common Patterns
User Lifecycle
Standard Segment user lifecycle:
1. Anonymous user visits -> PAGE call with anonymousId
2. User interacts -> TRACK call with anonymousId
3. User signs up -> ALIAS (anonymousId -> userId), then IDENTIFY with traits
4. User takes action -> TRACK call with userId
5. User joins org -> GROUP call linking userId to groupId
Batch Optimization
For bulk data ingestion:
1. Collect events in memory (array of message objects)
2. Each message includes type, userId/anonymousId, and type-specific fields
3. Call SEGMENT_BATCH with the collected messages
4. Check response for any individual message errors
Naming Conventions
Segment recommends consistent event naming:
- Events: Use "Object Action" format (e.g., 'Order Completed', 'Article Viewed')
- Properties: Use snake_case (e.g., 'order_total', 'product_name')
- Traits: Use snake_case (e.g., 'first_name', 'plan_type')
Known Pitfalls
Identity Resolution:
- Always include
userId or anonymousId on every call
- Use ALIAS only once per user identity merge
- Identify before tracking to ensure proper user association
Data Quality:
- Event names should be consistent across all sources
- Properties should follow a defined schema for downstream compatibility
- Avoid sending sensitive PII unless destinations are configured for it
Rate Limits:
- Use BATCH for bulk operations to stay within rate limits
- Individual calls are rate-limited per source
- Batch calls are more efficient and less likely to be throttled
Response Parsing:
- Successful responses indicate acceptance, not delivery to destinations
- Response data may be nested under
data key
- Check for error fields in batch responses for individual message failures
Timestamps:
- Must be ISO 8601 format with timezone (e.g., '2024-01-15T10:30:00Z')
- Omitting timestamp uses server receive time
- Historical data imports should include explicit timestamps
Quick Reference
| Task |
Tool Slug |
Key Params |
| Track event |
SEGMENT_TRACK |
userId, event, properties |
| Identify user |
SEGMENT_IDENTIFY |
userId, traits |
| Batch calls |
SEGMENT_BATCH |
batch (array of messages) |
| Group user |
SEGMENT_GROUP |
userId, groupId, traits |
| Page view |
SEGMENT_PAGE |
userId, name, properties |
| Alias identity |
SEGMENT_ALIAS |
userId, previousId |
| Source schema |
SEGMENT_LIST_SCHEMA_SETTINGS_IN_SOURCE |
sourceId |
| Update source |
SEGMENT_UPDATE_SOURCE |
sourceId |
| Warehouses |
SEGMENT_LIST_CONNECTED_WAREHOUSES_FROM_SOURCE |
sourceId |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
1---2name: segment-automation3description: "Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. Always search tools first for current schemas."4requires:5 mcp: [rube]6risk: unknown7source: community8metadata:9 source: https://skillmd.com/skills/mayurrathi/segment-automation10---1112# Segment Automation via Rube MCP1314Automate Segment customer data platform operations through Composio's Segment toolkit via Rube MCP.1516## Prerequisites1718- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)19- Active Segment connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `segment`20- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas2122## Setup2324**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.2526271. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds282. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `segment`293. If connection is not ACTIVE, follow the returned auth link to complete Segment authentication304. Confirm connection status shows ACTIVE before running any workflows3132## Core Workflows3334### 1. Track Events3536**When to use**: User wants to send event data to Segment for downstream destinations3738**Tool sequence**:391. `SEGMENT_TRACK` - Send a single track event [Required]4041**Key parameters**:42- `userId`: User identifier (required if no `anonymousId`)43- `anonymousId`: Anonymous identifier (required if no `userId`)44- `event`: Event name (e.g., 'Order Completed', 'Button Clicked')45- `properties`: Object with event-specific properties46- `timestamp`: ISO 8601 timestamp (optional; defaults to server time)47- `context`: Object with contextual metadata (IP, user agent, etc.)4849**Pitfalls**:50- At least one of `userId` or `anonymousId` is required51- `event` name is required and should follow consistent naming conventions52- Properties are freeform objects; ensure consistent schema across events53- Timestamp must be ISO 8601 format (e.g., '2024-01-15T10:30:00Z')54- Events are processed asynchronously; successful API response means accepted, not delivered5556### 2. Identify Users5758**When to use**: User wants to associate traits with a user profile in Segment5960**Tool sequence**:611. `SEGMENT_IDENTIFY` - Set user traits and identity [Required]6263**Key parameters**:64- `userId`: User identifier (required if no `anonymousId`)65- `anonymousId`: Anonymous identifier66- `traits`: Object with user properties (email, name, plan, etc.)67- `timestamp`: ISO 8601 timestamp68- `context`: Contextual metadata6970**Pitfalls**:71- At least one of `userId` or `anonymousId` is required72- Traits are merged with existing traits, not replaced73- To remove a trait, set it to `null`74- Identify calls should be made before track calls for new users75- Avoid sending PII in traits unless destinations are configured for it7677### 3. Batch Operations7879**When to use**: User wants to send multiple events, identifies, or other calls in a single request8081**Tool sequence**:821. `SEGMENT_BATCH` - Send multiple Segment calls in one request [Required]8384**Key parameters**:85- `batch`: Array of message objects, each with:86 - `type`: Message type ('track', 'identify', 'group', 'page', 'alias')87 - `userId` / `anonymousId`: User identifier88 - Additional fields based on type (event, properties, traits, etc.)8990**Pitfalls**:91- Each message in the batch must have a valid `type` field92- Maximum batch size limit applies; check schema for current limit93- All messages in a batch are processed independently; one failure does not affect others94- Each message must independently satisfy its type's requirements (e.g., track needs event name)95- Batch is the most efficient way to send multiple calls; prefer over individual calls9697### 4. Group Users9899**When to use**: User wants to associate a user with a company, team, or organization100101**Tool sequence**:1021. `SEGMENT_GROUP` - Associate user with a group [Required]103104**Key parameters**:105- `userId`: User identifier (required if no `anonymousId`)106- `anonymousId`: Anonymous identifier107- `groupId`: Group/organization identifier (required)108- `traits`: Object with group properties (name, industry, size, plan)109- `timestamp`: ISO 8601 timestamp110111**Pitfalls**:112- `groupId` is required; it identifies the company or organization113- Group traits are merged with existing traits for that group114- A user can belong to multiple groups115- Group traits update the group profile, not the user profile116117### 5. Track Page Views118119**When to use**: User wants to record page view events in Segment120121**Tool sequence**:1221. `SEGMENT_PAGE` - Send a page view event [Required]123124**Key parameters**:125- `userId`: User identifier (required if no `anonymousId`)126- `anonymousId`: Anonymous identifier127- `name`: Page name (e.g., 'Home', 'Pricing', 'Dashboard')128- `category`: Page category (e.g., 'Docs', 'Marketing')129- `properties`: Object with page-specific properties (url, title, referrer)130131**Pitfalls**:132- At least one of `userId` or `anonymousId` is required133- `name` and `category` are optional but recommended for proper analytics134- Standard properties include `url`, `title`, `referrer`, `path`, `search`135- Page calls are often automated; manual use is for server-side page tracking136137### 6. Alias Users and Manage Sources138139**When to use**: User wants to merge anonymous and identified users, or manage source configuration140141**Tool sequence**:1421. `SEGMENT_ALIAS` - Link two user identities together [Optional]1432. `SEGMENT_LIST_SCHEMA_SETTINGS_IN_SOURCE` - View source schema settings [Optional]1443. `SEGMENT_UPDATE_SOURCE` - Update source configuration [Optional]145146**Key parameters**:147- For ALIAS:148 - `userId`: New user identifier (the identified ID)149 - `previousId`: Old user identifier (the anonymous ID)150- For source operations:151 - `sourceId`: Source identifier152153**Pitfalls**:154- ALIAS is a one-way operation; cannot be undone155- `previousId` is the anonymous/old ID, `userId` is the new/identified ID156- Not all destinations support alias calls; check destination documentation157- ALIAS should be called once when a user first identifies (e.g., signs up)158- Source updates may affect data collection; review changes carefully159160## Common Patterns161162### User Lifecycle163164Standard Segment user lifecycle:165```1661. Anonymous user visits -> PAGE call with anonymousId1672. User interacts -> TRACK call with anonymousId1683. User signs up -> ALIAS (anonymousId -> userId), then IDENTIFY with traits1694. User takes action -> TRACK call with userId1705. User joins org -> GROUP call linking userId to groupId171```172173### Batch Optimization174175For bulk data ingestion:176```1771. Collect events in memory (array of message objects)1782. Each message includes type, userId/anonymousId, and type-specific fields1793. Call SEGMENT_BATCH with the collected messages1804. Check response for any individual message errors181```182183### Naming Conventions184185Segment recommends consistent event naming:186- **Events**: Use "Object Action" format (e.g., 'Order Completed', 'Article Viewed')187- **Properties**: Use snake_case (e.g., 'order_total', 'product_name')188- **Traits**: Use snake_case (e.g., 'first_name', 'plan_type')189190## Known Pitfalls191192**Identity Resolution**:193- Always include `userId` or `anonymousId` on every call194- Use ALIAS only once per user identity merge195- Identify before tracking to ensure proper user association196197**Data Quality**:198- Event names should be consistent across all sources199- Properties should follow a defined schema for downstream compatibility200- Avoid sending sensitive PII unless destinations are configured for it201202**Rate Limits**:203- Use BATCH for bulk operations to stay within rate limits204- Individual calls are rate-limited per source205- Batch calls are more efficient and less likely to be throttled206207**Response Parsing**:208- Successful responses indicate acceptance, not delivery to destinations209- Response data may be nested under `data` key210- Check for error fields in batch responses for individual message failures211212**Timestamps**:213- Must be ISO 8601 format with timezone (e.g., '2024-01-15T10:30:00Z')214- Omitting timestamp uses server receive time215- Historical data imports should include explicit timestamps216217## Quick Reference218219| Task | Tool Slug | Key Params |220|------|-----------|------------|221| Track event | SEGMENT_TRACK | userId, event, properties |222| Identify user | SEGMENT_IDENTIFY | userId, traits |223| Batch calls | SEGMENT_BATCH | batch (array of messages) |224| Group user | SEGMENT_GROUP | userId, groupId, traits |225| Page view | SEGMENT_PAGE | userId, name, properties |226| Alias identity | SEGMENT_ALIAS | userId, previousId |227| Source schema | SEGMENT_LIST_SCHEMA_SETTINGS_IN_SOURCE | sourceId |228| Update source | SEGMENT_UPDATE_SOURCE | sourceId |229| Warehouses | SEGMENT_LIST_CONNECTED_WAREHOUSES_FROM_SOURCE | sourceId |230231## When to Use232This skill is applicable to execute the workflow or actions described in the overview.