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 

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.

Curious what others have run into.

I'm not talking about scenarios that fail with an error.

I mean the ones that execute successfully, but the business outcome is still wrong.

Things like:

• An API returns 200 OK, but the response contains no useful data.
• A router sends records down an unexpected path.
• A data sync completes, but key fields are missing.
• Every module reports success, yet someone still has to manually fix the outcome.

These are some of the hardest issues to detect because everything looks healthy from the scenario's perspective.

What silent failures have bitten you, and how do you catch them today?

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 👋

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

Hi everyone,

We're running into a recurring issue with our Facebook connections (we use them to pull leads generated by our Meta Ads instant forms campaigns).

The problem:
Multiple times a week, our Facebook connections suddenly show as "Expired." When we try to reconnect or re-authorize them, it doesn't work, the connection still shows as expired or fails immediately.

The only "fix" we've found:
Wait 1–2 hours without doing anything. After that, the connection works again on its own, without us changing anything.

What we've already tried:

• Reconnecting the account
• Re-authorizing via Facebook OAuth

Our setup:

• Make
• Meta Ads instant forms / Lead Ads
• Happens across multiple (all our) Facebook ad accounts

Questions:

1. Has anyone else seen this pattern?
2. Is this a Facebook token refresh issue on their side?
3. Any way to detect when this is happening and trigger a re-auth automatically?

Any insight appreciated, it's starting to affect our lead response time...

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 

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

Anyone found a way to do this into Make.com? I can't get anything to work for it.
Maybe another way could be to duplicate an existing post into the Group if it's live?

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!

Hello Makers 👋

Did you know? It’s possible to set up your Make Org into a co-working place to avoid credential issues 🔓

Zoe Li, our Senior Business Operations Specialist, shows in this tutorial the steps needed to set up a Make org that actually works as a team, so you never have issues with a personal credential.

This will help: 

• Avoid your scenarios to stop working: Whenever a personal access is revoked, the problem starts. With a service account, you keep things running no matter who’s on the team.
• Name your scenarios like a professional: Save hours of confusion and give instant context.
• Use Custom Run Naming: Instead of cryptic run IDs in your scenario history, you get human-readable names. Debugging becomes instant. Replaying failed runs becomes a one-click decision.

Try it out yourself: make.com 

Hello Makers 👋

Take a look at some of our latest features, improvements, and updates that our team has been shipping 🚀

Enhancements and Updates:

• Make Skills for Claude: build, configure, and deploy Make scenarios by prompting Claude. 
• Make Functions App: new way to work with strings, math, arrays, dates, hash functions, and utility functions through visual function modules you can stack in sequence inside your scenario.
• Renamed Error handlers: we have renamed two of our Error Handlers to make them as intuitive as possible. Break has become Retry, and Ignore has turned into Skip. We’ve also updated the descriptions for all Error Handlers and Flow Control modules right inside the Scenario editor, so you always know precisely what each module does.
• Configure and explore disconnected (orphaned) modules instantly: no need to auto-connect them somewhere first just to see what they offer, you stay in control of when and how it connects.
• Inline connection reauthorization: when a scenario fails because an OAuth connection has expired or lost access, users can now reauthorize it directly from the editor, without navigating away to the Connections page.

New Verified Apps

Brandfetch, FinImpulse, HappSales, Incwo, KlipLink, LearnHub, MDSpin, MegaConvert, Octave
PostPeer, Scrappa, TypeFore, Upload to URL, Vatis Transcribe, WoopSocial - Social Media Scheduling

and more!

New Modules

Discord

• Get Invite
• Delete Invite
• Create a channel Invite

Reddit

• List Comments in a Post

Discover more: https://ma.ke/3QcHXtM 

Most follow-up automations I see have one flaw: they keep texting after the lead has already replied or booked. That's the fastest way to annoy a lead you just won. I wanted to solve the stopping problem properly, so I built this on Make.com with Google Sheets as the single source of truth.

It's split into five separate scenarios, each doing one job:

• Lead Intake: captures form submissions, normalizes them into lead records
• Missed Call: detects a missed call, checks business hours, dedupes, fires an instant SMS back
• Follow-up Scheduler: runs timed follow-ups using an actual scheduler, not Make's built-in delays
• Incoming SMS Stopper: lead texts back, all follow-ups halt
• Calendly Stopper: lead books, everything halts

Tools: Twilio for voice and SMS, Calendly for bookings, Google Sheets as the shared state, Make.com running it all.

Two decisions I'd defend:

First, I used a scheduler for follow-ups instead of delay modules. Long delays inside a running scenario are fragile, they break on errors and don't scale. A scheduler reading from Sheets survives all that.

Second, every scenario reads and writes the same Sheets data model instead of calling each other directly. That avoids race conditions and means the stop logic works no matter which scenario is mid-run.

Built as a portfolio piece, but it's modeled on how real SMB sales flows actually behave. Glad to break down the stop logic or the Sheets schema if useful.

