Manus

Your assistant can list your Manus tasks, filter them by status, project, search term or time range, and then read any single task in full: its current status, the output messages it has produced, its metadata, and the credits it has consumed. That turns a check-in from opening the Manus interface and scrolling into asking a question and getting the state of everything in one answer. It reads only.

What you end up with. A current status list of your Manus tasks, with the finished ones summarized and the stalled ones named.

Start with it bringing you the information and you deciding.

Never without. Read a task's own output as its claim about what it did, not as verified fact. Status tells you the run finished, and it does not tell you the result is correct.

Built on: List tasks / Get Task

Credit usage is on the task record, so the assistant can pull the tasks for a period and total the credits by project or by the kind of work. The number that matters is usually not the total. It is the one task that ran four times because the instructions were vague, and that only shows up when you look at the tasks side by side.

What you end up with. Credit consumption broken out by project and task, with the expensive repeats identified by name.

Start with it bringing you the information and you deciding.

Never without. Treat this as the account's own usage record, not as a bill. Reconcile it against your actual invoice before you use it to make a spending decision.

Built on: List tasks / Get Task

It can create a Manus task from a description you give it, attach files, and specify which connectors the task is allowed to use, then hand back the task ID. Because the same action continues an existing task when you pass that ID, a follow-up correction is another instruction rather than a fresh start. The pattern that works is to dispatch, get on with something else, and read the result back later.

What you end up with. A Manus task running against your instructions, with its ID recorded so you can check on it or add to it later.

Start with it doing the work and checking with you.

Never without. Be deliberate about which connectors the task is allowed to use. You are handing a second agent access to the systems you name, and it will act on them while you are not watching.

Built on: Create New Task / Get Task

Manus projects hold default instructions that apply to every task created inside them. So the assistant can create a project once with the standing context, then create each new task against that project ID rather than restating the rules every time. It can also list your existing projects to find the right one. This is the difference between explaining your standards weekly and writing them down once.

What you end up with. A Manus project carrying your standing instructions, with new tasks inheriting them instead of being briefed from scratch.

Start with it doing the work and checking with you.

Never without. Read the default instructions back after they are written. Every future task in that project inherits them, so a vague line becomes a standing vague line rather than a one-time mistake.

Built on: Create New Project / List Projects / Create New Task

Uploading is two steps and the connector only covers one of them. It creates a file record and hands back a presigned upload URL that expires at a stated time. Putting the content at that URL is a separate PUT request that Manus does not expose as an action, so whether it happens depends on what else your assistant can reach. Once content is there, the connector can read the file's status, which moves from pending to uploaded, and list the ten most recent uploads.

What you end up with. A file record created with its upload URL, and the file's status read back so you know whether the content actually arrived.

Start with it doing the work and checking with you.

Never without. Check the status reads uploaded before you attach the file to a task. A record can exist while the content never made it, and the task then runs against nothing without saying so.

Built on: Create File / Get file details / List uploaded files / Create New Task

The assistant can update a task's title, its visibility in the task list, and its sharing settings, including turning public sharing on. That is the route to sending a result to a client or a colleague without adding them to the account. It is also the setting with the widest consequence in this connector, because it changes who can reach the task output.

What you end up with. The task titled clearly and shared exactly as far as you intended, confirmed by reading the setting back.

Start with it doing the work and checking with you.

Never without. Never enable public sharing without reading the full task output first. The output carries whatever the task saw, including anything it pulled from a connected system, and public means reachable by anyone with the link.

Built on: Update Task / Get Task

It can delete a task and delete an uploaded file, and Manus is direct about what that means. Deleting a task is permanent and cannot be undone. Deleting a file removes both the record and the stored content. Run it as two moves. Have it list what matches your rule, read that list yourself, then approve deletion of exactly those items.

What you end up with. The finished tasks and their source files removed, and a saved list of every item deleted with its ID and title.

Start with it doing the work and checking with you.

Never without. Never approve a deletion described only as a rule, and save any task output you still need before deleting. Manus states that deleting a task cannot be undone, and deleting a file removes the stored content as well as the record, so both take the evidence of what was done with them.

Built on: List tasks / List uploaded files / Get file details / Delete task / Delete a file