Todoist + Memtro

Only when you ask, and only what it has been granted: create a task in a project, with a due date, priority and labels; complete a task; add a task from one line of Quick Add text; update a task's text, description, due date, deadline, priority, labels, assignee or duration; reopen a completed task; delete a task and its sub-tasks permanently; move a task to another project, section or parent task; comment on a task or project, notifying only the collaborators named; edit a comment; delete a comment permanently; create a project; update a project's name, description, colour, view or favourite; archive a project; delete a project with all its sections and tasks permanently; create a section in a project; create a label. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.

API token. In Todoist go to Settings → Integrations → Developer and copy the API token shown there.

Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Todoist, choosing the same kinds; the tab shows Todoist's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.