Run Make scenario from AI chat and use the result
Say what you need. Manus picks the matching scenario, fills in its inputs, runs it and works with whatever the scenario returns.
Connect your own Make (make.com) account and Manus can see the scenarios you’ve made available as tools, run them when you ask, pass in the inputs and keep working with the results. On paid Make plans, it can also view and change your scenarios, connections, webhooks and data stores. Every app you’ve connected in Make can be put to work through your scenarios.
Ask in plain words. Through Make.com MCP, Manus picks the matching scenario, fills in its inputs, runs it and tells you what came back.
Say what you need. Manus picks the matching scenario, fills in its inputs, runs it and works with whatever the scenario returns.
Make waits up to 25 seconds for a run. Longer scenarios keep going in Make for up to 40 minutes. On paid Make plans, with read access to scenarios selected when you connect, Manus uses the execution ID to fetch the outputs when they’re done.
Set them up once in Make, and your Make.com AI workflows get the right data in and a clear result back.
Make offers active scenarios with On demand scheduling as tools. That includes scenarios you started from Make scenario templates.
Scenario inputs are what Manus fills in, and the Return output module sends the results back.
Make shows your scenario description to Manus as the tool’s description, so say what it does and when to use it.
On paid Make plans, Manus can also look after your Make.com AI automation setup. Before it changes anything, ask it to list the changes for your OK.
See which scenarios are active, how each one is scheduled and which ones Manus can run right now.
Ask for the webhook a scenario listens on, so you can paste it into a form or another app.
Find records with missing or wrong values and see each change before anything is saved.
Let Manus call the scenario that pulls your data, then write up what it found.
A Manus scheduled task can run your scenario at the time you choose, then turn what it returns into a short report.
See how scheduled tasks workManus works as the Make.com MCP client, so there’s no server URL or token to set up. Make is already in Manus Connectors, and you approve access on Make’s own screen.
In Manus, open Connectors and select Make.
Choose the organization and the scopes Manus can use, then select Allow.
Name a scenario or describe the job in plain words.
Yes. Manus connects to the Make MCP server, Make’s official MCP (Model Context Protocol) server at mcp.make.com. Make is already in Manus Connectors, so there’s nothing to install or host.
Open Connectors in Manus, select Make and sign in. On Make’s consent screen, choose the organization and the scopes Manus can use, then select Allow. Your Make password is never shared with Manus.
Active scenarios with On demand scheduling in the Make organization you choose, which is what Make’s Run your scenarios scope covers. Give each one scenario inputs and outputs, so Manus knows what to send and what comes back. To limit access further, Make suggests team-specific user accounts on its Teams plan or higher.
Not to run scenarios: Make’s scenario run tools work on every plan. Viewing and changing scenarios, connections, webhooks, data stores and teams, and fetching the outputs of runs that take longer than 25 seconds, use management scopes, which need a paid Make plan. Make’s pricing page has the current plan details.
Make waits up to 25 seconds for a scenario run to return. If it takes longer, the scenario keeps running in Make for up to 40 minutes and Manus gets an execution ID. Fetching the outputs once the run finishes needs read access to scenarios, a management scope on paid Make plans, so select it when you connect.
Yes, through the Manus API rather than this connector. To trigger Manus from Make webhook scenarios or any other scenario, add an HTTP → Make a request step that sends a request with your API key to create a task. The connector on this page works the other way: Manus calls your Make scenarios.
Yes, and it can go both ways. The Make connector lets Manus find and run your scenarios from a chat. The Manus API lets a scenario start a Manus task, and Manus API webhooks can send the result to a URL you choose when the task finishes.
No. Make AI Agents are agents you build and run inside Make, and they can use scenarios as tools too. Here, Manus is the agent: it calls the scenarios you’ve made available through the Make MCP server, as one step in a task it works on for you.
No. Make’s server also accepts an MCP token, which goes into a server URL with your zone or into a request header. In Manus, you sign in with your Make account and approve access on Make’s screen, so there’s nothing to copy or paste.
No. Claude and ChatGPT have their own ways to add Make, so a “Make.com MCP Claude” or “Make.com MCP ChatGPT” guide covers setup in those apps. In Manus, Make is already in Connectors: sign in once, ask in a chat and the task runs in the cloud.
Start with the scenario’s History tab in Make, which lists each run with its status and duration. You can paste what you find into a Manus chat and ask for help working out the cause.
Yes. Open Connectors in Manus, select Make and choose Disconnect.