--- title: "TickTick Integration" description: "Connect AI agents to TickTick. Agents create tasks from incoming events with due dates and priorities, complete and reschedule work in bulk, provision projects on demand, and pull a full project snapshot with open tasks and Kanban columns in one call." url: https://flowrunner.ai/integrations/ticktick date_modified: 2026-08-04T10:04:16-07:00 --- # TickTick [Productivity](https://flowrunner.ai/integrations/category/project-management-productivity) Connect AI agents to TickTick. Agents create tasks from incoming events with due dates and priorities, complete and reschedule work in bulk, provision projects on demand, and pull a full project snapshot with open tasks and Kanban columns in one call. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 10 actions · OAuth · available [TickTick website](https://ticktick.com/) · [Platform Documentation](https://developer.ticktick.com/) · Capability data verified 2026-07-28 1. A flagged email surfaces in the founder's inbox during the morning sweep 2. Create Task turns it into a TickTick task in the Follow-ups project with an ISO due date, a priority, and the email's context as Markdown content 3. Get Project Data pulls the project's full snapshot, open tasks and Kanban columns, in one call 4. The agent looks for the same commitment already tracked, matching on title and contact, to avoid a duplicate 5. The daily standup summary posts to Slack: what is due today, what slipped, what arrived overnight 6. The founder scans the summary and re-prioritizes with a reply, and the agent applies the changes with Update Task 7. Handled follow-ups are closed with Complete Task as replies go out ## What This Integration Enables TickTick is where individual operators actually track their day, which makes it the last mile of any automation that produces work for a human. FlowRunner agents treat it that way: they capture incoming commitments as tasks with due dates and priorities, keep external systems and TickTick agreeing about what is open, and read whole projects in one call with Get Project Data, metadata, open tasks, and Kanban columns together, so an agent can reason about a project's state before touching it. That snapshot operation matters: an agent that acts without reading the board is the automation people learn to distrust. - Create tasks from emails, forms, and calendar events with ISO due dates, priorities, and Markdown context - Read a project's complete open state in one call before any bulk action - Reschedule and re-prioritize in bulk through Update Task, driven by human replies to a daily summary - Provision projects for new workflows and retire them through a gated teardown - Close the loop with Complete Task as work is verifiably done ### Without FlowRunner **The task list is a second inbox**: Capturing work means retyping it, so half of it never gets captured **Priorities set once, never revisited**: Tuesday's priority order runs the week because re-triaging by hand costs more than it saves **Project cleanup never happens**: Finished workflows leave dead lists behind, and the sidebar becomes a museum ### With FlowRunner **Everything that asks for time becomes a task**: Emails, form submissions, and calendar events land in the right project with due dates and priorities set **Re-triage is a reply, not a session**: The agent proposes, the human adjusts in one message, and bulk updates apply in seconds **Projects live and die with their workflows**: Lists are provisioned on demand and torn down deliberately, with a human confirming the teardown ## Use Case Scenarios ### The morning brief that ends with a decision At 7 a.m., Get Project Data snapshots the founder's three working projects. The agent assembles a [Slack](https://flowrunner.ai/integrations/slack) brief: due today, overdue, newly arrived from last night's [Gmail](https://flowrunner.ai/integrations/gmail-service) sweep. The founder replies "push the vendor call to Thursday, make the investor update urgent," and the agent applies both with Update Task. Triage took ninety seconds and happened before the day started arguing. ### Meeting prep that exists before the meeting When [Google Calendar](https://flowrunner.ai/integrations/google-calendar) shows an event starting soon with an external attendee, the agent creates a prep task in the relevant project, due ahead of the meeting, with the attendee context in the task content. After the meeting, the follow-up task takes its place. The prep ritual stops depending on remembering to have one. ### A project per launch, gone when it is done Each product launch gets a Create Project call: a Kanban list with the launch checklist created as tasks. Agents move work through it, completions flow in from the connected systems via Complete Task, and the daily snapshot keeps the team honest. When the launch retrospective closes, the agent proposes teardown; the founder confirms, and Delete Project removes the list instead of leaving another dead board in the sidebar. ## Human-in-Loop Highlight Delete Project removes the project and every task inside it permanently, and the API offers no undo. The teardown step that makes on-demand project provisioning clean is the same call that, pointed at the wrong ID, erases a live board, and project IDs are exactly the kind of opaque string an automation can mix up between a finished launch list and an active one. Delete Task carries the same finality one task at a time. So FlowRunner treats teardown as a proposal, never a reflex: the agent presents the project's name and its remaining open-task count from Get Project Data, and the owner confirms before Delete Project runs. A stale list that survives an extra week costs a line in the sidebar. A live list deleted by a cleanup routine costs every commitment on it, and nobody finds out which ones until they are missed. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 10 actions ### Projects 5 - **List Projects** Retrieves all projects in the connected account with ID, name, color, sort order, view mode, and kind. The built-in Inbox is not returned. The discovery step before creating or querying tasks. - **Get Project** Retrieves one project's metadata by ID: name, color, view mode, and kind. - **Get Project Data** Retrieves a project with its undone tasks and Kanban columns in a single call. The snapshot an agent reads before deciding anything, and the evidence shown before any gated teardown. - **Create Project** Creates a project with a name, optional hex color, default view mode of List, Kanban, or Timeline, and a kind of task list or note list. The provisioning step for workflow-scoped lists. - **Delete Project** Permanently deletes a project and all of its tasks, with no undo; the Inbox cannot be deleted. The operation this page's confirmation gate exists for. ### Tasks 5 - **Get Task** Retrieves one task by project ID and task ID, with title, content, checklist items, priority, status, tags, and scheduling fields. - **Create Task** Creates a task with a required title, optional Markdown content, target project (blank routes to the Inbox), ISO 8601 due date, priority, and all-day flag. The capture operation behind every intake workflow. - **Update Task** Updates a task's fields by project and task ID; provided fields replace current values, omitted fields stay. The mechanism behind reply-driven re-triage. - **Complete Task** Marks a task done, removing it from the project's open list. The closing handshake between external systems and the board. - **Delete Task** Permanently deletes a task from a project, with no undo. Reserved for confirmed removals rather than routine cleanup. ## Frequently Asked Questions ### What can FlowRunner do with TickTick? FlowRunner agents can run List Projects, Get Project, and Get Project Data in TickTick, plus 7 more actions. ### Does connecting TickTick to FlowRunner require OAuth? Yes. TickTick connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can TickTick trigger a FlowRunner workflow automatically? TickTick doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at TickTick?** This integration exposes TickTick to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/ticktick. Site index: https://flowrunner.ai/llms.txt