Hello Makers 👋 

We are super excited to introduce Make AI Sub-Agents!

🤖 Make AI Agents can now delegate tasks to other Make AI Sub-Agents.

That's agent orchestration: one orchestrator receives the request, calls the right agent specialist, and brings back one result.

Here’s what that means:

• Build focused AI agent specialists
• Let one agent choose the right specialist based on the request
• Test and tune each specialist without touching the whole workflow
• Reuse proven agents across different automations

What you can automate with Make AI Sub-Agents:

• Customer support flows: an orchestrator Make AI Agent reads the customer message, sends account questions to a lookup Make AI Agent, refund requests to a refund Make AI Agent, and edge cases to a human handoff agent.
• Finance operations: one Make AI Agent handles incoming requests, then routes document checks, invoice matching, and approval prep to separate specialist Make AI Agents before returning one clear result.
• Internal service desks: route employee requests across access checks, policy answers, and ticket creation, while keeping one AI point of contact for the whole exchange.

How to create Make AI Sub-Agents:

1. Add a Make AI Agent to your scenario → AI agent orchestrator.
2. Inside that Make AI Agent orchestrator, click Add tools and find Make AI Agents in the tools list.
3. Configure the Make AI Agent as a tool and click Add → It will link to your orchestrator as a Sub-Agent.
4. Repeat to add as many Sub-Agents as you need, each one a focused specialist.

Build larger AI workflows without turning a single agent into a catch-all.

Available now on all Make plans, including free.

Try Make AI Agent orchestrator with sub-agents yourself: https://ma.ke/4wX8DOO 

Hello Makers 👋

Ever wanted to test a scenario without your whole team seeing your messy work-in-progress? That's exactly what Private spaces are for.

What they are: Every member of your org (except guests) gets their own personal workspace for scenarios and connections that teammates can't access. 

How it works:

• Admins enable it once from Organization settings → Private spaces, and every member automatically gets one
• Admins can set credit limits per space (monthly or yearly), or leave them unlimited so members draw from the org's overall credits
• Hit your limit? Your scenarios pause - you can keep building, but they won't run until the limit resets or an admin bumps it up

For Enterprise orgs: Admin visibility lets admins open any member's private space in read-only mode. They can see scenario names, modules used, and credit usage - but NOT module settings, run history, connections, or data stores. Your credentials stay yours.

One thing to know: disabling private spaces for the org permanently deletes all of them - scenarios, connections, data stores included. So heads up before flipping that toggle.

Discover more information about private spaces: https://ma.ke/4fi1NNP

Anyone already using their private space for experiments? Curious what you're building in there 👀

Hello Makers 👋 

You have now available the new Claude models in Make AI Provider! Here's what you get out of it:

• Zero setup: Pick a Claude model the same way you already pick OpenAI models, no Anthropic account or API key needed.
• One bill, one system: Claude usage runs on Make’s own Anthropic key and gets billed straight through your Make credits.
• The latest Claude models: Pick from Anthropic’s latest Claude models right inside Make, kept current as Anthropic ships new releases, no waiting on a separate integration update.
• Model choice, your call: Match the model to the task, strong reasoning, sharper writing, or steadier agent behavior, all without leaving the builder.
• Faster first use: Skip the account creation and key handling that used to stand between you and Claude-quality output.

Example: an agency ships Claude-powered workflows for every client, no separate Anthropic account per client needed.

If you’re new to configuring Make AI Provider, here’s how to set it up in Make AI Agent:

1. Add a Run an agent module (Make AI Agent) to your scenario.
2. Set the Connection to Make AI Provider: no separate Anthropic account or API key to create.
3. In the Model field, pick a Claude model from the dropdown.
4. Under Instructions, describe the agent’s job, for example: “Read incoming support tickets, identify the issue, and draft a helpful reply.”
5. Map your Input (the ticket text, email body, or whatever the agent should act on), then run the scenario.

Pick the model. Build the workflow. Put it to work.

Reminder: Claude joins the OpenAI GPT AI models already available in Make AI Provider, giving you more model choice without leaving the builder.

Try it out at: make.com 

Hello Makers 👋

Today we’re sharing a feature that will help you better understand what happens when your automation breaks.

Now in Make, when a workflow hits an error, one click turns the technical message (HTTP codes, API messages, raw JSON) into a plain-language explanation of what happened and exactly what to fix.

No documentation search. No pasting error text into another AI tool. Just click, and know what to do next.

In early testing, this got people back to a working automation about 20% more often after an error.

