Plan and build better workflows with Maia by Make, upgraded

Good co-workers remember how you like to work, show you the plan before they act, and help when something breaks. Maia, our co-worker that’s already part of how many teams build automations and AI agents on Make, just learned how to do all three in our latest upgrade! 

Since we launched Maia, she has been co-creating with you directly in Make’s visual Scenario Builder. Every step happens on the scenario, so you can learn as you go and see exactly how your scenario comes together.

Building with Maia has always been straightforward: you describe the outcome, and Maia maps the scenario, picks the modules, and asks questions along the way. This update gives her more context to work with and gives you more say in what changes. Here’s what’s new:

• Plan mode: Review the full approach before anything changes in the scenario.
• Memory: Carry your preferences from one scenario to the next, with you in control of what Maia remembers.
• Attach image: Drop in a sketch, whiteboard snapshot, or screenshot, and Maia builds from it.
• Resolve error: Go from a failed run to a fix you review before saving.
• Copy response: Share Maia’s diagnoses with your team.

Review the plan before you change the scenario

Maia now has two modes for building scenarios, and each fits a different stage of the work: 

Build is the default. Maia asks questions one at a time and builds after you approve each step. 

Plan asks all its questions up front and starts building once you approve the plan.

Choose Plan first when you want to see the full approach before anything changes in the scenario. Maia lays out the modules, assumptions, and approach, and nothing is built until you approve. Plan also checks connections, app capabilities, and plan-tier access on the go, as to avoid errors partway through the build.

Select Build when you want to shape the scenario together with Maia, one decision at a time.

Both modes work for new scenarios and existing ones. You can always open a scenario and Maia can suggest improvements, which you review before anything changes.

Give Maia the context it needs

Memory eliminates the hard reset every time you build a new scenario with Maia. Rather than starting from zero and re-explaining the apps you connect or avoid, or how you’d like her to respond, Maia meets you where you are without the need for external apps. Your context seamlessly moves with you from one chat to the next, learning and updating naturally as you chat. You stay in complete control and can manually add, tweak, or erase memories whenever you want.

The Attach Image feature brings that same effortless intuition to your visual ideas. When you already have a sketch, whiteboard snapshot, or screenshot of a workflow (like an approval flow that splits into two paths, for example) you can drop it straight into Maia. Maia interprets the layout directly from the image and starts building the workflow right from your visual blueprint, sparing you the headache of spelling out every split, loop, and condition by hand.

Together, the two capabilities make building faster, with less to explain. Upload a diagram to map out the structure of the workflow you want to build, and your saved preferences handle your app choices. That gives Maia everything she needs to deliver the build that you’re after. 

Learn how to manage Maia memories and add images to a Maia chat.

Resolve a failed run from its run data

When a scenario fails, you no longer have to play detective in the logs. You can troubleshoot straight from the run itself. Maia digs into the run data to see what each module processed, pinpoint where the flow broke down, and check if the error has surfaced before. Simply click Resolve error, and Maia turns that diagnostic context into a working fix, revising the scenario on the spot. You always review the update before committing it, giving you a fast resolution without needing to diagnose the root cause on your own.

Learn how to resolve errors with Maia. 

Share a response with your team

Sharing context with your team is just as effortless. Click Copy response to lift Maia’s diagnosis in one clean move, then paste it directly in markdown into Slack, shared documentation, or another workspace chat. Teammates get the full diagnostic breakdown instantly, sparing you from having to summarize or rewrite the findings yourself. 

Help shape where Maia goes next

Everything above happens in Scenario Builder today, and that’s only the start. We're building Maia to bring her capabilities across the Make platform to help you not just with how you build, but with how you get work done. Stay tuned for that update.

To make sure she learns what matters most, tell us: what should Maia learn next? What's the friction you'd love Maia to help you solve? You can share your views through our Ideas Exchange, and receive support on your petitions from others.

Try it on your next scenario

Choose Plan to review the approach before anything changes in your scenario, or attach an image of a workflow you’ve had in mind but haven’t managed to put into words.

Frequently Asked Questions

Q.1 What's the difference between Build and Plan mode?

Build asks questions one at a time and builds after each step is approved. Plan asks all its questions up front, presents the approach, and starts building once you approve the plan. Plan also checks connections, app capabilities, and plan-tier access before anything is built.

Q.2 Can Maia remember how I prefer to work?

Yes. Memory stores private, user-controlled preferences about apps and accounts, response detail, and language. You can save up to 50 memories, with up to 200 characters each. Memory is saved per user, per team, and teammates never see your memories. You can add, edit, delete, clear, or turn off memories at any time. 

Q.3 What images can I add to a Maia chat?

You can upload, drag and drop, or paste up to three images per session in PNG, JPEG, or WebP format, up to 1.5 MB each. Maia reads each image once, and Make doesn't store the image.

Q.4 How does Maia use run data, and can it apply a fix?

Maia uses scenario run data to identify what passed through a module, where a run stopped, and whether an issue recurs. Resolve error gives you a direct path from that run data to a scenario fix, with the change ready for your review.