How do I ensure tool schemas are current?

Always call RUBE_SEARCH_TOOLS before executing and verify you have the latest slugs and argument schemas.

How do I verify a connection to Oncehub?

Use RUBE_MANAGE_CONNECTIONS with toolkits ["oncehub"] and confirm the connection status is ACTIVE before running workflows.

Do I need to include memory in tool executions?

Yes. Include the memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if it’s empty.

oncehub-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Oncehub Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/oncehub

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Oncehub operations through Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before any execution, and validating an ACTIVE Oncehub connection via RUBE_MANAGE_CONNECTIONS. Workflows rely on structured tool executions to avoid hard-coded slugs.

How This Skill Works

It uses RUBE_SEARCH_TOOLS to fetch tool slugs and schemas, then RUBE_MANAGE_CONNECTIONS to verify an ACTIVE connection to Oncehub. After validation, workflows execute tools via RUBE_MULTI_EXECUTE_TOOL with the required arguments and a memory object, reusing session IDs for continuity.

When to Use It

Starting a new Oncehub workflow with up-to-date tool schemas
Reconnecting to Oncehub after credential changes or reconnection steps
Running batch or bulk tasks across multiple Oncehub operations
Ensuring correct memory and session handling within a workflow
Debugging or validating tool schemas and handling pagination tokens during discovery

Quick Start

Step 1: Discover Available Tools RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Oncehub task"}] session: {id: "existing_session_id"}
Step 2: Check Connection RUBE_MANAGE_CONNECTIONS toolkits: ["oncehub"] 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"

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from search results to avoid schema errors
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

Create a new Oncehub event from a CRM trigger using the discovered tool slug
Update event details (time, participants) via the appropriate Oncehub tool from search results
Retrieve upcoming events for a team and summarize them for a daily brief
Bulk-create multiple Oncehub events for a marketing campaign
Reconcile scheduled events with an external calendar by reusing a session

Frequently Asked Questions

Add this skill to your agents