Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

TickTick

TickTick integration for Flows360 workflows.

CategoryOther
AuthenticationOAuth 2.0
Version0.2.0
Published scopes2 published scopes
Last updatedSeptember 24, 2026

Overview

Connect TickTick with Flows360

TickTick integration for Flows360 workflows.

Use the TickTick connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 8 actions and 1 trigger.

Available actions

  • Create Task
  • Update Task
  • Get Task
  • Delete Task
  • Complete Task
  • Find Task
  • Get Task List
  • Custom API Call

Available triggers

  • New Task Created

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: TickTick
  • Package: @activepieces/piece-ticktick@0.2.0
  • Exact artifact digest: sha256:81992d0b60e379d25858fcc43ca431738a8d40b52f400570b4423bf44fb7d076
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Task (create_task), Creates a new in a specific list. Classification: read.
  • Update Task (update_task), Update an existing task. Classification: read.
  • Get Task (get_task), Retrieves the details of a specific task. Classification: read.
  • Delete Task (delete_task), Deletes an existing task. Classification: read.
  • Complete Task (complete_task), Marks an existing task as completed. Classification: read.
  • Find Task (find_task), Finds tasks in a specific project by their title. Classification: read.
  • Get Task List (get_project), Retrieves the details of a specific task list by ID. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Task Created, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0
Supported objects9
Supported actions8
Triggers1

Authentication

Authentication method: OAuth 2.0

Required scopes

tasks:readtasks:write

Authentication profiles

connection · oauth2

OAuth scopes: tasks:read, tasks:write

Supported objects

ObjectReadWriteNotes
Create Task Yes No Creates a new in a specific list.
Update Task Yes No Update an existing task.
Get Task Yes No Retrieves the details of a specific task.
Delete Task Yes No Deletes an existing task.
Complete Task Yes No Marks an existing task as completed.
Find Task Yes No Finds tasks in a specific project by their title.
Get Task List Yes No Retrieves the details of a specific task list by ID.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Task Created Yes No polling trigger declared by the pinned package.

Supported actions

Create Task · Read

Creates a new in a specific list.

create_task · Risk: low · Retry: safe

Inputs

  • projectId · string · Required, The list to create the task in.
  • title · string · Required
  • content · string · Optional
  • desc · string · Optional, Description of the checklist, often used with subtasks (items).
  • startDate · string · Optional
  • dueDate · string · Optional
  • priority · string · Optional
Update Task · Read

Update an existing task.

update_task · Risk: low · Retry: safe

Inputs

  • projectId · string · Required, The list to update the task in.
  • taskId · string · Required, The ID of the task to update.
  • title · string · Optional
  • content · string · Optional
  • desc · string · Optional, New description of the checklist items. Replaces existing.
  • startDate · string · Optional
  • dueDate · string · Optional
  • priority · string · Optional
Get Task · Read

Retrieves the details of a specific task.

get_task · Risk: low · Retry: safe

Inputs

  • projectId · string · Required, The list the task belongs to.
  • taskId · string · Required, The ID of the task to retrieve.
Delete Task · Read

Deletes an existing task.

delete_task · Risk: low · Retry: safe

Inputs

  • projectId · string · Required, The list the task belongs to.
  • taskId · string · Required, The ID of the task to delete.
Complete Task · Read

Marks an existing task as completed.

complete_task · Risk: low · Retry: safe

Inputs

  • projectId · string · Required
  • taskId · string · Required, The ID of the task to complete.
Find Task · Read

Finds tasks in a specific project by their title.

find_task · Risk: low · Retry: safe

Inputs

  • projectId · string · Required, The list to search within.
  • title · string · Required
  • matchType · string · Required, Select how the title should be matched.
Get Task List · Read

Retrieves the details of a specific task list by ID.

get_project · Risk: low · Retry: safe

Inputs

  • projectId · string · Required, Select the list to retrieve details for.
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Task Created · Poll

Triggers when a new task is created in a selected project.

Inputs

  • projectId · string

Setup

Setup

  1. Add the TickTick connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.

OAuth scopes

  • tasks:read
  • tasks:write
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-ticktick@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 8 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required TickTick connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-ticktick@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com