Salesforce Service Cloud Automation

What This Skill Does

This skill automates Salesforce Service Cloud operations using the Composio Salesforce Service Cloud toolkit via Rube MCP. It's designed for users who want to streamline their Salesforce workflows and integrate them with other systems. The skill requires an active Salesforce Service Cloud connection and Rube MCP setup.

When to Use

Automate case creationUpdate existing case detailsRetrieve customer informationTrigger workflows based on case statusEscalate critical support issuesManage knowledge base articles

Key Features

Uses Rube MCP for tool executionRequires active Salesforce Service Cloud connectionEmploys RUBE_SEARCH_TOOLS for tool discoveryUses RUBE_MANAGE_CONNECTIONS for connection managementSupports RUBE_MULTI_EXECUTE_TOOL for workflow executionProvides documentation for the Salesforce Service Cloud toolkit

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_CONNECTIONS with toolkit salesforce_service_cloud 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 salesforce_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_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

Toolkit docs: composio.dev/toolkits/salesforce_service_cloud