Do I need API keys to use adyntel-automation?

No—the setup uses the Rube MCP endpoint (no API keys required) and relies on RUBE_SEARCH_TOOLS for current schemas.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS before executing; do not hardcode tool slugs or arguments.

How should I manage sessions and memory?

Reuse session IDs within a workflow and include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if it is empty.

adyntel-automation

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

Files (1)

SKILL.md

2.9 KB

Adyntel Automation via Rube MCP

Automate Adyntel operations through Composio's Adyntel toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/adyntel

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["adyntel"]
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 Adyntel-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `adyntel`
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/adyntel-automation/SKILL.mdView on GitHub

Overview

Automate Adyntel operations through Composio's Adyntel toolkit via Rube MCP. Always search for current tool schemas before executing workflows to avoid hardcoding slugs or arguments. This approach ties together discovery, connection management, and tool execution for repeatable automation.

How This Skill Works

Begin by discovering available Adyntel tools with RUBE_SEARCH_TOOLS to obtain up-to-date slugs and input schemas. Next, verify that an Adyntel connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, then execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id. Always perform the discovery step before execution to align with current schemas.

When to Use It

When you need to automate Adyntel tasks and ensure you’re using current tool schemas.
When setting up a new Adyntel integration and validating an ACTIVE connection before operations.
When you want to discover available Adyntel tools before selecting a workflow.
When you require proper memory handling and session continuity for tool executions.
When performing bulk or remote operations across multiple Adyntel tools using Composio tooling.

Quick Start

Step 1: Set up the Rube MCP endpoint (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit ["adyntel"] and confirm ACTIVE status.
Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a selected tool via RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.

Best Practices

Always search first for current tool schemas using RUBE_SEARCH_TOOLS.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
Use exact field names and types from the discovered tool schemas; avoid hardcoding slugs.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and paginate responses until complete.

Example Use Cases

Discover Adyntel tools for a given use_case, then run a specific tool slug with required arguments.
Set up MCP, verify RUBE_SEARCH_TOOLS, connect with the adyntel toolkit, and execute a task.
Pass a session_id from discovery and reuse it across subsequent steps.
Handle pagination tokens by continuing to fetch until complete.
Use RUBE_REMOTE_WORKBENCH with run_composio_tool() for bulk Adyntel operations.

Frequently Asked Questions

Add this skill to your agents