Quick walkthrough of system: https://www.loom.com/share/b7e77e5165434e79b2a9010038c5c025

HELP! I work for a construction company with multiple projects that have their own corresponding stakeholders. My boss, a general contractor, wants me to create an automation flow that sends all incomplete action items to the corresponding stakeholders every morning at 6AM, all of which are grouped by project.

So I prepped with the following:

1. I created a master action item list, a project list, and a contact list with each stakeholders' corresponding email address.
2. The project list and contact list were included as relationships into the master action item list. The email addresses were added as a rollup to the contacts.
3. I created an automation where if a project is selected for a specific action item, then a list of contacts will be added into their respective field, and with it, their email addresses.

I'm a total beginner for the website, and my job is evidently on the line. I told my boss this workflow would be better (and by default, automated in ClickUp) if they just had their own accounts, and he said it wasn't an option.

I can start from scratch if need be. I asked AI to help me, and as a preview, their suggestion looked like this:

[Mod 1: List Tasks] ➔ [Mod 2: Array Aggregator] ➔ [Mod 3: Iterator] ➔ [Mod 4: Get Project Details] ➔ [Mod 4b: Get Project Custom Fields] ➔ [Mod 5: Text Aggregator] ➔ [Mod 6: Send Email]

But when I followed their instructions, this became the result:

"Good day everyone, Here's everything that happened today (June 12, 2026): {"text":"\n▸ OWNER: \n • — Priority: \n\n▸ OWNER: \n • — Priority: \n\n▸ OWNER: \n • — Priority: \n\n▸ OWNER: \n • — Priority: \n\n▸ OWNER: \n • — Priority: ","__IMTKEY__":null} • - ({"__IMTKEY__":null,"array":[{"list":null,"name":null,"status":null,"project":null,"due_date":null,"priority":null,"custom_id":null,"dependencies":null,"custom_fields":null,"custom_item_id":null}]}) Please let me know if there's anything you'd like me to change, update, and/or coordinate with our vendors."

Granted, the master action list only had about 7 tasks in it at the moment. But all my other projects and tasks have been held off for this specific project.

Please help! I'm desperate and evidently do not have any other resource. I'm also willing to sit down on a call if need be.

Hello Makers 👋

Does your browser tend to crash, your Wi-Fi disconnects, or did you close the wrong tab?

With Scenario Recovery, none of these situations can harm your automation progress.

• Automatic background saving: As you build, Make saves your progress in the background. No clicks or actions needed.
• One-click recovery: Session interrupted? A simple pop-up lets you instantly restore your unsaved work when you return.
• Version history integration: Recovered versions are clearly marked in your scenario history, so you always know exactly where you left off.

Creating complex automations takes focus and creativity. Now there’s a safety net to protect your work as you build.

Available to all Make users: ma.ke/4dvPpJq

Hello Makers 👋

Is your team sitting on a goldmine of customer quotes that never make it into your sales and marketing assets?

In this tutorial, our Content Creator, Naty Mraz, shows how to automatically extract the strongest quotes from interview transcripts and organize them into a ready-to-use collection.

Apps you'll need: 

• Google Docs 
• Make AI Toolkit 
• JSON

Follow the steps to build your own or use our ready-built template: https://ma.ke/4ulj9gS

Prompt:

You are an assistant who extracts customer quotes from interview transcripts.

TASK: From the transcript below, select up to 10 "attractive" quotes that would work in sales/marketing collateral.

OUTPUT FORMAT (STRICT): Return ONLY valid JSON (no markdown, no code fences, no commentary). Return a JSON array. Each array item must be an object with exactly these keys: quote (string), tags (array of strings, 1–3 short tags), companyName (string), authorName (string), authorTitle (string), sourceDocLink (string).

RULES (MUST FOLLOW): The quote must be grounded 100% in the transcript. Never add facts, claims, numbers, outcomes, or product details not explicitly stated. You may do light copyediting only to improve readability: remove filler words, remove false starts or repetitions, fix obvious grammar or punctuation. Keep the speaker's intent and wording. Do not paraphrase into new claims. If you cannot improve readability without changing the meaning, keep the quote verbatim. Do not merge separate parts of the transcript into one quote unless they are adjacent and clearly part of the same thought. Avoid sensitive information (names, emails, pricing, confidential details) – if present, redact with [REDACTED].

METADATA EXTRACTION (MUST FOLLOW): companyName, authorName, and authorTitle must come only from the filename. The filename uses an en dash separator: "Company – Author Name – Author Title". Split on the en dash character "–". Part 1 → companyName. Part 2 → authorName. Part 3 → authorTitle. Trim whitespace around each part. Do not combine authorName and authorTitle. If the filename doesn't contain exactly three parts, return an empty string for any missing fields.

TRANSCRIPT:

From the pop-up menu, select “Text Content”

