Do I need API keys to use this skill?

No API keys are required. You add the Rube MCP endpoint and connect to the doppler_marketing_automation toolkit; RUBE_SEARCH_TOOLS handles schema discovery.

What if tool schemas change?

Always search tools first to fetch current schemas, avoid hardcoding slugs or arguments, ensure memory is provided in executions, and handle pagination if results are incomplete.

doppler-marketing-automation-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/doppler-marketing-automation-automation --openclaw

Files (1)

SKILL.md

3.2 KB

Doppler Marketing Automation Automation via Rube MCP

Automate Doppler Marketing Automation operations through Composio's Doppler Marketing Automation toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/doppler_marketing_automation

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Doppler Marketing Automation connection via RUBE_MANAGE_CONNECTIONS with toolkit doppler_marketing_automation
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 doppler_marketing_automation
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: "Doppler Marketing Automation 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 Doppler Marketing Automation task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["doppler_marketing_automation"]
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 Doppler Marketing Automation-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `doppler_marketing_automation`
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/doppler-marketing-automation-automation/SKILL.md

View on GitHub

Overview

Automate Doppler Marketing Automation operations using Composio's toolkit through Rube MCP. The approach emphasizes discovering current tool schemas first and validating an ACTIVE Doppler connection before running any workflows.

How This Skill Works

The workflow uses RUBE_SEARCH_TOOLS to discover available Doppler automation tools and their input schemas. It then uses RUBE_MANAGE_CONNECTIONS to ensure the doppler_marketing_automation toolkit is ACTIVE, and executes tools with RUBE_MULTI_EXECUTE_TOOL, supplying a memory payload and a session_id.

When to Use It

When you need to automate a Doppler Marketing Automation task but tool schemas are unknown or frequently updated
When you must verify the Doppler connection status is ACTIVE before execution
When you need to discover available tools and their input schemas before scripting
When performing chained or bulk operations that require session continuity
When you need to fetch full tool schemas via RUBE_GET_TOOL_SCHEMAS to understand inputs

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and ensure RUBE_SEARCH_TOOLS responds
Step 2: Run RUBE_MANAGE_CONNECTIONS with toolkits: ["doppler_marketing_automation"] and verify ACTIVE
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory: {} and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current schemas
Check RUBE_MANAGE_CONNECTIONS status is ACTIVE before execution
Use exact field names and types from search results; avoid hardcoding
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and refresh for new workflows when needed

Example Use Cases

Discover tools for a Doppler automation task and select a tool slug based on current schemas
Establish a connection to the doppler_marketing_automation toolkit and confirm ACTIVE status
Execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and required arguments
Perform bulk operations or tool chaining via RUBE_REMOTE_WORKBENCH and run_composio_tool()
Fetch full tool schemas using RUBE_GET_TOOL_SCHEMAS for reference or audit

Frequently Asked Questions

Add this skill to your agents