Resources · Zapier integration

Manus Zapier integrationAutomate Manus with Zapier.

The Manus Zapier integration gives you 2 triggers, 5 actions and 1 search. Hand instructions to Manus from your other apps, hear back the moment a task stops, then rename, hide, read or delete that task without opening Manus at all.

See the 8 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What Manus and Zapier do together

Manus is a general AI agent: you describe a goal, it works on it as a task. Zapier is the bridge that starts those tasks from other apps and reacts when they move. The integration links the two, so a Manus task can begin, continue or end up somewhere useful with nobody copying text between tabs.

A task brief that writes itself. With Create Task, an entry in another app becomes the instructions of a new Manus task. Zapier gets back the task ID and its direct URL, so the next step can file that link wherever your team looks.

A status report on every stop. Task Stopped fires when a task completes, asks for input, becomes pending or hits an error. Chain Get Task behind it and you hold the status, title, URL, sharing setting and credit usage of that exact task.

A tidy task list. Update Task changes a title, the sharing setting or whether the task shows in the Manus task list. Automated runs stop crowding the tasks people work on by hand.

What Zapier does not do here: there is no find-or-create variant, so Get Tasks only looks things up and never creates a missing task. Delete Task is permanent and cannot touch agent tasks or subtasks. And both triggers are instant, so there is no polling interval to tune on this app. Before you pick a tool, see our Zapier review; if you are weighing other options, open our n8n vs Zapier comparison.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every line of this page. Here is what each one means in plain English.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or changes something in an app on your behalf.
Task
The unit Zapier bills. One task is one action your Zap completed successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap carry on only when the incoming data meets a condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can reuse what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it needs a paid plan.
Cost

What a Manus Zap really costs

Zapier bills tasks, not triggers. A Manus task starting, stopping or being created never costs you anything on the Zapier side by itself.

  • Free plan100 tasks a month, two-step Zaps
  • BilledEach action that succeeds
  • Never billedTriggers, checks and failed actions
  • Premium appNo, works on the free plan

Each action that succeeds counts as one task, and each one counts separately: a Zap with Create Task plus a spreadsheet row uses two per run. An action that fails is not billed. Manus is not a premium app, so the free plan accepts it, with 100 tasks a month and unlimited Zaps of two steps. Add a second action such as Get Task, a filter or the Get Tasks search, and the Zap turns multi-step, which needs a paid plan.

The interval grid below sets how often Zapier checks a polling trigger. It does not apply to the two Manus triggers, which are both instant.

Connect

Connect your Manus account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps, then click + Add connection. You need a Manus account first, plus access to any task you did not create yourself and want the Zap to touch.

  2. 02

    Pick Manus in the dialog

    Type Manus in the search box of the dialog, select it, then click Add connection. A new tab opens on the Manus side so you can sign in with the account the Zaps will use.

  3. 03

    Grant access and come back

    Sign in to Manus in that tab and grant Zapier access to the account. Every Manus step of every Zap then reuses that connection, so you only do this once.

First Zap

Your first Zap: rename and log every new Manus task

GoalEach new Manus task gets a clear title, and a row in a spreadsheet records it, so the team can find automated work without scrolling Manus.

  1. 01

    Create the Zap and set the trigger

    Start a new Zap, pick Manus and Task Created. Test it: Zapier brings back the three most recent tasks of the connected account, so you map fields from a real one, not a sample.

  2. 02

    Add Update Task

    Add Manus again as the action and choose Update Task. Map the Task ID from what the trigger returned at test (check it is there), then set the title you want.

  3. 03

    Decide on visibility

    Set Show in Task List if automated tasks should leave the list, or leave it blank to keep the current setting. A hidden task still opens through its direct URL.

  4. 04

    Log the link

    Add your spreadsheet as a third step and map the task details the earlier steps returned; check at test which ones actually come through. Three steps make this a multi-step Zap, so it needs a paid plan.

  5. 05

    Test, then publish

    Run each step once and read what came back before moving on. Check the renamed task in Manus, then click Publish to switch the Zap on for the tasks created from now on.

