Salesmate Automation
This skill automates Salesmate operations via the Composio Salesmate toolkit and Rube MCP. It's intended for users looking to integrate and automate Salesmate...
Install
npx promptshop add salesmate-automationDetails
What This Skill Does
This skill automates Salesmate operations via the Composio Salesmate toolkit and Rube MCP. It's intended for users looking to integrate and automate Salesmate workflows with other systems. The skill necessitates an active Salesmate connection and a properly configured Rube MCP.
When to Use
Create new contacts in SalesmateUpdate existing deal stagesSchedule follow-up activitiesSend automated email sequencesTrack sales performance metricsManage Salesmate CRM data
Key Features
Leverages Rube MCP for automationRequires active Salesmate connectionUtilizes RUBE_SEARCH_TOOLS for tool discoveryEmploys RUBE_MANAGE_CONNECTIONS for connection managementSupports RUBE_MULTI_EXECUTE_TOOL for executing workflowsProvides documentation for the Salesmate toolkit
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 |
| 's Salesmate toolkit via Rube MCP. |
Toolkit docs: composio.dev/toolkits/salesmate