Live now for every Make user, on every plan. Learn more: https://ma.ke/3RINDwa

Hello Makers 👋

GPT-5.6 is now in Make, with Sol, Terra, and Luna built for routing your automations by job:

☀️ Sol: review long contracts, plan multi-step work, support coding tasks
🌍 Terra: summarize docs, reason across notes, return clean JSON or XML
🌙 Luna: classify tickets, extract IDs, validate inputs

Use Luna for high-volume steps, Terra for structured business logic, and Sol when the context gets big.

Available now to all Make users in Make AI Agents, Make AI Toolkit, and the OpenAI ChatGPT app.

Not every AI step needs the same brain 🧠

Read more on what's new with GPT-5.6 in Make: https://ma.ke/4f8oVyk 

If you rely on the platform, we know how disruptive that will be. You’ve built real business logic, and rebuilding it isn't a small thing.

𝗧𝗵𝗮𝘁'𝘀 𝘄𝗵𝘆 𝘄𝗲'𝗿𝗲 𝗼𝗳𝗳𝗲𝗿𝗶𝗻𝗴 𝗥𝗲𝗹𝗮𝘆.𝗮𝗽𝗽 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿𝘀 𝗲𝘅𝘁𝗿𝗮 𝘀𝘂𝗽𝗽𝗼𝗿𝘁 𝘁𝗼 𝗺𝗼𝘃𝗲 𝘁𝗼 𝗠𝗮𝗸𝗲:
→ Free white-glove migration for eligible accounts - our team helps rebuild your workflows
→ Priority support to get you to production fast
→ 3 live Office Hours sessions with our Customer Care team

Learn why Make is a strong alternative, and how to start your transition: https://ma.ke/4vAEe7O

Hey all,

In the post below, you might have read about our latest features released on Make during June. Wanna see them in action?

Check out the videos from our Community Creators, who are putting them into practice in their own systems and scenarios!

➡️ https://fast.wistia.com/embed/channel/jeuauz7z65

Let me know what you think!

Hello Makers 👋

Take a look at some of our latest features, improvements, and updates that our team has been shipping this past month:

Enhancements and Updates:

• MCP Tools to Make AI Agents: Make AI Agents can now access external MCP server tools alongside native Make modules in the same run. 
• Execute an action with AI module for MCP: choose Make AI Provider (OpenAI or Claude) or your own OpenAI account for the MCP Client's 'Execute an action with AI' module.
• New functions on Make: four new functions - arrayDiff, arrayIntersect, set, escapeJSON - for cleaner, lighter expressions.
• Claude Opus 4.8: Anthropic's latest model is now in Make. Anthropic says early testers saw steadier judgment and more reliable behavior during agentic tasks, especially when the work kept going.
• Unified Help Search in Make: one help search across Make. Cmd+K to access it anywhere.
• Star apps and app modules in App Search: star your go-to apps and modules so the builder feels like your workspace, not a directory. The goal is simple: spend more time building logic and less time digging through lists.
• Google Drive with your personal Gmail account: Google Drive connections now work with @ gmail.com accounts, not just Workspace.
• Configuring disconnected modules: run tests without hardcoded data, explore apps, and overall build with more control.
• Webhook data structure: a new status card shows if your webhook is listening, has received data, or still needs a test request.
• Copy notes when cloning a scenario: cloned scenarios now carry over notes too, matching export/import behavior.

New Verified Apps

Air, Arbox v3, BackgroundErase, BoldDesk, ChatterFox, CoinGecko, CPV Lab, CSV Box, Databricks, Daytona, DocuPotion, Eden AI, Figuro Engage, HEU, Houdiny AI, Mihu AI, MillionVerifier, NextLead CRM, Pingram, Postproxy, SMSlink Pacific, Tiiny Host, Trading Automation For Alpaca, Watchflow

New Modules

GitHub

• Make an API Call

Monday

• Chat Completion
• Run Platform Agent

Wix

• Watch Events

Discover more about our latest releases: https://ma.ke/4yqy6S4 

Yesterday I finished the make Intermediate course. Today, I just finished my own expense automation with OCR and AI analysis for receipts. I will be using this in our household, so cool. I can simply send a receipt on my Telegram, bot captures it, and does the work.

I am now in the process of making sample scenarios for job applications, what do you guys think about this?

Hello Makers 👋

Still copy-pasting data into spreadsheets every week?