Triggers

Manus triggers in Zapier

2 events start a Zap when something happens in Manus, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Task Created

Instant trigger

In Zapier“Triggers when a Manus task is created.”

Starts your Zap each time a new task is created in the connected Manus account. It is your hook on the very start of the work, the point where a title, a visibility setting or a log entry is easiest to put in place.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
logging every task the account opens into a shared tracker, so the team sees what is in progress without asking around.
Watch out
as with any trigger, a Zap that writes back into the place this trigger watches can set itself off again, so test it on a single entry first.
2

Task Stopped

Instant trigger

In Zapier“Triggers when a Manus task completes, requests input, becomes pending, or encounters an error.”

Fires when a Manus task stops moving, for one of four reasons: it completed, it needs input from you, it became pending, or it ran into an error. That makes it the trigger for anything you want to happen after Manus is done.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
sending the result of a finished task to the person who asked for it, together with its direct link.
Watch out
four different reasons share this one trigger, so add a filter on the status the test returns if only completed tasks matter.
Actions

Manus actions in Zapier

Manus gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Continue Task

Action

In Zapier“Sends follow-up instructions to an existing Manus task.”

Sends a new turn of instructions to a task that already exists, with the extra context Manus needs to keep going.

When to use it
answering a task that stopped to request input, using what arrived in another app.
Watch out
Task ID and Follow-up Instructions are both required, and Remove All Connectors must stay off if you selected connectors in the same step.
2

Create Task

Action

In Zapier“Creates a Manus task from your instructions and returns its ID and direct URL.”

Opens a new Manus task from the instructions you map in, then hands back its ID and direct URL for the following steps.

When to use it
turning a request that lands in another app into work Manus starts on straight away.
Watch out
Allow Follow-up Questions lets Manus pause to ask you something. For a Zap nobody watches, leave it disabled.
3

Delete Task

Action

In Zapier“Permanently deletes a Manus task. This action cannot be undone.”

Removes one Manus task for good, picked from your recent tasks or by its ID.

When to use it
clearing out test tasks that a Zap created while you were building it.
Watch out
the deletion is permanent and cannot be undone, and agent tasks and subtasks cannot be deleted this way at all.
4

Get Task

Action

In Zapier“Retrieves a Manus task’s status, title, URL, sharing setting, and credit usage.”

Reads one task and returns its status, title, URL, sharing setting and credit usage, so later steps can work with them.

When to use it
after Task Stopped, to know how much credit a finished task used before you report on it.
Watch out
Zapier lists it with the actions, so each successful run counts as a task, and placed after another action it makes the Zap multi-step.
5

Update Task

Action

In Zapier“Updates a task’s title, sharing settings, or visibility in the Manus task list.”

Changes the title of a task, its sharing setting, or whether it shows in the Manus task list.

When to use it
renaming automated tasks so they sort cleanly, or pulling them out of the list once handled.
Watch out
leaving Show in Task List blank keeps the current setting. A hidden task still opens through its direct URL.
Searches

Manus search in Zapier

1 search step looks for data that already exists in Manus, so a later step can use it.

Searches sit at the bottom of the action-event list, under the SEARCH heading. Three settings decide what happens when the lookup does not return exactly one task.

1

Get Tasks

Search

In Zapier“Finds Manus tasks and optionally filters them by type, project, or agent.”

Looks up Manus tasks that already exist, and can narrow them by type, project or agent before handing them to the next step.

When to use it
finding the tasks of one project so a later step can update or report on them.
Watch out
a search makes the Zap multi-step, and whether it wants the exact value or something close is decided by Manus, so check at test.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and skips the steps that relied on it. Switched on, the Zap carries on with nothing.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Manus exposes no find-or-create variant on Zapier, so Get Tasks only ever looks things up.
  3. If multiple search results are found?
    Three ways out when several tasks match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When a Manus Zap breaks

