Integrations · Todoist
Guild agents create, update, close, and delete Todoist tasks and projects on your team’s behalf. Store the Todoist API key as a server-side credential so agent code never sees it, then use credential policies to restrict exactly which operations each agent can call.
Book a demo
See how teams govern agents that use Todoist.
Talk to sales
Get access to Guild, then connect Todoist to your first agent.
What the Todoist integration exposes
The integration isguildai~todoist-openapi. Tools cover tasks, projects, sections, labels, comments, reminders, folders, workspace membership, invitations, activity logs, productivity stats, backups, and template operations. Tools are prefixed todoist_openapi_ and can be narrowed with pick() to include only what an agent needs. The catalog entry requires a Todoist API token, which Guild sends as a bearer token in the Authorization header.
How it works
1
Open credentials in Guild
Go to Access & setup > Credentials in Guild and click Connect. Select todoist-openapi and paste your Todoist API key into the API Key field.
2
Scope the credential
Choose account, workspace, member, or agent scope. See Credentials for the difference between each scope and who can set them.
3
Add tools to your agent
Import
TodoistOpenapiTools from @guildai-services/guildai~todoist-openapi and spread it into your agent’s tools object. Use pick() to include only the tools your agent needs.Why Todoist access needs governing
Todoist tools can delete tasks and all their subtasks, delete projects and all their sections and tasks, remove workspace users, and revoke access tokens. An agent with unrestricted access to a shared credential can make changes that affect every member of a workspace. Credential policies let you write ALLOW and DENY rules that Guild’s credential proxy enforces before any request reaches Todoist, limiting agents by operation name, HTTP method, workspace, or agent ID. Credentials are injected server-side by Guild’s proxy after the policy check passes. Agent code never sees the API key, and a matching DENY rule blocks a request even when an ALLOW rule also matches. Credential scoping lets you bind a credential to one agent, one workspace member, or one workspace, so a tightly scoped agent cannot reach data outside its remit.About the Todoist integration
Agents can create, update, close, and delete tasks and projects, organize work into sections and labels, and manage reminders and comments. They can also handle workspace membership, invitations, and folders. Productivity stats, activity logs, backups, and template operations are also available. The integration isguildai~todoist-openapi.
Authentication
- Type: API key
- Header: Guild sends the key as a bearer token in the
Authorizationheader
Setup
1
Connect Todoist
In Guild, go to Access & setup > Credentials, click Connect, select todoist-openapi, and paste the key into API Key.
Usage
Selecting specific tools
Tools are named with thetodoist_openapi_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildai~todoist-openapi:
All 123 tools
All 123 tools
Frequently asked questions
Can an agent react to new Todoist tasks arriving in real time?
Can an agent react to new Todoist tasks arriving in real time?
No. The catalog entry for
guildai~todoist-openapi lists no webhook events, so the integration does not support event-driven triggers from Todoist.How do I stop an agent from deleting tasks or projects?
How do I stop an agent from deleting tasks or projects?
Add a DENY rule in credential policies targeting operations such as
todoist_openapi_delete_task* and todoist_openapi_delete_project*. A DENY rule takes precedence over any ALLOW rule and is enforced by Guild’s credential proxy before the request reaches Todoist.Does the agent ever see my Todoist API key?
Does the agent ever see my Todoist API key?
No. Guild stores the key as a server-side credential and injects it as a bearer token in the
Authorization header after the credential policy check passes. The key never enters agent code, the agent’s prompt, or its state.Can one Todoist credential serve multiple workspaces?
Can one Todoist credential serve multiple workspaces?
Yes. An account-scoped credential serves every workspace the account owns by default. You can also scope a credential to a single workspace, a single member, or a single agent. See Credentials for how Guild selects which credential to use when more than one is available.
Put a governed agent on Todoist today
Book a demo
See how teams govern agents that use Todoist.
Talk to sales
Get access to Guild, then connect Todoist to your first agent.