What is Rube MCP used for in this skill?

Rube MCP is used to discover, connect, and execute Salesmate tools in a compliant workflow.

Do I always need to search tools first?

Yes. Tool schemas change, so you must call RUBE_SEARCH_TOOLS before executing any tool.

What if the connection shows not ACTIVE?

Follow the returned auth link to complete setup, then re-check until ACTIVE before running any workflows.

salesmate-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/salesmate-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Salesmate Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/salesmate

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Salesmate connection via RUBE_MANAGE_CONNECTIONS with toolkit salesmate
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 salesmate
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: "Salesmate 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 Salesmate task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["salesmate"]
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

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Salesmate-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `salesmate`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/salesmate-automation/SKILL.mdView on GitHub

Overview

Automate Salesmate operations through Composio's Salesmate toolkit via Rube MCP. This skill emphasizes discovering current tool schemas first, establishing an ACTIVE Salesmate connection, and executing tools with schema-compliant inputs.

How This Skill Works

Fetch current tool schemas using RUBE_SEARCH_TOOLS, then establish or verify a Salesmate connection with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments, always including memory and a valid session.

When to Use It

Create or update a Salesmate contact from an external data source by using a discovered tool slug and the required contact fields.
Advance a deal by updating its stage or status automatically based on trigger events in another system.
Bulk-create tasks for a list of follow-ups or activities linked to Salesmate records.
Sync notes or activities from an external system into Salesmate to keep records aligned.
Validate and test tool schemas with RUBE_GET_TOOL_SCHEMAS before running a major workflow, ensuring compatibility.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration (no API keys required).
Step 2: Verify RUBE_SEARCH_TOOLS responds to confirm tool schemas are current.
Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["salesmate"], then ensure status is ACTIVE before running workflows.

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs, input schemas, and execution plans.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
Use exact field names and types from search results; avoid hardcoding slugs or args.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
Reuse session IDs within a workflow and fetch new tokens only for new workflows; watch for pagination tokens.

Example Use Cases

Use a discovered create_contact tool slug to add a new Salesmate contact with fields like first_name, last_name, and email sourced from an external CRM export.
Run a tool to update a deal's stage to 'Negotiation' by passing deal_id and new_stage as arguments.
Bulk-create follow-up tasks for a list of customers by iterating over their IDs and scheduling tasks with due dates.
Sync external meeting notes as activities in Salesmate by calling a notes/activities tool with relevant identifiers and content.
Fetch the full tool schemas with RUBE_GET_TOOL_SCHEMAS to audit and test a workflow before deployment.

Frequently Asked Questions

Add this skill to your agents