Zapier attaches no help article to Manus, and no limit specific to the app is on record. What breaks is what breaks on any Zap.

Four cases are worth knowing before you publish. If one of them hits and the cause is not obvious, see our Zapier troubleshooting guide.

  • Old tasks are not picked up

    A Zap only reacts to what happens after you switch it on. Tasks that already existed in Manus never start it; moving that backlog is a separate job.

  • The Zap keeps setting itself off

    A Zap that writes into the place its own trigger watches can start itself again and burn through your tasks. Test any such Zap on a single entry first.

  • A sudden batch is held back

    When a trigger returns a huge batch at once, after a bulk import or a migration, Zapier's flood protection can hold those runs back.

  • A deletion that cannot be reversed

    Delete Task is permanent and refuses agent tasks and subtasks. Test it on a throwaway task, never on one that matters.
Need help

Need help automating Manus with Zapier?

A person reads every message.

FAQ

Manus Zapier integration: frequently asked questions

01Is the Manus Zapier integration free?
Yes, on Zapier's side. Manus is not a premium app, so the free plan accepts it with 100 tasks a month and as many Zaps as you like. The catch is the shape of those Zaps: the free plan stops at two steps, one trigger and one action. A Zap that adds Get Task after Create Task, a filter, or the Get Tasks search becomes multi-step, and that needs a paid plan. Count your steps before you build, not after.
02How many tasks does a Manus Zap use?
One per action that succeeds, per run. Task Created and Task Stopped cost nothing, and neither does Zapier waiting for them. A Zap that runs Create Task and then adds a spreadsheet row uses two tasks each time it fires. Get Task is listed as an action, so reading a task's status also counts once it works. An action that fails is not billed. To keep the count low, put any filter before the actions, so runs that do not matter stop early.
03Do Manus triggers in Zapier run in real time?
Yes. Both Manus triggers, Task Created and Task Stopped, are instant: Manus tells Zapier the moment the event happens, and the Zap starts right away whatever your plan. The interval grid of the plans only applies to polling triggers, and Manus has none on Zapier. In the editor, a Zap built on an instant trigger shows a lightning bolt. Nothing waits for a check. On a free plan, that is the main reason Manus Zaps feel fast: there is no 15-minute wait to plan around.
04What do you need to connect Manus to Zapier?
A Manus account, plus access to any task you did not create yourself and want the Zap to read or change. In Zapier, open Apps, click + Add connection, search for Manus, click Add connection, then sign in to Manus in the tab that opens and grant access. The connection is then reused by every Manus step. Keep at least one task in the account before testing actions, since the Task ID picker lists recent tasks.
05Can a Zap delete any Manus task?
No. Delete Task removes a task permanently, with no undo, and it cannot delete agent tasks or subtasks at all. For anything else, the Task ID field is required, picked from recent tasks or typed in. Since the deletion is final, build the Zap on a throwaway task, test it, and only then point it at real work. If what you want is to get automated tasks out of the way, Update Task can hide them from the task list instead.
06What if the Manus operation you need is missing?
Start from the eight visible ones: two triggers, five actions and one search. Many needs are a combination rather than a missing feature. Get Tasks finds the tasks of a project, and Update Task or Continue Task then works on each one found. Remember that each extra step makes the Zap multi-step. If no combination of these covers the need, Zapier cannot do it for Manus today, and another automation tool is worth checking.
07Zapier, Make or n8n for Manus?
It depends on three criteria, not on a winner. First, the operations: Zapier offers eight for Manus, so check that the other tool covers the ones your workflow uses. Second, the shape of the workflow: on Zapier, anything past one trigger and one action is a paid multi-step Zap. Third, volume: Zapier bills each successful action, so a busy flow with several actions per run adds up. Compare those three on your real case before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations