Log in Sign up
First-party app
TickTick

TickTick

Manage TickTick projects, tasks, focus records and habits via the TickTick Open API.

stable ProductivityProject Management

About

TickTick ships in the w6w first-party pack. It declares 23 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.

App id
io.w6w.ticktick
Version
0.1.2
Author
w6w
Licence
MIT
Categories
Productivity · Project Management

Overview

TickTick puts the same account a person’s TickTick app runs on within reach of a workflow — creating and updating tasks and projects, checking off habits, and reading back focus session history, through the TickTick Open API.

Projects (TickTick’s word for a list) can be created, updated and read back with their tasks and kanban columns; tasks can be created, updated, completed, deleted, moved between projects, and filtered by date, priority, tags or status, with a separate action for pulling completed tasks over a time range. Focus sessions and habit check-ins are also readable, so a productivity workflow can report on more than just open tasks.

It fits personal and team productivity automations — creating a task from an email or form, syncing due dates with another planner, or reporting on completed work and habit streaks — for any TickTick account connected through OAuth. Tags, comments, attachments and un-completing a task are product features TickTick’s own API does not expose, so they aren’t available here either.

Build with TickTick

Three routes to the same 23 actions. The Workflow tab is generated from TickTick's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.

Check In Habit

checkin-habit

Record or amend a habit check-in for one day. Keyed by a YYYYMMDD stamp, so re-posting the same day updates rather than duplicates.

Complete Task

complete-task

Mark a task complete. TickTick exposes no matching un-complete endpoint, so this is one-way through the API.

Create Habit

create-habit

Create a habit. Only the name is required (max 1000 characters).

Create Project

create-project

Create a TickTick project (list). Only the name is required.

Create Task

create-task

Create a task in a project. Title and project are required; subtasks, tags, reminders and a repeat rule can all be set in the same call.

Delete Focus

delete-focus

Delete a focus record. The Open API can read and delete focus records but never create or update one.

Delete Project

delete-project

Delete a project and everything in it. Destructive and not undoable through the API — TickTick exposes no archive or trash endpoint.

Delete Task

delete-task

Delete a task and its subtasks. The Open API exposes no trash or restore endpoint, so treat this as one-way.

Filter Tasks

filter-tasks

Query tasks across projects by project, start-date range, priority, tags and status. The nearest thing to a task search in the Open API; results are unpaged.

Get Focus

get-focus

Fetch one focus record (a pomodoro or timing session) by id. The focus type is part of the address, not a filter.

Get Habit

get-habit

Fetch one habit by id, in full. For its check-in history use List Habit Check-Ins.

Get Project

get-project

Fetch one project's metadata by id. Does not include its tasks.

Get Project With Data

get-project-data

Fetch a project together with its undone tasks and its kanban columns. This is the only way to enumerate a project's tasks — completed ones are excluded, use List Completed Tasks for those.

Get Task

get-task

Fetch one task, including its subtasks. Needs both the project id and the task id — there is no task-only address in this API.

List Completed Tasks

list-completed-tasks

List tasks completed within a time range, optionally restricted to some projects. The only way to see completed tasks — Get Project With Data returns undone ones only.

List Focuses

list-focuses

List focus records (pomodoro or timing sessions) in a time range. TickTick clamps any range longer than 30 days to the last 30 days before the end, without warning.

List Habit Check-Ins

list-habit-checkins

List check-in history for one or more habits over a date range. Dates are YYYYMMDD integers, not timestamps.

List Habits

list-habits

List every habit. Takes no parameters; the API has no paging or filter here.

List Projects

list-projects

List every TickTick project (what the apps call a List). Takes no parameters and returns all of them — the API has no paging and no filter.

Move Task

move-task

Move one task from one project to another. TickTick's endpoint is a batch; this action sends a single move so the operation stays visible in the graph.

Update Habit

update-habit

