Do I need API keys to use Ticktick automation?

No API keys are required. Add the MCP server at https://rube.app/mcp and authenticate via RUBE_MANAGE_CONNECTIONS; the system uses tool schemas from RUBE_SEARCH_TOOLS.

How do I keep tool schemas up to date?

Always run RUBE_SEARCH_TOOLS before executing; do not hardcode slugs or argument names—rely on the returned schemas.

What if the Ticktick connection is not ACTIVE?

Follow the auth link provided by the toolkit to complete setup, then re-check the connection status before running workflows.

ticktick-automation

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

Files (1)

SKILL.md

2.9 KB

Ticktick Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ticktick

Prerequisites

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

Step 2: Check Connection

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

Overview

Ticktick Automation via Rube MCP enables programmatic control of Ticktick tasks using Composio's toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before invoking actions, preventing hard-coded tool slugs and ensuring up-to-date capabilities. This approach makes Ticktick workflows repeatable, auditable, and scalable across teams.

How This Skill Works

The workflow starts by connecting Rube MCP and the Ticktick toolkit, then querying RUBE_SEARCH_TOOLS to fetch available tools and their input schemas. Before any action, RUBE_MANAGE_CONNECTIONS validates an ACTIVE toolkit connection. Finally, RUBE_MULTI_EXECUTE_TOOL runs the chosen tool with the schema-compliant arguments, passing memory and a session_id to support retries and session reuse.

When to Use It

Create a Ticktick task from a chat message or note
Update due dates or priorities on existing tasks in Ticktick based on milestones
Bulk-create tasks from a backlog list or CSV feed
Fetch upcoming tasks and present a concise daily digest
Reuse a single session to chain multiple steps in a workflow

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds
Step 2: Discover available Ticktick tools with RUBE_SEARCH_TOOLS to get tool slugs and input schemas
Step 3: Connect to Ticktick with RUBE_MANAGE_CONNECTIONS and execute a discovered tool using RUBE_MULTI_EXECUTE_TOOL with proper arguments, memory, and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before every workflow to fetch current tool slugs and schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tool
Use exact field names and types from the search results; avoid hard-coded slugs
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow where possible and monitor pagination in results

Example Use Cases

Create a new Ticktick task from a customer chat by selecting the appropriate tool slug from the search results
Update the due date of upcoming tasks in Ticktick based on new project milestones
Bulk-create Ticktick tasks from a backlog list or CSV feed by iterating items and invoking the corresponding tool
Fetch upcoming Ticktick tasks and generate a concise daily digest for a user
Automatically complete a set of tasks when a related milestone is marked done in your integration

Frequently Asked Questions

Add this skill to your agents