timely-automation

Timely Automation - Automating Time Tracking Tasks via Rube MCP

Skill Overview

The Timely Automation skill uses Composio’s Timely toolkit and Rube MCP to automate various Timely time-tracking operations without requiring an API key, including time entry creation, project management, and batch task processing.

Use Cases

Automated Time Entry Creation

When you need to automatically create Timely time entries based on events, this skill can execute time entry creation through the MCP interface without manual intervention or complex API key configuration.

Batch Processing of Timely Data

When you need to perform bulk operations on multiple projects, tasks, or time entries, you can efficiently execute Timely operations in batches using the RUBE_REMOTE_WORKBENCH and run_composio_tool() methods.

Integration into MCP Workflows

When you are building automated workflows with MCP (Model Context Protocol) and need to integrate Timely time-tracking functionality into an existing system, this skill provides complete tool discovery, connection management, and execution capabilities.

Core Features

Intelligent Tool Discovery

Use RUBE_SEARCH_TOOLS to automatically discover currently available Timely tools and their input schemas, ensuring that the latest tool definitions are always used and preventing execution failures caused by schema changes. This feature returns tool identifiers, recommended execution plans, and known considerations.

Connection Status Management

Use RUBE_MANAGE_CONNECTIONS to check and manage the Timely connection status in real time, ensuring that the connection is active before executing any automation task and providing clear authentication guidance and status feedback.

Flexible Tool Execution

Use RUBE_MULTI_EXECUTE_TOOL to execute discovered Timely tools. It supports schema-compliant parameter passing, session reuse, and memory management, making it suitable for everything from one-time operations to complex workflows.

Frequently Asked Questions

How do I configure Rube MCP to connect to Timely?

Simply add https://rube.app/mcp as an MCP server in your client configuration. No API key is required. After adding it, use RUBE_SEARCH_TOOLS to verify that the connection is available, then use RUBE_MANAGE_CONNECTIONS to configure the toolkit as timely and complete the authentication process.

Does Rube MCP require an API key?

No. Rube MCP uses a keyless design; you only need to add the MCP server endpoint. All authentication is completed through the authentication link returned by RUBE_MANAGE_CONNECTIONS, simplifying the configuration process.

Why must I call RUBE_SEARCH_TOOLS before every execution?

The schemas of Composio tools may change at any time. Hardcoding tool identifiers or parameters can lead to execution failures. RUBE_SEARCH_TOOLS always returns the currently valid tool definitions, input schemas, and recommended execution plans, making it a critical step for ensuring stable automation.

How can I verify that the Timely connection is active?

Call RUBE_MANAGE_CONNECTIONS and specify the toolkit as timely, then check the returned connection status. If the status is not ACTIVE, follow the authentication link provided to complete the setup. Execute the workflow only after confirming that the status has changed to ACTIVE.

What are the best practices for batch operations on Timely data?

Use RUBE_REMOTE_WORKBENCH together with the run_composio_tool() method for batch operations. Before execution, always use RUBE_SEARCH_TOOLS to obtain the correct tool schema, and reuse the same session ID throughout the batch operation to maintain context continuity.

What is the purpose of the memory parameter in RUBE_MULTI_EXECUTE_TOOL?

The memory parameter is used to pass and store contextual information between tool executions. Even if you do not currently need to store any data, you must include this parameter (it can be set to an empty object {}), as it is required for tool execution.