Teamwork.com + Memtro

Only when you ask, and only what it has been granted: create a task in a Teamwork task list; add a comment to a Teamwork task; log unbillable time on a Teamwork task; change a task: name, description, dates, assignees, priority, progress, estimate or task list; add a subtask under a task; mark a task complete, or reopen it; delete a task and its subtasks, permanently; create a task list in a project; create a project, or change its name, description or dates; add a milestone to a project, or mark one complete; start a timer on a task, stopping any timer already running; change or delete a logged time entry; create a tag. 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.

Site address and API key. In Teamwork open your avatar (top right) → Edit My Details → API & Mobile, show your token and copy it. It acts as you, so Memtro can change only what you can.

Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Teamwork.com, choosing the same kinds; the tab shows Teamwork.com'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.