salesforce-automation
Automate Salesforce tasks via Rube MCP (Composio): leads, contacts, accounts, opportunities, SOQL queries. Always search tools first for current schemas.
What this skill does
# Salesforce Automation via Rube MCP Automate Salesforce CRM operations through Composio's Salesforce toolkit via Rube MCP. ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active Salesforce connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `salesforce` - 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 `salesforce` 3. If connection is not ACTIVE, follow the returned auth link to complete Salesforce OAuth 4. Confirm connection status shows ACTIVE before running any workflows ## Core Workflows ### 1. Manage Leads **When to use**: User wants to create, search, update, or list leads **Tool sequence**: 1. `SALESFORCE_SEARCH_LEADS` - Search leads by criteria [Optional] 2. `SALESFORCE_LIST_LEADS` - List all leads [Optional] 3. `SALESFORCE_CREATE_LEAD` - Create a new lead [Optional] 4. `SALESFORCE_UPDATE_LEAD` - Update lead fields [Optional] 5. `SALESFORCE_ADD_LEAD_TO_CAMPAIGN` - Add lead to campaign [Optional] 6. `SALESFORCE_APPLY_LEAD_ASSIGNMENT_RULES` - Apply assignment rules [Optional] **Key parameters**: - `LastName`: Required for lead creation - `Company`: Required for lead creation - `Email`, `Phone`, `Title`: Common lead fields - `lead_id`: Lead ID for updates - `campaign_id`: Campaign ID for campaign operations **Pitfalls**: - LastName and Company are required fields for lead creation - Lead IDs are 15 or 18 character Salesforce IDs ### 2. Manage Contacts and Accounts **When to use**: User wants to manage contacts and their associated accounts **Tool sequence**: 1. `SALESFORCE_SEARCH_CONTACTS` - Search contacts [Optional] 2. `SALESFORCE_LIST_CONTACTS` - List contacts [Optional] 3. `SALESFORCE_CREATE_CONTACT` - Create a new contact [Optional] 4. `SALESFORCE_SEARCH_ACCOUNTS` - Search accounts [Optional] 5. `SALESFORCE_CREATE_ACCOUNT` - Create a new account [Optional] 6. `SALESFORCE_ASSOCIATE_CONTACT_TO_ACCOUNT` - Link contact to account [Optional] **Key parameters**: - `LastName`: Required for contact creation - `Name`: Account name for creation - `AccountId`: Account ID to associate with contact - `contact_id`, `account_id`: IDs for association **Pitfalls**: - Contact requires at least LastName - Account association requires both valid contact and account IDs ### 3. Manage Opportunities **When to use**: User wants to track and manage sales opportunities **Tool sequence**: 1. `SALESFORCE_SEARCH_OPPORTUNITIES` - Search opportunities [Optional] 2. `SALESFORCE_LIST_OPPORTUNITIES` - List all opportunities [Optional] 3. `SALESFORCE_GET_OPPORTUNITY` - Get opportunity details [Optional] 4. `SALESFORCE_CREATE_OPPORTUNITY` - Create new opportunity [Optional] 5. `SALESFORCE_RETRIEVE_OPPORTUNITIES_DATA` - Retrieve opportunity data [Optional] **Key parameters**: - `Name`: Opportunity name (required) - `StageName`: Sales stage (required) - `CloseDate`: Expected close date (required) - `Amount`: Deal value - `AccountId`: Associated account **Pitfalls**: - Name, StageName, and CloseDate are required for creation - Stage names must match exactly what is configured in Salesforce ### 4. Run SOQL Queries **When to use**: User wants to query Salesforce data with custom SOQL **Tool sequence**: 1. `SALESFORCE_RUN_SOQL_QUERY` / `SALESFORCE_QUERY` - Execute SOQL [Required] **Key parameters**: - `query`: SOQL query string **Pitfalls**: - SOQL syntax differs from SQL; uses Salesforce object and field API names - Field API names may differ from display labels (e.g., `Account.Name` not `Account Name`) - Results are paginated for large datasets ### 5. Manage Tasks **When to use**: User wants to create, search, update, or complete tasks **Tool sequence**: 1. `SALESFORCE_SEARCH_TASKS` - Search tasks [Optional] 2. `SALESFORCE_UPDATE_TASK` - Update task fields [Optional] 3. `SALESFORCE_COMPLETE_TASK` - Mark task as complete [Optional] **Key parameters**: - `task_id`: Task ID for updates - `Status`: Task status value - `Subject`: Task subject **Pitfalls**: - Task status values must match picklist options in Salesforce ## Common Patterns ### SOQL Syntax **Basic query**: ``` SELECT Id, Name, Email FROM Contact WHERE LastName = 'Smith' ``` **With relationships**: ``` SELECT Id, Name, Account.Name FROM Contact WHERE Account.Industry = 'Technology' ``` **Date filtering**: ``` SELECT Id, Name FROM Lead WHERE CreatedDate = TODAY SELECT Id, Name FROM Opportunity WHERE CloseDate = NEXT_MONTH ``` ### Pagination - SOQL queries with large results return pagination tokens - Use `SALESFORCE_QUERY` with nextRecordsUrl for pagination - Check `done` field in response; if false, continue paging ## Known Pitfalls **Field API Names**: - Always use API names, not display labels - Custom fields end with `__c` suffix - Use SALESFORCE_GET_ALL_CUSTOM_OBJECTS to discover custom objects **ID Formats**: - Salesforce IDs are 15 (case-sensitive) or 18 (case-insensitive) characters - Both formats are accepted in most operations ## Quick Reference | Task | Tool Slug | Key Params | |------|-----------|------------| | Create lead | SALESFORCE_CREATE_LEAD | LastName, Company | | Search leads | SALESFORCE_SEARCH_LEADS | query | | List leads | SALESFORCE_LIST_LEADS | (filters) | | Update lead | SALESFORCE_UPDATE_LEAD | lead_id, fields | | Create contact | SALESFORCE_CREATE_CONTACT | LastName | | Search contacts | SALESFORCE_SEARCH_CONTACTS | query | | Create account | SALESFORCE_CREATE_ACCOUNT | Name | | Search accounts | SALESFORCE_SEARCH_ACCOUNTS | query | | Link contact | SALESFORCE_ASSOCIATE_CONTACT_TO_ACCOUNT | contact_id, account_id | | Create opportunity | SALESFORCE_CREATE_OPPORTUNITY | Name, StageName, CloseDate | | Get opportunity | SALESFORCE_GET_OPPORTUNITY | opportunity_id | | Search opportunities | SALESFORCE_SEARCH_OPPORTUNITIES | query | | Run SOQL | SALESFORCE_RUN_SOQL_QUERY | query | | Query | SALESFORCE_QUERY | query | | Search tasks | SALESFORCE_SEARCH_TASKS | query | | Update task | SALESFORCE_UPDATE_TASK | task_id, fields | | Complete task | SALESFORCE_COMPLETE_TASK | task_id | | Get user info | SALESFORCE_GET_USER_INFO | (none) | | Custom objects | SALESFORCE_GET_ALL_CUSTOM_OBJECTS | (none) | | Create record | SALESFORCE_CREATE_A_RECORD | object_type, fields | | Transfer ownership | SALESFORCE_MASS_TRANSFER_OWNERSHIP | records, new_owner | ## When to Use This skill is applicable to execute the workflow or actions described in the overview. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.