home / skills / composiohq / awesome-claude-skills / salesforce-marketing-cloud-automation

salesforce-marketing-cloud-automation skill

/salesforce-marketing-cloud-automation

This skill automates Salesforce Marketing Cloud tasks through Rube MCP, enabling reliable tool discovery, connection management, and execution with schema

npx playbooks add skill composiohq/awesome-claude-skills --skill salesforce-marketing-cloud-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.1 KB
---
name: salesforce-marketing-cloud-automation
description: "Automate Salesforce Marketing Cloud tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Salesforce 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](https://composio.dev/toolkits/salesforce_marketing_cloud)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Salesforce Marketing Cloud connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `salesforce_marketing_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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `salesforce_marketing_cloud`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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_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

| 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](https://composio.dev)*

Overview

This skill automates Salesforce Marketing Cloud tasks through Composio’s Salesforce Marketing Cloud toolkit via Rube MCP. It provides a repeatable workflow pattern for discovering tools, validating connections, and executing toolkit actions safely. The skill emphasizes always discovering current tool schemas before running operations to avoid breakage.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to discover available tool slugs, input schemas, and recommended execution plans. It then verifies an active SFMC connection with RUBE_MANAGE_CONNECTIONS before running RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs) using schema-compliant arguments. Session IDs and a memory object are used to maintain workflow context and support pagination and multi-step orchestration.

When to use it

  • Automate email sends, data extension management, or contact updates in Salesforce Marketing Cloud.
  • Run scheduled or bulk operations that require authenticated SFMC access through Composio/Rube MCP.
  • Create repeatable deployment or data-sync workflows that must adapt to changing tool schemas.
  • Prototype integrations that call Composio toolkits without embedding API keys in client code.
  • Execute multi-step campaigns that require session-based orchestration and pagination handling.

Best practices

  • Always call RUBE_SEARCH_TOOLS first to retrieve current tool slugs and exact input schemas.
  • Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for toolkit salesforce_marketing_cloud before executing tools.
  • Include a memory object (can be empty {}) in RUBE_MULTI_EXECUTE_TOOL calls to avoid execution errors.
  • Reuse a session_id throughout a single workflow; generate a new session for separate workflows.
  • Respect schema types and field names exactly; validate inputs against returned schemas and handle pagination tokens.

Example use cases

  • Schedule a bulk email send: discover send tool, confirm connection, execute send with schema-compliant args and session reuse.
  • Sync subscribers from an external system: fetch tool schemas, run data extension upsert operations with pagination handling.
  • Bulk update contact attributes across data extensions using RUBE_REMOTE_WORKBENCH to run run_composio_tool() jobs.
  • Validate toolkit availability and build a safe automation playground by discovering tools, checking connections, and running dry-run executions.

FAQ

Do I need API keys to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server in your client configuration; no API keys are required for Rube MCP endpoints.

What if a tool schema changes during a workflow?

Always re-run RUBE_SEARCH_TOOLS at the start of a workflow or before calling a new tool. If schema changes mid-workflow, re-discover tools and adapt arguments accordingly.