Manus: connected apps
Connects apps such as email, calendars and CRM so Manus can use their information and take available actions in a task.
Check which actions your connector supports, what it can access and what should need your approval.
Workflow Planner
Explore an example. Change a decision. See where people, software and AI fit together.
Press play or select a step to explore.
These are authored scenarios, not connected systems or measured results. Tool names show possible roles, not a recommended stack. Role and tool edits change labels; the two switches and sample situation change the walkthrough. Your edits stay in this tab until you leave or reset it.
Reference shelf
Explore how AI tools, automation and business software could support your workflow. Each link takes you to the provider’s guide.
Connects apps such as email, calendars and CRM so Manus can use their information and take available actions in a task.
Check which actions your connector supports, what it can access and what should need your approval.
Combines workflow steps with AI models, agents, tools and memory to connect work across different services.
Plan for failed steps, repeated runs and human checks before an action changes business records.
Makes Salesforce Flow automations available as actions an Agentforce agent can use.
Check your edition, permissions and which records each action is allowed to change.
Uses connectors to find information and take actions in services your team already uses.
Review the connected account's access and the actions you want a person to approve.
Brings information and supported actions from connected services into a ChatGPT conversation.
Available features depend on the app, plan and workspace settings. Check permissions before connecting business data.
Lets you visually connect models, data sources, agents and tools, then test the resulting flow.
A working demonstration still needs evaluation, access controls and someone responsible for maintaining it.
Defines billable outcomes, including confirmed and assumed resolutions.
A supplier’s billable outcome is not proof of your business result. Agree measurement, exclusions and human handover.
Documents agent instructions, knowledge and connected tools.
Check the available tools, permissions and licence in your own account.
Documents embedded interfaces that can extend CRM workflows.
Edition, permissions and platform limits still apply.
Documents agents with configured inputs and actions.
Check subscription access, credits, permissions and each action.
Documents automation actions inside its workflow tools.
Available actions depend on the account and subscription.
Documents connecting a generated application to external APIs.
An AI app builder does not take responsibility for access control or production support.
Explains the responsibilities shared by a cloud platform and its customer.
Application security, permissions and operating decisions remain work to assign.
Documents ways to connect an application to services.
Check exact operations, credentials, limits and failure handling.
Documents deployment and ownership considerations.
This is context for later investigation, not a hosting or tool recommendation.
Start with one piece of work: handling enquiries, onboarding a customer, approving an invoice or passing information between spreadsheets and other tools. Map the steps, who does them and what you want to improve.
Yes. Map how customer information moves through your team, what your current CRM handles and where people rely on spreadsheets or manual work. Use the CRM example to explore the planner, or start with your own workflow.
It helps you decide what you need before choosing a product. You can compare improving an existing tool, buying software, connecting tools or building something specific. The tool cards are starting points to explore; the planner does not rank products or choose one for you.
Yes. Different steps can use different approaches. You might keep customer records in your CRM, connect a spreadsheet and use AI to prepare a draft that a person checks. The planner lets you record that mix and who is responsible for each part.
The examples are interactive walkthroughs with fixed scenarios. Changing a situation or check shows a possible consequence; it does not run an agent or connect to a real system. Use an example as the starting point for a planning brief, or build your own through guided questions. Your written answers are not sent to an AI service.
Review the draft and download your brief. Walk through it with the people doing the work and whoever would build or configure it. Check the assumptions, agree one small test and decide what a better result would look like. The brief is a starting point for that conversation, not a finished technical specification.
Example edits stay in this tab and are lost when you leave or reload. In the custom planner, you can choose Save on this device to enable automatic saving of your planning brief in this browser. Anyone using the same browser may be able to see it. Clearing the device copy does not remove PDFs or other files you have downloaded.