Userlist Automation

What This Skill Does

• This skill automates operations within the Userlist platform using Composio's Userlist toolkit via Rube MCP.
• It enables users to manage user data and communication workflows through automated processes.
• It is designed for Userlist users who want to streamline their user management tasks.

When to Use

Automate user data managementManage communication workflowsSegment users based on behaviorSend targeted messagesTrack user engagementIntegrate with other marketing tools

Key Features

Uses Rube MCP for Userlist automationRequires an active Userlist connectionDiscovers available tools via RUBE_SEARCH_TOOLSChecks connection status before executionExecutes tools with schema-compliant argumentsProvides toolkit documentation for reference

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedUserlist Automation via Rube MCP

Automate Userlist operations through Composio's Userlist toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/userlist

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Userlist connection via RUBE_MANAGE_CONNECTIONS with toolkit userlist Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

• Get Rube MCP: Add https://rube.
• 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 userlist If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS queries: [{use_case: "Userlist operations", known_fields: ""}] session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Userlist task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["userlist"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"

Known Pitfalls

• Always search first: Tool schemas change.
• Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS. Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Schema compliance: Use exact field names and types from the search results Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
• Session reuse: Reuse session IDs within a workflow.
• Generate new ones for new workflows. Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference