playbooks

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

forcemanager-automation skill

/forcemanager-automation

This skill automates Forcemanager tasks via Rube MCP, ensuring tools are discovered first and connections are active for reliable workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill forcemanager-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: forcemanager-automation
description: "Automate Forcemanager tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Forcemanager Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/forcemanager](https://composio.dev/toolkits/forcemanager)

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["forcemanager"]
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 Forcemanager-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `forcemanager` |
| 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 Forcemanager tasks using Composio’s Forcemanager toolkit via the Rube MCP interface. It standardizes discovery, connection management, and tool execution so you can run CRM operations programmatically and reliably. The skill enforces runtime checks to avoid schema drift and connection failures.

How this skill works

The skill first queries RUBE_SEARCH_TOOLS to fetch current tool slugs, input schemas, and recommended execution plans. It then verifies or establishes an active Forcemanager connection via RUBE_MANAGE_CONNECTIONS. Once tools and connection status are confirmed, it runs operations through RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs), always providing schema-compliant arguments and a memory object.

When to use it

  • Automating repetitive Forcemanager CRUD operations (contacts, accounts, activities).
  • Running bulk updates or imports where tool schemas can change over time.
  • Embedding Forcemanager actions inside multi-step agent workflows.
  • Orchestrating scheduled maintenance or data-sync jobs against Forcemanager.
  • When you need robust prechecks (tool discovery + connection validation) before executing actions.

Best practices

  • Always call RUBE_SEARCH_TOOLS at the start of every workflow to get current schemas and tool slugs.
  • Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the forcemanager toolkit before executing tools.
  • Pass exact field names and types returned by the search response; do not hardcode argument shapes.
  • Include a memory object (can be empty {}) in every RUBE_MULTI_EXECUTE_TOOL call.
  • Reuse session IDs within a single workflow; generate new sessions for new workflows and handle pagination tokens.

Example use cases

  • Create or update contact records by discovering the correct create/update tool and supplying schema-compliant fields.
  • Bulk import leads using RUBE_REMOTE_WORKBENCH with run_composio_tool() to process large batches.
  • Automate activity logging after sales calls by chaining tool discovery, connection check, and multi-execute calls.
  • Build an agent that syncs account data nightly, handling pagination and schema changes automatically.
  • Trigger conditional workflows that first validate connection status and then run a sequence of Forcemanager tools.

FAQ

Do I need API keys to use Rube MCP?

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

What happens if tool schemas change?

You must re-run RUBE_SEARCH_TOOLS; the skill relies on fresh search results and will fail if you use stale or hardcoded schemas.