toneden-automation

Automate Toneden platform operations through Rube MCP toolkits and structured execution workflows.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill toneden-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: toneden-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/toneden-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill toneden-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual overhead of managing Toneden campaigns and assets by providing a standardized, automated interface for interacting with the Toneden API via the Rube MCP gateway.

Core Features & Use Cases

  • Automated Tool Discovery: Dynamically fetch current tool schemas and execution plans for Toneden operations.
  • Connection Management: Verify and maintain active authentication states for Toneden integrations.
  • Multi-Step Execution: Execute complex, multi-tool workflows with memory persistence and session management.
  • Use Case: Automate the deployment of marketing assets or campaign updates by chaining discovery, connection verification, and multi-tool execution commands.

Quick Start

Use the toneden-automation skill to discover available tools and execute a campaign update task.

Frequently Asked Questions about toneden-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute Toneden tasks using this skill?

Start by calling RUBE_SEARCH_TOOLS to identify available Toneden tools, verify your connection status with RUBE_MANAGE_CONNECTIONS, and then use RUBE_MULTI_EXECUTE_TOOL to perform your specific operations.

What should I do if my Toneden connection is inactive?

Call RUBE_MANAGE_CONNECTIONS with the toneden toolkit. If the status is not ACTIVE, the system will provide an authentication link to re-establish your connection.

Why must I call RUBE_SEARCH_TOOLS before executing tasks?

Tool schemas and available endpoints change frequently. Searching first ensures you use the correct tool slugs and argument structures, preventing execution errors.

Can I reuse session IDs for different workflows?

No, you should generate new session IDs for distinct workflows to ensure proper state management and avoid cross-contamination of task memory.

What is the purpose of the memory parameter in tool execution?

The memory parameter allows the Rube MCP to maintain context across multiple tool calls within a single session, which is required for complex, multi-step automation tasks.