Update a habit. Sends only the fields you set — note that an explicitly empty name is documented to null the habit's name.

Update Project

update-project

Update a project's name, colour, view mode or kind. Sends only the fields you set; TickTick does not document whether the update merges or replaces.

Update Task

update-task

Update a task's title, content, dates, tags, priority, reminders or subtasks. Sends only the fields you set. Use Complete Task to mark it done and Move Task to change project.

A workflow step names the app and the action, and the editor fills in the connection when you pick one. This is the Step shape from the workflow spec, carrying TickTick's real ids. 

{
  "manifestVersion": "2",
  "name": "ticktick-example",
  "steps": [
    {
      "id": "checkin-habit",
      "uses": {
        "app": "io.w6w.ticktick",
        "action": "checkin-habit",
        "connection": "conn_YOUR_CONNECTION_ID"
      },
      "with": {
        "habitId": "<habitId>",
        "stamp": "<stamp>"
      }
    }
  ]
}

Here are some of the things you can do

  • Check In Habit

    perform
    checkin-habit

  • Complete Task

    perform
    complete-task

  • Create Habit

    perform
    create-habit

  • Create Project

    perform
    create-project

  • Create Task

    perform
    create-task

+18 more actions available

Every app-specific value here is a blank you have to fill in. An app action is reached through the connection that authenticates it, so the address is a connection id, not the app id — and connections belong to your account, so a public page cannot know yours. Create one for TickTick, then fill in the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the parameters that action declares. The call itself is real — the shape is transcribed from the studio's own snippet builder, which prints the same kind of blanks — but nothing in it is specific to TickTick. The Workflow tab is where this app's real ids are.

Install 
npm install @w6w/sdk
yarn add @w6w/sdk
pnpm add @w6w/sdk
deno add npm:@w6w/sdk
Code 
import { W6wClient, isActionRun } from "@w6w/sdk";

// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();

const envelope = await client.run({
  urn: "conn_YOUR_CONNECTION_ID",
  action: "create-task",
  payload: {
    projectId: "<value>",
    title: "<value>",
    // content: "<value>",
    // desc: "<value>",
    // isAllDay: "<value>",
    // startDate: "<value>",
    // dueDate: "<value>",
    // timeZone: "<value>",
    // reminders: "<value>",
    // tags: "<value>",
    // repeatFlag: "<value>",
    // priority: "<value>",
    // sortOrder: "<value>",
    // items: "<value>",
  },
});

if (isActionRun(envelope)) console.log(envelope.value);
Install the CLI 
npm install -g @w6w/cli
CLI 
w6w run conn_YOUR_CONNECTION_ID --action create-task --payload '{"projectId":"<value>","title":"<value>"}'

Give an AI agent TickTick — without giving it TickTick's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.

One tool call 
{
  "name": "w6w_invoke",
  "arguments": {
    "ref": "app:io.w6w.ticktick#checkin-habit",
    "input": {
      "habitId": "<habitId>",
      "stamp": "<stamp>"
    }
  }
}

Every tool names its target with a single ref. The app: form above doesn't name a connection at all — the host resolves which of the caller's TickTick connections to sign with, and refuses rather than guesses when the answer is ambiguous.

What the agent gets

Credentials it can't read

The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.

A tool surface scoped to the caller

Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.

A durable workflow in one call

Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.

Health-aware discovery

TickTick's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.

The MCP surface is part of the hosted platform. TickTick itself is MIT, and the runtime that executes it is source-available (FSL).

Request MCP access

Health checks

TickTick declares its own checks, so its health is a property of the app rather than something the host guesses at.

service

TickTick API reachable

Unsigned GET of api.ticktick.com/open/v1/project. TickTick publishes no status page — no status.ticktick.com, and ticktick.statuspage.io is an unclaimed Atlassian subdomain — so the honest probe is the API's own auth gate: a 401 with the documented JSON error envelope proves the service is serving.

quota

API quota headroom