TickTick

Install corsair and @corsair-dev/ticktick, add the TickTick plugin, and connect with OAuth. Then call methods like corsair.ticktick.api.oauth.generateAuthUrl() from your app. Corsair stores tokens, and keeps each tenant isolated.

Yes. TickTick needs an OAuth app with scopes that match what you automate. Register the app in TickTick, configure redirect URLs, then connect through Corsair or managed OAuth in Hub.

Yes. One Corsair client can hit TickTick, GitHub, Notion, Stripe, and the rest. Trigger TickTick from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for task and habit manager for to-do lists, calendars, reminders, and personal productivity. Common builds include sync jobs, admin tooling, and agents that call TickTick APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per TickTick API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/ticktick in the open repo. When TickTick ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your TickTick data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store TickTick data on your behalf.