Introducing Automations: Put Repetitive Work on Autopilot
You are halfway through a meeting when a new lead lands in HubSpot. By the time you get back to your desk, Manus has researched the company, built a deck around what the buyer cares about, and sent the follow-up email.
Setting that up used to take real work. You would write a script in Python or JavaScript, or open a tool like Zapier or Make and draw the flow yourself, connecting each app and deciding what happens at every step.
Automations lets you skip the building. You tell Manus when the work should start and what the finished result should be, and Manus works out how to get there.
Describe the Outcome Instead of Mapping Every Step
Most multi-step automations are built like a flowchart. You place a block that watches for the new lead, add a filter after it, and then build separate blocks for the research, the deck, the email, and a record of what was sent. Every handoff is yours to design, and every change sends you back into the chart.
With Automations, a single prompt can describe the whole routine.
When a new lead is added to HubSpot, research their company, create a short deck tailored to their role and industry, and email it to them from my account.
Manus turns that request into a working automation. It may write a script behind the scenes to run it, but you never need to write or read that script yourself. You review the timing, conditions, actions, and connected accounts Manus set up, then turn it on.
Three Ways to Start an Automation
Every automation needs a starting point, and Automations offers three.
•Schedule runs at a time you choose, such as every weekday at 8:00 AM. Scheduled tasks you already use in Manus continue to run here.
•Trigger starts when something happens in a connected app, such as an invoice arriving in Gmail. You can add conditions so only the right events count, like a specific sender or a refund over $100.
•Advanced automation is for routines that combine several sources, conditions, and actions. You describe the routine in your own words, and Manus configures it for you.
Advanced automation is where a condition can get as specific as your situation. A traveler can ask Manus to watch fares from San Francisco to Tokyo and have the agent call them when the price drops below a set amount.
Turn One Event into a Multi-Step Task
The event that starts an automation can be small. What follows can be a full piece of work that draws on everything Manus already does.
Take a job search. You can ask Manus to watch a job board for product manager roles in California. When a matching role appears, Manus compares it with your experience, tailors your résumé to the description, saves it as a PDF, and emails it to you. It then texts you from its agent phone so you see the match right away.
A flow builder would need a separate block and settings for each of those steps, while Manus treats the whole sequence as one task.
Let Manus Make Decisions Between Steps
Many workflows need a judgment call partway through, which a fixed rule handles poorly. An inbox is a good example, since customer requests, invoices, and promotions all arrive in the same place.
You can ask Manus to read each new email, decide what kind of message it is, and act on it. Customer requests get a summary and a draft reply, invoices go into your expense spreadsheet with the attachment saved to Google Drive, and promotions are left alone.
Manus reads the content and follows the path you described for that type of message, so you don't have to write a rule for each one.
Connect the Apps Where Your Work Starts and Ends
Connect an app once, and its events can start an automation. The same connectors let Manus deliver the result where it belongs, whether that is a Slack channel, a Notion page, or a draft in Gmail.
Sources such as GitHub and Shopify send events the moment they happen. Other apps are checked at regular intervals, so a trigger from those sources may start a few minutes after the event. For services that are not listed, a Webhook can start an automation from any tool that can send one.
Build on Earlier Runs Without Repeating Work
An automation that checks for new information every few minutes has to know what it has already handled. Without that, the same invoice gets logged twice and the same job gets sent to you again.
You can choose to have every run continue in the same task, keeping earlier messages, files, and results together, or start a new task each time when every run should stand on its own. Running in the same task gives Manus that history. You can ask it to compare a webpage with the version it saw last time and act only when the content changes in a way you care about, or to skip any listing it has already sent you.
You can also attach an automation to a 
Manus project, so every run follows that project's instructions and skills.
Check and Control Every Automation Run
Automations run while you are doing something else, so you need a clear record of what they did. Every run appears in Updates with its time, status, and a short summary of the result. Runs that did not meet your conditions show up as well, so you can tell the difference between an automation that failed and one that had nothing to act on.
Before you rely on a new automation, use Test run to see a real result. For anything that sends or publishes, such as the follow-up email to a new lead, keep Approval required on so Manus waits for your confirmation. If a run fails, open it, ask Manus what went wrong, and let it help fix the setup. You can pause, edit, or delete any automation when your work changes.
What You Can Build with Automations
•Outcome-based setup: Describe the result in a prompt and Manus builds the workflow, so you do not have to map each step yourself.
•Three ways to start: Begin from a schedule, an event in a connected app, or a routine described in plain language.
•Multi-step tasks: Turn one event into research, a finished deliverable, and delivery, such as turning a new product post from a company you follow on X into a blog draft.
•Judgment between steps: Let Manus read a message, record, or page and choose the right next action.
•Agent follow-through: Have Manus create a deck, tailor a résumé, send an email, text you, or call you when a price crosses your threshold.
•Run history and context: Continue each run in the same task so Manus can compare against earlier results and avoid repeat work.
•Review and control: Test before going live, require approval for anything that sends, and check every run in Updates.
Build Multi-Step Automations Without Writing the Script Yourself
•Automate a process that once needed a developer or a long afternoon in a flow builder.
•Spend less attention on work that follows the same pattern every time.
•Handle cases a fixed rule would get wrong, since Manus reads the content before it acts.
•Keep control over anything that leaves your account through test runs and approvals.
How to Create an Automation
1.Click Automations in the left sidebar, then click Create. You can also start from Build on the Manus home page.
2.Choose Schedule, Trigger, or Advanced automation.
3.Set when it should run: a time, an event from a connected app, or a plain-language description of the routine.
4.Add conditions so only the right events qualify, such as a specific sender or an amount over $100.
5.Describe the outcome you want and where the result should go.
6.Use Test run to check a real result, review the setup, and turn it on.
For ideas to start from, browse the example automations on the Automations page. The Automations guide covers how to write conditions that hold up in practice.
Availability
Automations is available now in Manus. Schedules, triggers, and Advanced automations live together in one place, and your existing scheduled tasks now appear there and keep running on their current schedule. Advanced automation is currently in Beta. The trigger sources you can choose depend on the apps you have connected.
Common Questions About Automations
Q: Do I need to write a script or build a flowchart?A: No. Describe when the work should start and what the result should be. Manus builds the workflow, and you review it before turning it on.
Q: How is an automation different from a scheduled task?A: A scheduled task starts at a set time. An automation can also start when something happens in a connected app, or from a routine you describe that combines several sources and conditions. Your existing scheduled tasks now live in Automations.
Q: Will the same email or listing be handled more than once?A: Have the automation run in the same task so Manus keeps its earlier results, and tell it to skip anything it has already handled. Check Updates after the first few runs to confirm it behaves the way you expect.
Q: Can I review results before anything is sent?A: Yes. Use Test run to see a real result first, and keep Approval required on for anything that sends or publishes.
Q: Why didn't my trigger start right away?A: Some apps send events instantly, while others are checked at intervals. Also confirm that the connector is authorized and that the event meets every condition you set.
What Automations Means for Working with Manus
Until now, most work in Manus began when you opened a task and typed a request. With Automations, Manus can start the work as soon as your conditions are met and bring back a finished result for you to review.
