salesforce-marketing-cloud-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/salesforce-marketing-cloud-automation --openclawSalesforce Marketing Cloud Automation via Rube MCP
Automate Salesforce Marketing Cloud operations through Composio's Salesforce Marketing Cloud toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/salesforce_marketing_cloud
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Salesforce Marketing Cloud connection via
RUBE_MANAGE_CONNECTIONSwith toolkitsalesforce_marketing_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_marketing_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 Marketing 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 Marketing Cloud task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["salesforce_marketing_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 Marketing Cloud-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit salesforce_marketing_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-marketing-cloud-automation/SKILL.mdView on GitHub Overview
Automate Salesforce Marketing Cloud operations using Composio's toolkit via Rube MCP. The workflow emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before executing and validating connections with RUBE_MANAGE_CONNECTIONS to ensure ACTIVE status.
How This Skill Works
You first discover available SFMC tools using RUBE_SEARCH_TOOLS, then verify your Salesforce Marketing Cloud connection with RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tool(s) with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments. Always include a memory object and reuse session IDs for cohesive workflows, and re-run RUBE_SEARCH_TOOLS if tool schemas change.
When to Use It
- Before automating SFMC tasks, discover available tools with RUBE_SEARCH_TOOLS.
- To initialize or verify an active Salesforce Marketing Cloud connection via RUBE_MANAGE_CONNECTIONS.
- When you need to execute a discovered SFMC tool with exact arguments from the schema.
- When running multiple SFMC actions in one session to improve efficiency (reuse session_id).
- When schemas change or you need complete tool coverage by handling pagination and updated schemas.
Quick Start
- Step 1: RUBE_SEARCH_TOOLS queries: [{use_case: "Salesforce Marketing Cloud operations", known_fields: ""}] session: {generate_id: true}
- Step 2: RUBE_MANAGE_CONNECTION toolkits: ["salesforce_marketing_cloud"] session_id: "your_session_id"
- Step 3: RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/* schema-compliant args from search results */} }] memory: {} session_id: "your_session_id"
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from search results; avoid hardcoding slugs.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs where possible and handle pagination tokens when listing tools.
Example Use Cases
- Discover tools for SFMC operations and run a data extension update tool with proper args.
- Establish an ACTIVE SFMC connection and schedule a campaign using a discovered tool.
- Execute a sequence of SFMC actions in one session via RUBE_MULTI_EXECUTE_TOOL.
- Paginate through tool schemas with RUBE_GET_TOOL_SCHEMAS to stay up-to-date.
- Use RUBE_REMOTE_WORKBENCH with run_composio_tool() for bulk SFMC tasks.