home / skills / composiohq / awesome-claude-skills / salesmate-automation

salesmate-automation skill

safe

This skill automates Salesmate operations via Composio's Rube MCP, discovering tool schemas first to execute approved workflows efficiently.

npx playbooks add skill composiohq/awesome-claude-skills --skill salesmate-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: salesmate-automation
description: "Automate Salesmate tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Salesmate Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/salesmate](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `salesmate`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Salesmate CRM tasks using Composio's Salesmate toolkit via the Rube MCP. It provides a clear discovery-first workflow to find current tool schemas, manage connections, and execute operations reliably. The design enforces schema compliance and session management to avoid runtime errors. Use it to orchestrate single or bulk Salesmate actions from an agent environment.

How this skill works

The agent first calls RUBE_SEARCH_TOOLS to discover available Salesmate tool slugs, input schemas, and recommended execution plans. Next it verifies or completes an active Salesmate connection via RUBE_MANAGE_CONNECTIONS. Operations execute through RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk work), always passing schema-compliant arguments, a memory object, and a session ID. The skill emphasizes reusing session IDs within a workflow and handling pagination and schemaRef lookups when needed.

When to use it

Automating CRM actions like creating or updating contacts, deals, or notes in Salesmate.
Running bulk imports, mass updates, or multi-step workflows across Salesmate entities.
Embedding Salesmate operations into an AI-driven workflow that must adapt to changing tool schemas.
Orchestrating cross-tool flows where Salesmate is one component and schema discovery is required.
Building guarded automation where connection and schema validation are required before execution.

Best practices

Always call RUBE_SEARCH_TOOLS first—do not hardcode tool slugs or argument shapes.
Confirm RUBE_MANAGE_CONNECTIONS shows ACTIVE for the salesmate toolkit before any execute call.
Include a memory object (even {}) in every RUBE_MULTI_EXECUTE_TOOL call and reuse session IDs.
Respect exact field names and types returned by search; use RUBE_GET_TOOL_SCHEMAS when schemaRef is provided.
Handle pagination tokens in responses and iterate until all pages are fetched.
Generate a new session ID for distinct workflows; reuse session IDs within the same workflow.

Example use cases

Create a new contact and link it to an existing deal by discovering contact/deal tool schemas and executing each step in sequence.
Run a bulk update to add a tag to thousands of leads via RUBE_REMOTE_WORKBENCH with run_composio_tool().
Build an agent that checks connection status, fetches active pipelines, then creates deals based on AI-generated leads.
Fetch paginated lists of contacts, transform them, and push updates while honoring schema and memory requirements.
Automate onboarding tasks: create company, contacts, initial deal, and schedule follow-up reminders using discovered tool slugs.

FAQ

What is the first call an agent should make?

Always call RUBE_SEARCH_TOOLS to retrieve current tool slugs and input schemas before any other action.

Do I need API keys to use Rube MCP?

No API keys are required for Rube MCP; add https://rube.app/mcp as an MCP server in your client configuration.