← Back to Skills Marketplace
byungkyu

Todoist

by byungkyu · GitHub ↗ · v1.2.7 · MIT-0
cross-platform ✓ Security Clean
10244
Downloads
13
Stars
0
Active Installs
14
Versions
Install in OpenClaw
/install todoist-api
Description
Todoist API integration with managed OAuth. Manage tasks, projects, sections, labels, and comments. Use this skill when users want to create, update, complete, or organize tasks and projects in Todoist. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Todoist connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Todoist action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Todoist examples; they add no Todoist capability - Todoist is not an event source, a trigger cannot read Todoist data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Install only if you are comfortable using Maton as the gateway to your Todoist account. Review every requested write, connection, hosted function, trigger, or destination before approving it, and be especially careful with persistent automations or any destination outside Maton-controlled hosts.
Capability Assessment
ℹ Credentials
Network access, Bash, OAuth login, and optional API-key HTTP calls are proportionate to a Todoist API integration, with clear guidance to avoid exposing credentials and to prefer the CLI credential store.
ℹ Install Mechanism
Installation requires the external Maton CLI via pinned npm or Homebrew instructions and a Maton account. The artifact does not ship executable code or hidden install scripts.
✓ Instruction Scope
The instructions default to read/list calls, require explicit user approval for connections and all write operations, require user approval for hosted functions/triggers, and warn that third-party event payloads are untrusted data rather than instructions.
ℹ Persistence & Privilege
Persistent OAuth connections, hosted functions, scheduled/event triggers, and trigger destinations are documented and potentially sensitive, but the skill discloses their persistence, requires explicit approval, recommends narrow scope, and provides deletion guidance.
ℹ Purpose & Capability
The core capability matches the stated Todoist purpose: listing and managing tasks, projects, sections, labels, and comments through Maton. The artifact also documents Maton functions and triggers for automation, including references for other event sources, but it explicitly frames those as optional platform automation and not default Todoist access.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install todoist-api
  3. After installation, invoke the skill by name or use /todoist-api
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.7
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.6
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.5
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.4
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.3
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.2
Resolve remaining audit findings: state one consistent endpoint policy instead of conflicting scope claims, qualify the local-execution and high-impact wording, note that locale examples are illustrative, and correct app-specific auth, method and upload-path documentation
v1.2.1
Address security-audit findings: disclose the api passthrough in the access-scope and description text, warn on irreversible connection deletion, add response data-minimization guidance, and correct app-specific auth and request-body notes
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.4
- Changed all API endpoints and examples from `gateway.maton.ai` and `ctrl.maton.ai` to `api.maton.ai` for consistency. - Added a Security & Permissions section clarifying access and user approval requirements for write operations. - Removed obsolete reference to deleted LICENSE.txt file. - Minor clarifications and formatting improvements in API documentation examples.
v1.0.3
- Switched API endpoints from `/rest/v2` to `/api/v1` for all Todoist requests. - Updated base URLs and code examples to reflect the new API version. - Adjusted response examples and field names to match the v1 API structure. - Clarified quick start instructions and connection header usage with new endpoint paths.
v1.0.2
- Added a new clawdbot metadata section, including an emoji and required environment variable (MATON_API_KEY). - No changes to functionality or API; documentation updated with metadata only.
v1.0.1
- No file changes detected in this release. - Internal version increment to 1.0.1; no new features or user-facing updates included.
v1.0.0
Initial release: Todoist API integration with managed OAuth - Enables task, project, section, label, and comment management via the Todoist REST API v2. - Supports authentication and connection management with Maton API key and OAuth. - Provides endpoints for creating, updating, listing, and deleting projects and tasks. - Includes Python code samples for common API operations. - Allows management of multiple Todoist connections through the control panel. - Comprehensive API reference and setup instructions included.
Metadata
Slug todoist-api
Version 1.2.7
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 14
Frequently Asked Questions

What is Todoist?

Todoist API integration with managed OAuth. Manage tasks, projects, sections, labels, and comments. Use this skill when users want to create, update, complete, or organize tasks and projects in Todoist. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Todoist connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Todoist action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Todoist examples; they add no Todoist capability - Todoist is not an event source, a trigger cannot read Todoist data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 10244 downloads so far.

How do I install Todoist?

Run "/install todoist-api" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Todoist free?

Yes, Todoist is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Todoist support?

Todoist is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Todoist?

It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.7.

💬 Comments