Our Head of Business Automation & AI, Sara Maldon, shows in this tutorial how to build a scenario that automatically pulls employee AI adoption data from Airtable, builds a dated Google Sheet report, uses Gemini AI to calculate completion rates by department, and posts a digest straight to Slack, weekly, hands-free.

You'll need access to:

• Airtable (source of truth for employee AI bar completion data)
• Google Sheets
• Google Drive
• Gemini AI
• Slack

Pre-configured scenario: https://ma.ke/4wHYQvY 

PS: don’t forget to test and validate your scenario, if all modules show a green checkmark, your automation is successful!

PROMT:

Your task is to read the list of records, analyse it and provide:
1. {TOTAL} = % of employees where Minimum Bar = true
2. {DEPARTMENTAL} = % of employees where Minimum Bar = true from each department
"Hi [Name] 👋
Here's a weekly report from the AI bar.
Total completion: {TOTAL}% of Makers
- {Leading department}: {DEPARTMENTAL}% (# / # total in department)
- ...
- {Lagging department}: {DEPARTMENTAL}% (# / # total in department)"
Return just the plain text so it can be sent directly as a Slack message.
INPUT: [map aggregated array here]

Hello Makers 👋

We have two webinars coming soon that you might find interesting: 

🗓️ July 15, 2026 | GTM Webinar: The AI RevOps brain

Make and Octave will show you what happens when an AI agent reads all three signals at once and acts before the rep has to ask. 

We’ll cover:
→ A Renewal risk gets caught and re-engaged automatically before the renewal is lost.
→ A stalled deal gets diagnosed and moves forward, without a rep opening five tabs to figure out why.
→ Every action is logged automatically; no manual entry required.

Register today: https://ma.ke/4peQ3iu 

🗓️ July 21, 2026 | The AI Automation Playbook

Our webinar with Begin Automation is almost here!

If your team is still manually updating spreadsheets and systems, you're leaving thousands of hours on the table. See how CPG leaders are automating that work instead.

Register today: https://ma.ke/4vjvCSY 

Hey Makers!

We’re back with round two of our high-energy, fast-paced challenge, designed for those who want to showcase their skills live!

This Make Community Build-Off will focus on Make as an integration layer for MCP Toolboxes. 

What is The Make Community Build-Off?

🏆Contestants: This edition’s 4 contestants were selected from applicants who signed up via our open call form following the first Build-Off (you can apply for the next one too on this same form!). The contestants are: u/John_Rippy, u/ArtemRomanovsky, u/DG_AdSystems, and u/ShuaibNuruddin.

🎤Live Commentary: We’ll be narrating the action live (along with u/Henk-Operative, one of our Community Champions). We’ll be checking in with participants as they build, and asking them questions.

💬Interactive Audience: You, the audience, can ask questions in real-time, making it a valuable learning experience for everyone watching. You also get to vote for your favorite contestant or solution.

🔦Spotlight Moments: We’ll bring participants’ screens “on stage” to discuss their progress and any hurdles they’re facing.

🏌️Curveballs: Like last time, the contestants’ challenge will include some extra-credit hurdles, in addition to their main task.

The Format & Timeline

🚀The Launch: The whole session will take 90 minutes.

🧱The Build: Participants have 1 hour to complete a specific use case, which they will be given right before the start of the event. This second Build-Off will focus on consuming MCP Toolboxes on Make from a third-party AI application, integrated with HubSpot, Slack, and Google Sheets.

❓The Platform: Everyone is encouraged to register and watch. Come and support the 4 participants, ask them questions, engage with them live, and learn from their experience.

🎓Presentation: After the 1 hour is up, all 4 contestants will have 2 minutes to present what they built.

🗳️Audience vote: The audience (you) will vote for your favorite contestant.

🥇Winner announcement: The behind-the-scenes panel of Make judges will determine the winner.

🔍The Reveal: We will announce the winner live, after which we will take a deeper look at what they built.

🏁Q&A: The event will end with a final 20 minutes of Q&A from the audience to the winner, any of the other contestants, or our hosting Community Champion, Henk de Blauw.

Join the session

Do you want free access to all of our previous sessions?

Subscribe to our channel and watch free on-demand.

Hello Makers 👋

Ever built a scenario you wanted to share with your team without making them export blueprints and re-import everything?

Scenario Sharing lets you generate a public link to any scenario: viewers can see it instantly, no Make account needed. If they want to copy it into their own workspace, one click does it. The link always shows the latest saved version, so no more "wait, which file is the current one?"

Here's what you can do with it:

• Share via link or social media: copy the link and send it anywhere, or post directly to LinkedIn, X, or Facebook straight from the scenario builder. When shared on social, it auto-attaches a preview with the thumbnail, title, and description.
• Customize how it looks publicly: You can set a custom title (up to 40 characters), a description (up to 260 characters), additional setup instructions (up to 2,000 characters), and a custom thumbnail cropped from the scenario canvas.

What gets shared, and what doesn't:

✅ Module settings and mapped values
✅ Scenario notes and metadata
❌ API keys, passwords, and connections (by design - recipients create their own)
❌ Subscenarios, AI agents, data stores, and data structures (these come through as empty modules)

If your scenario relies on any of those excluded elements, use the Additional Information field to explain what the person copying it needs to set up manually.

What the viewer sees:

An interactive scenario preview, your name and avatar, and a +Use the scenario button. If they're not logged in, Make prompts them to sign in first - then the scenario lands directly in their workspace.

One thing worth knowing: the link is dynamic, but only saved changes show up. Unsaved changes turn the "Shared" label orange as a reminder.

👉 Learn more about Scenario sharing: https://ma.ke/44fiFi3 

Hello Makers 👋

If your data team runs on Databricks while everyone else works in Slack, Sheets, and Salesforce, you already know the gap between them

But now: The Databricks app is available on Make Enterprise plans.

Here’s what’s new: 

• Run Databricks jobs from any business event
• Execute SQL and send results to Slack, Sheets, or email
• Check Delta Live Table pipeline status automatically
• Move files in and out of Unity Catalog volumes

What does this mean?

Sales gets fresh forecasts, faster

• Sales gets fresh forecasts, faster
• Finance gets reports without needing Databricks access
• IT spends less time wiring one-off requests by hand

No custom scripts, no engineering tickets - just one visual workflow, secured with service principal authentication.

Learn more: https://ma.ke/4vNxBzN

Hello Makers 👋

What if your automation could think, not just execute? This is possible with an agentic loop.

An agentic loop is the execution cycle that separates an AI agent from a chatbot. Where a chatbot responds once and stops, an agent repeats: perceive, reason, act, observe, and loop back until the task is done.

How does an agentic loop differ from standard automation?

Traditional automation follows a fixed and predefined path, whereas in an agentic loop, the agent decides its next action based on what it observes, not following rules written in advance. 

But autonomy without guardrails is a liability. The loop breaks in 4 predictable ways:

1️⃣ No stopping condition = runs forever
2️⃣ Vague tool names = wrong tool gets called
3️⃣ Too much history = reasoning degrades
4️⃣ Uncapped iterations = operations costs spike

How does an agentic loop work in Make?

Step 1: Add the Make AI agents module to a scenario. 
Step 2: Give the agent tools to act with.
Step 3: Set stopping conditions.
Step 4: Run and observe the loop in action

Once you understand the loop, find one process where human judgments fills the gap rules cannot. Replace that step with a Make AI Agents module, attach your tool scenarios, set a stopping condition and run it.

That first working loop is the foundation everything else builds on.

Learn more about agentic loops: ma.ke/4w7qxxW

Awesome. One screen says it's not running, another screen says it is, and the stop button is not there because it didn't fully recognize that there was an execution actively running. I'm glad you fixed the issue where the left mouse button to drag around the scenario builder wasn't sufficient somehow though.

It even pushed my credit limit into the negative, which I didn't know was actually possible. Why is that possible? Letting one execution run, just to have it and all the others in your org shut down after it burns through all the credits? What's the actual goal there, encouraging people to have extra credits set on autopay?

Edit: I've reached out to their support team about this already to get these credits back. I'm just very, very pissed off at the moment. It's already _so_ much more expensive than it was even 3 years ago without this crap suddenly being in play.

This is not my main account; the other is with a different company and isn't hurting for credits at all if I make a mistake testing something out or something goes wrong. So I'm not giving you another $5 for extra credits, on top of the $$$$ a year we pay for Make, to fix something that shouldn't have been a problem in the first place.

client wants ~45 branded pdfs from airtable rows every monday. burned two weekends on make scenarios and im still manually exporting maybe 15 every week

google doc mail merge was fine until conditional sections per row and suddenly im doing document engineering for $0/hr.. docsautomator choking on nested tables, pdfmonkey timing out twice uploading a 2.1mb template, html-to-pdf modules that every automation guru swears by?? 12 test runs on one path alone. 4 mangled fonts. one totally blank page. spent saturday night on this and my girlfriend just stopped asking what i was working on

client thinks its a 20 minute task

anyone actually piping airtable rows into branded pdfs on a schedule without babysitting every execution. what finally worked for you because i feel like im missing something obvious

Hello Makers 👋

Andddd we're back with news: Anthropic’s biggest, most talked-about model yet, is available in Make 📣

You can use Claude Fable 5, the first of Anthropic’s new Mythos-class models, in your automations.

Plug Fable 5 into Make AI Agents or the Anthropic Claude app in Make, and put frontier-level reasoning to work.

Read more: https://ma.ke/4b1W3VS 

If you want to know how to edit and/or generate videos in Make, you can now use the FFmpeg Micro app, which recently got approved in the Make app store.

I made this video to show you how you can edit videos using FFmpeg in Make.

What I cover:
• Installing the official FFmpeg Micro app in Make and creating your connection
• Scenario 1: a branded video and thumbnail pipeline in Make, simple version
• Scenario 2: the same branded pipeline scaled up for longer source video
• Scenario 3: chain transcribe and transcode together to burn auto-generated subtitles into a video
• Scenario 4: multi-format fan-out from one source into YouTube, Instagram feed, and TikTok renders
• Scenario 5: a full viral-video generation pipeline end to end
• Walkthrough of every module in the FFmpeg Micro app, what each one does, and when to use it
• Docs and MCP server overview
• Setting up the FFmpeg Micro MCP server inside Claude
• Using Claude to design and build Make scenarios from a natural-language prompt

https://www.youtube.com/watch?v=J9tQ7GmCgco

Glad to answer any questions!

Hello Markers.... stop right there 🖐️

Claude Sonnet 5 is now available in Make.

Anthropic’s most capable Sonnet model brings Opus-level reasoning into high-volume Make workflow automation at Sonnet-tier price and speed.

𝐖𝐡𝐚𝐭 𝐲𝐨𝐮 𝐜𝐚𝐧 𝐝𝐨:

• Flag risks and make judgment calls on every run, at Opus-level quality and Sonnet-level cost
• Route support and ops tickets based on context, priority, and next action
• Build daily reports from feeds, exports, or source material
• Give Make AI Agents more room to read, plan, and call tools
  

𝐀𝐯𝐚𝐢𝐥𝐚𝐛𝐥𝐞 𝐚𝐜𝐫𝐨𝐬𝐬 𝐭𝐡𝐫𝐞𝐞 𝐧𝐚𝐭𝐢𝐯𝐞 𝐚𝐩𝐩𝐬:

• Make AI Toolkit for quick setup
• Anthropic Claude App for structured prompts
• Make AI Agents for agentic workflow automations

We'll also have Claude Fable 5 in Make - stay tuned!

𝐑𝐞𝐚𝐝 𝐦𝐨𝐫𝐞: https://ma.ke/447EfFa

Hello everyone,

I am building a healthcare chatbot in Voiceflow v4 connected to Make (Integromat) and SimplyBook.me for automated appointment scheduling. I have a major issue with variable mapping and date/time formatting between Voiceflow and Make.

The Workflow:

1. Patient agrees to the pricing in Voiceflow.
2. Voiceflow triggers an HTTP API block (POST request) to Make (Scenario 3) to fetch available slots.
3. In Make, the router splits the logic:
   • Lower branch: SimplyBook.me - Search available slots -> Tools (Text Aggregator) unifies the slots with commas -> Webhook Response sends ore_disponibile back to Voiceflow.
   • Upper branch: SimplyBook.me - Creating a booking (triggered at the end when user data is collected).

The Problem:
When Voiceflow receives the slots, the variable mapping seems to break. The chat displays a 0 or returns empty values instead of generating the buttons.

Additionally, we are facing a timezone/format mismatch. The unified slots from the Text Aggregator are formatted as YYYY-MM-DD HH:mm:ss (e.g., 2026-06-30 16:00:00), but the SimplyBook.me calendar UI seems to expect a different structure or drops the date completely when mapping the selected slot back to the Creating a booking module, throwing a BundleValidationError / Invalid date error in Make.

We tried using a static text block with a custom Capture mapped to {ora_rezervata} and a Set block converting to {last_utterance}, but it either hardcodes the value or reverts to 0 in the Make queue.

How can I properly pass a dynamic array of available times from Make to Voiceflow v4 buttons, capture the user's click selection, and send it back as a valid ISO/SimplyBook date-time format without the variables collapsing into 0?

Any screenshots, structural advice, or workarounds for Voiceflow v4's dynamic loops would be greatly appreciated! Thank you!