What do I need to begin?

You need a connected Rube MCP, an ACTIVE Timecamp connection for the timecamp toolkit, and you must call RUBE_SEARCH_TOOLS first to fetch current tool schemas.

How do I run a Timecamp task securely?

Discover the tool with RUBE_SEARCH_TOOLS, confirm the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, then execute the tool via RUBE_MULTI_EXECUTE_TOOL using the proper memory and session_id.

What common issues should I avoid?

Avoid hardcoding tool slugs; always fetch current schemas, ensure ACTIVE connection, include the memory parameter, reuse session IDs within a workflow, and handle pagination tokens if results are paginated.

timecamp-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Timecamp Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/timecamp

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Timecamp operations through Composio's Timecamp toolkit using Rube MCP. This skill emphasizes always querying current tool schemas with RUBE_SEARCH_TOOLS to stay in sync with updates, and provides a guided flow from establishing connections to executing tools.

How This Skill Works

The workflow starts by validating the RUBE_SEARCH_TOOLS endpoint to fetch current Timecamp tool schemas. Next, you manage the Timecamp connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, you execute the discovered tool via RUBE_MULTI_EXECUTE_TOOL using the tool slug, proper arguments from the schema, a memory object, and a session_id from the discovery step.

When to Use It

When you need to automate Timecamp tasks via Composio
Before running any workflow to fetch current tool schemas with RUBE_SEARCH_TOOLS
After establishing a Timecamp connection, verify it is ACTIVE before executing tools
When performing batch operations using RUBE_MULTI_EXECUTE_TOOL with discovered tools
When handling session continuity and pagination across results

Quick Start

Step 1: Ensure Rube MCP is connected and verify RUBE_SEARCH_TOOLS responds
Step 2: Use RUBE_SEARCH_TOOLS to discover Timecamp tools and their input schemas
Step 3: Verify the Timecamp connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, then run RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug and memory

Best Practices

Always search first for current tool schemas using RUBE_SEARCH_TOOLS
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results (schema compliance)
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and fetch new ones for new workflows; handle pagination if present

Example Use Cases

Automate a weekly Timesheet entry in Timecamp by discovering the relevant tool and executing daily entries
Bulk update multiple time entries across several tasks after a sprint review
Create Timecamp entries automatically when a new project task is created in your system
Synchronize Timecamp data with project management milestones to keep reports aligned
Generate daily time reports and export them to a file or dashboard

Frequently Asked Questions

Add this skill to your agents