How do I start automating Ascora tasks?

Add the Rube MCP endpoint, verify RUBE_SEARCH_TOOLS, manage the Ascora connection, then discover tools and execute with RUBE_MULTI_EXECUTE_TOOL using a session_id and memory.

What if tool schemas change?

Always run RUBE_SEARCH_TOOLS first to fetch current slugs and input schemas and avoid hardcoded values.

Should I reuse sessions between steps?

Yes, reuse session IDs within a workflow for continuity; generate new sessions only for entirely new workflows.

ascora-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Ascora Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ascora

Prerequisites

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

Step 2: Check Connection

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

Overview

Ascora Automation via Rube MCP enables end-to-end automation of Ascora operations by leveraging Composio's Ascora toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution and ensuring an ACTIVE Ascora connection via RUBE_MANAGE_CONNECTIONS. This approach reduces schema drift and improves reliability of automated workflows.

How This Skill Works

First, discover available Ascora tools using RUBE_SEARCH_TOOLS to obtain up-to-date tool slugs and input schemas. Then verify your connection with RUBE_MANAGE_CONNECTIONS and run tools with RUBE_MULTI_EXECUTE_TOOL, passing a session_id and memory payload. Always include memory even if empty and reuse sessions for continuity.

When to Use It

When you need up-to-date tool schemas before automating Ascora tasks
When setting up or validating an Ascora connection prior to execution
When orchestrating multi-tool Ascora workflows in a single session
When performing bulk or repeated Ascora operations across tasks
When debugging issues caused by changed tool schemas or pagination

Quick Start

Step 1: Add the Rube MCP endpoint and verify RUBE_SEARCH_TOOLS responds
Step 2: Manage the Ascora connection and ensure the toolkit is ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS for your use case and execute with RUBE_MULTI_EXECUTE_TOOL using a session_id and memory

Best Practices

Always call RUBE_SEARCH_TOOLS first before executing any tool
Verify that RUBE_MANAGE_CONNECTIONS shows ACTIVE for the Ascora toolkit
Use exact field names and types from the search results; avoid hardcoding
Include memory in RUBE_MULTI_EXECUTE_TOOL calls even if empty
Reuse session IDs within a workflow and handle pagination tokens if present

Example Use Cases

Automate a daily Ascora data fetch by discovering the right tool and executing with memory in a single session
Orchestrate a multi-tool Ascora workflow by first discovering tools, then validating connection and executing sequentially
Onboard a new Ascora operation by validating the tool schemas via RUBE_SEARCH_TOOLS before running
Bulk run several Ascora tasks in one session using RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Debug a failed Ascora task caused by a schema change by re-fetching schemas prior to execution

Frequently Asked Questions

Add this skill to your agents