What is due in Wrike this week and what changed on a project.
Connect Wrike with a permanent access token and your data-centre host and Memtro reads tasks by status, title or recent change with importance, dates and who is responsible, projects, people, time logs and comments. The token acts as you. The hourly sync writes tasks into memory. When you ask, and once an administrator has granted the action by name, it can create, edit, assign, complete, move or delete tasks, comment on them, log or correct time, create and edit folders and projects, and invite a person by email, whose accepted invitation may take a paid seat.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Wrike tool, reads what it needs, and answers with the source cited.
These tools change something in Wrike. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Wrike is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Wrike + MemtroWhat is due in Wrike this week?
What changed on the Northwind launch project since Monday?
How many hours did I log on the Acme migration last week?
Create a task in the Brightwave Ltd project: draft the onboarding email, due next Wednesday, Priya Nair responsible
Mark the BigCo pricing page task completed
At Monday planning the team lead asks what is due in Wrike this week. Memtro reads the open tasks due in the week, turns responsible ids into names, and lists each task with its importance and who owns it, with anything overdue first.
Before her leave, Priya Nair asks Memtro to move her three open BigCo tasks to Dan Fletcher and push their due dates by a week. Memtro swaps the assignees and changes the dates under her name, and Wrike notifies Dan and the tasks' followers by their settings.
The teams that lean on Wrike most, a question each of them asks, and what they connect beside it.
A record in Wrike is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Clio Manage
YouTrack
Canny
Float
Productive
Smartsheet
Financial Cents
Karbon
Scoro
Kanboard
Kimai
Leantime
Acuity Scheduling
Luma
Tito
Fellow
Samsara
ServiceM8
Cliniko
Fleetio
SavvyCal
Chili Piper
Humanitix
Circleback
Aha!
Tempo
Smoobu
Semble
Airmeet
Beds24
Bookeo
Commusoft
Fergus
Fixflo
Housecall Pro
Nookal
Paymo
ProductPlan
SimplyBook.me
TimeCamp
Workiz
Guesty
Buildium
Skilljar
Runn
ClockodoIn Wrike open your profile picture → Apps & Integrations → API, create an app or open one, and under Permanent access token choose Create token. Copy it, it is shown once
Find your data-centre host in your browser's address bar when signed in: www.wrike.com, app-eu.wrike.com or app-us2.wrike.com
In Memtro open Connections → Wrike, paste the Permanent access token and the Data-centre host, and connect. On Wrike's Team plan a task's status cannot be set through the API
Ask what is due this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Wrike tools are the same everywhere.
Only when you ask, and only what it has been granted: create a task in a Wrike folder or project; add a comment to a Wrike task; log time on a Wrike task; edit a Wrike task's title, description, importance or dates; add or remove assignees on a Wrike task; set a Wrike task's status (complete, defer, cancel, reopen); move a Wrike task into or out of folders; delete a Wrike task (to the Recycle Bin); make one Wrike task depend on another; create a Wrike folder or project; edit a Wrike folder or project; correct a Wrike time log; edit a Wrike comment within 5 minutes of posting; invite a person into the Wrike account by email. 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. An hourly sync anchors recently changed Wrike records into memory as entities.
Permanent access token and data-centre host. In Wrike open your profile picture → Apps & Integrations → API, create an app or open one, and under Permanent access token choose Create token. Copy it, it is shown once.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time