What is Rube MCP in Timelink automation?

Rube MCP is the central management point used to discover Timelink tool schemas, manage connections, and execute tools within Composio's Timelink toolkit.

Why must I always search tools first?

Tool schemas change over time; fetching current slugs and input schemas ensures your automation uses valid, up-to-date parameters and avoids execution errors.

What if a tool schema changes mid-workflow?

RUBE_SEARCH_TOOLS should be re-run to refresh tool slugs and schemas before continuing. Do not proceed with cached or hardcoded values.

timelink-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Timelink Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/timelink

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Timelink operations using Composio's Timelink toolkit through Rube MCP. It prioritizes discovering current tool schemas with RUBE_SEARCH_TOOLS and requires an active Timelink connection to execute workflows reliably.

How This Skill Works

The workflow starts by invoking RUBE_SEARCH_TOOLS to fetch available Timelink tool slugs and input schemas. Next, it checks the Timelink connection status with RUBE_MANAGE_CONNECTIONS. Finally, it runs tools via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments, always including memory, and reusing session IDs when appropriate.

When to Use It

You need to automate routine Timelink tasks across multiple workflows and want up-to-date tool schemas.
Tool schemas change or new Timelink capabilities are released; you must fetch current slugs before execution.
You must verify an ACTIVE Timelink connection before running any Timelink workflows.
You want to perform bulk Timelink operations or chain several Timelink actions in a single session.
You are integrating Timelink actions into larger automated processes and need reliable session management.

Quick Start

Step 1: Get Rube MCP set up and verify RUBE_SEARCH_TOOLS responds to confirm tool schemas.
Step 2: Use RUBE_MANAGE_CONNECTIONS with toolkit 'timelink' to ensure an ACTIVE Timelink connection.
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the provided slug and schema-compliant arguments, including memory: {}.

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and input schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding slugs or arguments.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty (memory: {}).
Reuse session IDs within a workflow where possible; generate new IDs only for new workflows.

Example Use Cases

Daily Timelink status pull: discover tools with RUBE_SEARCH_TOOLS, verify connection, then execute the status tool with current schema fields.
Create a Timelink item from a CRM feed: fetch the appropriate tool slug, validate connection, and run with CRM-derived arguments.
Bulk close completed Timelinks: discover bulk-close tool, ensure ACTIVE connection, execute across a batch with proper session reuse.
Timelink performance report: discover reporting tool, confirm schema, run with date range and aggregation parameters.
Retry failed Timelink tasks: reuse an existing session, re-run the failed tool using the same memory structure and updated inputs.

Frequently Asked Questions

Add this skill to your agents