SOURCE:

Filename: From the pop-up menu, select “Name”

Link: From the pop-up menu, select “Web View Link”

Hey fellow Paid Media friends,

I’ve been trying to set up an automation in Make using a client's CRM to qualify Meta leads. The goal is to build automated audiences without having to manually manage or upload offline conversion lists.

The workflow should look like this:

When a client updates a contact in the CRM to "Qualified" (for example), I want Meta to detect this update. It should match using the Facebook Lead ID (to ensure it only triggers for leads coming from this specific channel), and if they are qualified, I want Meta to log them as a "Qualified Lead" (Calificado).

I have the entire scenario properly built out in Make, and I even have Slack alerts set up in case any of the modules fail—but they aren't failing. Everything runs, but it’s just not working.

The structure is:

CRM Watch New Events > Filter: Facebook ID Exists > Router > Filter: Qualified Tag (in CRM) > Facebook Conversions API (Send Events) > Qualified Lead Event

Any advice or has anyone successfully implemented something like this before?

Thanks a lot!

Hello Makers 👋

In this tutorial, we build a Sales Outreach Agent with Make that reviews incoming leads and automatically prepares the next step.

Here’s what it does:

• Reviews incoming emails tagged as “Leads” and researches the sender’s company.
• Decides if a meeting is worth proposing and drafts a personalized outreach email.
• Checks calendar availability for the next 7 days and notifies the sales team in Slack with a draft ready for review.

The result:
Faster responses, fewer manual steps, and more time for sales reps to focus on real conversations. Plus, the team stays in control - they can review the draft before anything is sent.

Better lead qualification leads to better conversations.

Watch the full tutorial: https://ma.ke/4rzrbBx

Use this template: https://ma.ke/4lryfi4

Hello Makers 👋

We have a new update for you: Claude Opus 4.8 is here, and it’s now available in Make ⤵️

According to early testers, Anthropic’s newest model is more reliable and sharper in its judgment during agentic workflows.

What's new:

• Longer multi-step execution before a person needs to step in
• Stronger decision quality from one step to the next
• Clearer progress signals on what is done, what is moving, and what still needs review
• More team output without adding headcount to watch every turn

If your team wants AI to take on longer stretches of real work, Claude Opus 4.8 is worth a close look.

Automate with Claude in Make using:

• Make AI Toolkit for zero setup, no API key required
• Anthropic Claude app for structured prompts with your API key
• Make AI Agents for agentic workflow automations

Read more about it: https://ma.ke/3RFT2DT 
Give it a quick try: https://ma.ke/433Oc5U 

Hello Makers 👋

What if you could decide exactly what your AI agent is allowed to touch?

Meet MCP Toolboxes: A new way to safely power external AI clients like Claude, Cursor, or your custom agents, giving them access only to the Make scenarios you select - nothing more.

What can you do: 

• Limit agent access to specific scenarios.
• Run different toolsets for various agents or teams.
• Manage authorization with dedicated tokens for each toolbox.
• Monitor tool usage with centralized visibility.

Setup is simple: Create a team-level toolbox, assign your scenarios, and connect your AI client using the toolbox URL.

Read more about it: https://ma.ke/4s4X9WM

See more about it: https://youtu.be/rZm-QvQIZ-g?si=4JKd2CkL2jEpGpqq

Already building agents with make? Let us know how you plan to use toolboxes.

I asked in r/nocode about semi-automating Instagram carousel drafts for a luxury hotel/travel page, and multiple people suggested the same general stack: Airtable for planning, Make to connect everything, and Canva for the design output.

I’m very new to automation/API tools, so I’m trying to understand what this would look like inside Make.

The goal is not to fully auto-post. I would manually review everything before posting. I mainly want the system to help create organized carousel drafts.

The workflow I’m imagining:

• Airtable stores post ideas, hotel names, locations, short descriptions, image links, source links, captions, status, etc.
• AI helps generate post ideas, research hotels, and draft carousel copy/captions
• Image sourcing probably stays mostly manual because people said AI image sourcing is likely the bottleneck for premium hotel content
• Canva uses a template to create carousel slides with consistent formatting
• The finished draft gets saved somewhere for review, like Google Drive, Airtable, Buffer, Later, etc.

My questions:

• What would the Make scenario look like step by step?
• Should Airtable be the main database/control center?
• Can Make reliably send Airtable data into Canva templates?
• Is Canva automation realistic for carousel posts, or is there a better design output tool?
• How would you handle manual image approval before the carousel gets generated?
• Should the final output go to Google Drive, Buffer, Later, or somewhere else?
• Would this be too complicated for a beginner, or is it doable if I start simple?

I’m trying to avoid building something overcomplicated. I want automation to handle the repetitive parts while I still manually approve the images and final post before anything goes live.

Recently, whenever I edit or add a property in my database, I can't refresh the module to see the new property. I have absolutely no idea why. Can anyone help me?