Skill

Automate Salesforce CRM Operations

Automates Salesforce CRM via Rube MCP - leads, contacts, accounts, opportunities, tasks, and custom SOQL queries.

Works with salesforcerube

91
Spark score
out of 100
Updated 20 days ago
Version 14.1.0
Models
universal

Add to Favorites

Why it matters

Streamline your Salesforce CRM operations by automating lead management, contact and account handling, opportunity tracking, and custom data queries using Composio's Salesforce toolkit via Rube MCP.

Outcomes

What it gets done

01

Manage leads (create, search, update, list, add to campaign)

02

Manage contacts and accounts (create, search, link)

03

Manage opportunities (create, search, list, get details)

04

Execute custom SOQL queries for data retrieval

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-salesforce-automation | bash

Overview

Salesforce Automation via Rube MCP

Automates Salesforce CRM via Rube MCP and Composio's Salesforce toolkit: leads, contacts, accounts, opportunities, tasks, and custom SOQL queries, with field-naming and pagination guidance. Use when creating, searching, updating, or listing Salesforce leads, contacts, accounts, opportunities, or tasks, or running SOQL queries, through Rube MCP.

What it does

Salesforce Automation via Rube MCP automates Salesforce CRM operations through Composio's Salesforce toolkit, accessed via Rube MCP at rube.app/mcp with no API keys needed. Setup requires confirming RUBE_SEARCH_TOOLS responds, calling RUBE_MANAGE_CONNECTIONS with toolkit salesforce, completing Salesforce OAuth via the returned auth link if not already ACTIVE, and always calling RUBE_SEARCH_TOOLS first for current tool schemas. Five core workflows are documented with tool sequences and required fields: managing leads via SALESFORCE_SEARCH/LIST/CREATE/UPDATE_LEAD plus campaign assignment and lead-assignment-rule tools (LastName and Company required for creation); managing contacts and accounts via SALESFORCE_CREATE_CONTACT (LastName required), SALESFORCE_CREATE_ACCOUNT, and SALESFORCE_ASSOCIATE_CONTACT_TO_ACCOUNT for linking them; managing opportunities via SALESFORCE_CREATE_OPPORTUNITY (Name, StageName, and CloseDate required, with StageName needing to match Salesforce's configured stage names exactly); running custom SOQL queries via SALESFORCE_RUN_SOQL_QUERY or SALESFORCE_QUERY, where field API names differ from display labels (Account.Name, not "Account Name") and results paginate for large datasets; and managing tasks via SALESFORCE_SEARCH/UPDATE/COMPLETE_TASK, where status values must match Salesforce's picklist options exactly.

When to use - and when NOT to

Use this skill to create, search, update, or list Salesforce leads, contacts, accounts, opportunities, or tasks, or to run custom SOQL queries, through Rube MCP.

Inputs and outputs

Given a Salesforce automation task, the skill outputs the correct tool sequence and required parameters, plus SOQL syntax patterns for relationship queries:

SELECT Id, Name, Account.Name FROM Contact WHERE Account.Industry = 'Technology'

and date filtering (CreatedDate = TODAY, CloseDate = NEXT_MONTH). It documents cursor-based pagination via nextRecordsUrl, continuing while the response's done field is false, and known pitfalls: field API names must be used rather than display labels, custom fields end with a __c suffix (discoverable via SALESFORCE_GET_ALL_CUSTOM_OBJECTS), and Salesforce IDs come in 15-character case-sensitive or 18-character case-insensitive formats, both generally accepted.

Integrations

Built entirely on Composio's Salesforce toolkit accessed through Rube MCP. A Quick Reference table maps roughly 20 tasks to their tool slugs and key parameters, spanning leads, contacts, accounts, opportunities, tasks, SOQL queries, custom object discovery, generic record creation (SALESFORCE_CREATE_A_RECORD), user info lookup (SALESFORCE_GET_USER_INFO), and mass ownership transfer (SALESFORCE_MASS_TRANSFER_OWNERSHIP), which reassigns a batch of records to a new owner in one call.

Who it's for

Sales operations teams and engineers automating Salesforce CRM workflows through Rube MCP who need the correct tool sequences, required fields, and SOQL/pagination/ID-format pitfalls up front, rather than discovering Salesforce's field-naming and picklist quirks through trial and error on a live production org.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.