salesforce-service-cloud-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/salesforce-service-cloud-automation --openclawSalesforce Service Cloud Automation via Rube MCP
Automate Salesforce Service Cloud operations through Composio's Salesforce Service Cloud toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/salesforce_service_cloud
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Salesforce Service Cloud connection via
RUBE_MANAGE_CONNECTIONSwith toolkitsalesforce_service_cloud - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitsalesforce_service_cloud - 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: "Salesforce Service Cloud 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 Salesforce Service Cloud task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["salesforce_service_cloud"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Salesforce Service Cloud-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit salesforce_service_cloud |
| 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/salesforce-service-cloud-automation/SKILL.mdView on GitHub Overview
Automate Salesforce Service Cloud operations using Composio's Salesforce Service Cloud toolkit via Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS, validating connections with RUBE_MANAGE_CONNECTIONS, and executing actions through RUBE_MULTI_EXECUTE_TOOL. This keeps workflows aligned with up-to-date tool definitions while reducing manual steps.
How This Skill Works
First, query RUBE_SEARCH_TOOLS to fetch available Salesforce Service Cloud tools and their input schemas. Then ensure an ACTIVE connection using RUBE_MANAGE_CONNECTIONS with the salesforce_service_cloud toolkit. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying the required arguments and a memory payload, reusing the same session_id when possible.
When to Use It
- You need to automate routine Salesforce Service Cloud tasks (e.g., case creation, update, or routing).
- Onboarding a new task where a discoverable tool exists and its schema can be fetched with RUBE_SEARCH_TOOLS.
- You must validate current tool schemas before running workflows to avoid hardcoding slugs or fields.
- You want to reuse a session ID across multiple steps in a single workflow for continuity.
- You plan to perform bulk or batch operations using the toolkit (e.g., multi-tool execution or bulk updates).
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration (no API key needed).
- Step 2: Run RUBE_SEARCH_TOOLS with use_case: "Salesforce Service Cloud operations" to fetch current tool schemas.
- Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["salesforce_service_cloud"] and session_id, ensure ACTIVE, then execute tools with RUBE_MULTI_EXECUTE_TOOL using memory and the discovered tool_slug.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current tool schemas before any execution.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status for the salesforce_service_cloud toolkit before running tools.
- Use exact field names and types as returned by the search results; do not hardcode slugs or arguments.
- Include a memory payload in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
- Reuse session IDs within a workflow and avoid generating new ones unless starting a new workflow.
Example Use Cases
- Discover or route a new Service Cloud case by finding the appropriate tool via RUBE_SEARCH_TOOLS and executing it with the case_id and customer details.
- Update the status of an existing service case using a discovered tool, feeding the case_id and new status through the tool arguments.
- Automatically assign cases to agents by discovering the routing tool and executing it with case_id and assignee fields.
- Bulk close a set of resolved cases by executing a batch tool with a list of case_ids and a resolution summary.
- Summarize interactions for a case by running a summarize_interactions tool and returning a concise case recap.
