Do I need API keys for Dadata Ru when using this skill?

No API keys are required; authentication is managed through the Rube MCP connection to the dadata_ru toolkit.

How do I verify tools and schemas are up to date?

Always run RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas before executing any workflow.

What if tool schemas change during a workflow?

Rerun RUBE_SEARCH_TOOLS to refresh slugs and schemas, then adjust execution parameters to match the latest schema.

dadata-ru-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Dadata Ru Automation via Rube MCP

Automate Dadata Ru operations through Composio's Dadata Ru toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/dadata_ru

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Dadata Ru operations via Composio's Dadata Ru toolkit using Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running workflows and requires an ACTIVE Dadata Ru connection. This keeps automation resilient to schema changes and setup variances.

How This Skill Works

You first call RUBE_SEARCH_TOOLS to fetch current tool schemas. Then verify the Dadata Ru connection is ACTIVE using RUBE_MANAGE_CONNECTIONS for the dadata_ru toolkit. Finally, execute discovered tools with RUBE_MULTI_EXECUTE_TOOL, including memory and session handling, ensuring schema-compliant arguments are used.

When to Use It

When automating routine Dadata Ru operations and you need up-to-date tool schemas
When establishing or revalidating a Dadata Ru connection before workflows
When performing batch or multi-step Dadata Ru tasks that require known tool slugs
When debugging tool executions and needing explicit memory and session management
When handling workflows with pagination or evolving tool schemas

Quick Start

Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) as your MCP server
Step 2: Run RUBE_SEARCH_TOOLS to discover Dadata Ru tools and ensure the toolkit dadata_ru connection is ACTIVE with RUBE_MANAGE_CONNECTIONS
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the provided slug and schema-compliant arguments

Best Practices

Always call RUBE_SEARCH_TOOLS before any workflow to obtain current tool schemas
Ensure the Dadata Ru connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before execution
Use exact field names and types from the discovered tool schemas
Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs for related steps in a single workflow and generate new ones for new workflows

Example Use Cases

Automate address normalization and enrichment for a customer dataset using a discovered Dadata Ru tool
Validate and enrich company information by chaining multiple Dadata Ru tools in a single workflow
Bulk clean and deduplicate contact records across a CRM pipeline with session-based execution
Run incremental updates by paging through tool responses and reusing a session ID
Handle authentication flow by following the auth link when RUBE_MANAGE_CONNECTIONS reports non-ACTIVE

Frequently Asked Questions

Add this skill to your agents