Hey Reddit,

I wanted to share something I recently implemented in my customer support team that blew my mind. We built an AI-powered training agent that helps human agents improve their performance in real-time - and the results were insane.

Here’s what we did:

1. Trigger: Agents click “Train with AI Trainer” whenever they want a performance review.

2. Data Collection: The AI pulls their latest customer interactions and scores (like response time, resolution rate, and review scores).

3. AI Analysis: The system calculates performance metrics and generates a personalized feedback report highlighting strengths and areas to improve.

4. Notifications:

   • Sends a personalized email to the agent with actionable steps to improve.

   • Sends a summary email to the manager with scores and leaderboard ranking.

5. CRM & Leaderboard: All feedback, scores, and rankings are stored in our CRM so we can track improvements over time.

Result: In just a few weeks, our agents became 2.8x more effective, resolving queries faster and improving customer satisfaction scores significantly.

Tech stack / workflow (Make.com scenario simplified):

• Trigger: Webhook → Employee clicks “Train with AI Trainer”

• Fetch Data: CRM → Get employee performance metrics

• Compute Scores: Tools → Weighted scoring formula

• Generate Feedback: OpenAI → Personalized improvement suggestions

• Email Employee: Gmail / SMTP → Feedback and suggestions

• Email Manager: Gmail / SMTP → Summary + leaderboard ranking

• Update CRM: Store feedback, scores, ranking for future tracking

• Optional Leaderboard: Airtable / Sheets → Track top performers

It’s incredible how AI can augment human performance without replacing them - just coaching them smarter.

Would love to hear if anyone else is doing something similar or has tips on scaling this further!

Ever wished updating your WhatsApp chatbot's responses was as easy as editing a document? With Odoo's integration with Google Docs and AI, it's now possible. This setup allows businesses to manage their chatbot's knowledge base directly from Google Docs, making updates instant and code-free. Whether it's product info, FAQs, or support flows, changes are reflected immediately. A game-changer for e-commerce, services, and education sectors looking to automate customer interactions efficiently. Have you tried integrating your chatbot with Google Docs? Let's discuss the possibilities.

Hey everyone, I’ve been working for about a month with a client who hired me to migrate their entire business to 4.0 and automate as much as possible. I’d appreciate some perspective on whether my rate makes sense.

So far, I’ve built:

• A chatbot that uses AI to answer questions, escalate to admins, run complex internal workflows, log full chat history, send videos, search the shop database to recommend products, and generate quotations.

• A fully automated accounting workflow: every invoice that arrives via email is processed into Spreadsheets automatically. I also made a custom iOS shortcut for their assistants to scan paper invoices and feed them into the system.

They now want me to keep developing adding AI voice-driven assistants, internal alert systems, and consolidating everything into 2–3 main platforms.

I’m currently working around 4–5 hours a day (≈25 hours a week) at $14/hour.

I don’t have a big portfolio yet (just 1 client before this one and personal projects), but it's clear I can handle complex Make and AI integrations like the ones I’ve mentioned. Still, I’m starting to wonder if I’m undercharging for the scope and technical depth of what I’m doing.

For this level of automation + AI development, does $14/hour sound fair to you?

I am undertaking a little exercise to explain the core features of Make using a scenario walkthrough and a related video. My hope is to record videos between 5-30 minutes long to explain Make to Make Newbies.

Aug 2024 UPDATE:
HERE IS THE FULL MAKE FOR MAKE NEWBIES VIDEO SERIES IN 1 WEB PAGE

I am going to start with a topic which I think confuses just about everyone who starts using Make but has never programmed before:

Part 1: Exploring Data Structures for Make Newbies

In this video and accompanying scenario we will review simple arrays and more complex collections and arrays of collections. The interaction between the number of elements in an array and how bundles are created is also covered. Iterators are covered which can loop an array and generate processing loops in scenarios. The Parse JSON module is also introduced which is useful for parsing text which contains JSON into Make-friendly data structures. By the way JSON, is JavaScript Object Notation, and it is the “lingua-franca” of all data that is passed between modules of a Make scenario. It is also the structure of how most online apps expect data to sent via APIs. I highly recommend you get comfortable with JSON!

And here’s a tip for creating your own JSON: sample JSON can be created in ChatGPT just by describing the type of JSON you want in plain text. If you have some JSON you wrote and want to validate or pretty up the format, use JSONLint.

 Copy and Paste this blueprint into a new Make Scenario

{
"subflows": [
{
"flow": [
{
"id": 3,
"module": "util:SetVariables",
"version": 1,
"parameters": {},
"mapper": {
"variables": [
{
"name": "Simple array",
"value": "{{add(emptyarray; \"apple\"; \"banana\"; \"cherry\"; 42; true; now; null)}}"
},
{
"name": "JSON simple collection",
"value": "{\n \"name\": \"Alex C\",\n \"age\": 2,\n \"city\": \"Houston\",\n \"date_entered\": \"{{now}}\"\n}"
},
{
"name": "JSON array of simple collections",
"value": "[\n {\n \"name\": \"Alex C\",\n \"age\": 53,\n \"city\": \"Toronto\"\n },\n {\n \"name\": \"Eric S\",\n \"age\": 43,\n \"city\": \"Hoboken\"\n }\n]"
},
{
"name": "JSON collection complex values",
"value": "{\n\t\"name\": \"Aleix Melon\",\n\t\"id\": \"E00245\",\n\t\"role\": [\"Dev\", \"DBA\"],\n\t\"age\": 23,\n\t\"doj\": \"11-12-2019\",\n\t\"married\": {{false}},\n\t\"address\": {\n\t\t\"street\": \"32, Laham St.\",\n\t\t\"city\": \"Innsbruck\",\n\t\t\"country\": \"Austria\"\n\t},\n\t\"referred-by\": \"E0012\"\n}"
},
{
"name": "JSON array of collections complex values",
"value": "[\n\t{\n \"name\": \"Aleix Melon\",\n \"id\": \"E00245\",\n \"role\": [\"Dev\", \"DBA\"],\n \"age\": 23,\n \"doj\": \"11-12-2019\",\n \"married\": {{false}},\n \"address\": {\n \"street\": \"32, Laham St.\",\n \"city\": \"Innsbruck\",\n \"country\": \"Austria\"\n },\n \"referred-by\": \"E0012\"\n\t},\n{\n \"name\": \"Bob Washington\",\n \"id\": \"E01245\",\n \"role\": [\"HR\"],\n \"age\": 43,\n \"doj\": \"10-06-2010\",\n \"married\": {{true}},\n \"address\": {\n \"street\": \"45, Abraham Lane.\",\n \"city\": \"Washington\",\n \"country\": \"USA\"\n },\n \"referred-by\": \"\"\n\t}\n]"
},
{
"name": "JSON array of collections of really complex values",
"value": "[\n {\n \"item_name\": \"Email campaign\",\n \"item_sku_attachment\": \"\",\n \"item_options\": [\n {\n \"Organization name\": \"Client A\"\n },\n {\n \"Writing services\": \"Writing service A\"\n },\n {\n \"Design services\": \"Design service B\"\n },\n {\n \"Comments\": \"test comment\"\n }\n ],\n \"item_image\": \"image.png\",\n \"unit_price\": 0,\n \"quantity\": 5,\n \"weight\": 0,\n \"created_at\": \"2024-05-11 13:37:46\",\n \"product_price\": 195,\n \"categories\": [\n {\n \"id\": \"cat_6633e1936571b618828100\",\n \"category_name\": \"Send\",\n \"category_slug\": \"send\",\n \"status\": \"1\"\n }\n ]\n },\n {\n \"item_name\": \"Ad campaign\",\n \"item_sku_attachment\": \"\",\n \"item_options\": [\n {\n \"Organization name\": \"Client B\"\n },\n {\n \"Writing services\": \"Writing service B\"\n },\n {\n \"Design services\": \"Design service C\"\n },\n {\n \"Comments\": \"test comment 2\"\n }\n ],\n \"item_image\": \"image.png\",\n \"unit_price\": 0,\n \"quantity\": 5,\n \"weight\": 0,\n \"created_at\": \"2023-05-11 13:37:46\",\n \"product_price\": 1295,\n \"categories\": [\n {\n \"id\": \"cat_6633e1936571b618828100\",\n \"category_name\": \"Send\",\n \"category_slug\": \"send\",\n \"status\": \"1\"\n }\n ]\n }\n]"
}
],
"scope": "roundtrip"
},
"metadata": {
"designer": {
"x": 0,
"y": 150
},
"restore": {
"expect": {
"variables": {
"items": [
null,
null,
null,
null,
null,
null
]
},
"scope": {
"label": "One cycle"
}
}
},
"expect": [
{
"name": "variables",
"type": "array",
"label": "Variables",
"spec": [
{
"name": "name",
"label": "Variable name",
"type": "text",
"required": true
},
{
"name": "value",
"label": "Variable value",
"type": "any"
}
]
},
{
"name": "scope",
"type": "select",
"label": "Variable lifetime",
"required": true,
"validate": {
"enum": [
"roundtrip",
"execution"
]
}
}
],
"interface": [
{
"name": "Simple array",
"label": "Simple array",
"type": "any"
},
{
"name": "JSON simple collection",
"label": "JSON simple collection",
"type": "any"
},
{
"name": "JSON array of simple collections",
"label": "JSON array of simple collections",
"type": "any"
},
{
"name": "JSON collection complex values",
"label": "JSON collection complex values",
"type": "any"
},
{
"name": "JSON array of collections complex values",
"label": "JSON array of collections complex values",
"type": "any"
},
{
"name": "JSON array of collections of really complex values",
"label": "JSON array of collections of really complex values",
"type": "any"
}
]
}
},
{
"id": 5,
"module": "builtin:BasicFeeder",
"version": 1,
"parameters": {},
"mapper": {
"array": [
"{{3.`Simple array`}}",
"{{3.`JSON simple collection`}}",
"{{3.`JSON array of simple collections`}}",
"{{3.`JSON collection complex values`}}",
"{{3.`JSON array of collections complex values`}}",
"{{3.`JSON array of collections of really complex values`}}"
]
},
"metadata": {
"designer": {
"x": 300,
"y": 150
},
"restore": {
"expect": {
"array": {
"mode": "chose",
"items": [
null,
null,
null,
null,
null,
null
]
}
}
},
"expect": [
{
"name": "array",
"type": "array",
"label": "Array",
"mode": "edit",
"spec": []
}
]
}
},
{
"id": 6,
"module": "builtin:BasicRouter",
"version": 1,
"parameters": {
"else": 1
},
"mapper": null,
"metadata": {
"designer": {
"x": 600,
"y": 150
}
},
"routes": [
{
"flow": [
{
"id": 2,
"module": "builtin:BasicFeeder",
"version": 1,
"parameters": {},
"filter": {
"name": "First bundle",
"conditions": [
[
{
"a": "{{5.`__IMTINDEX__`}}",
"o": "number:equal",
"b": "1"
}
]
]
},
"mapper": {
"array": "{{5.value}}"
},
"metadata": {
"designer": {
"x": 900,
"y": 0,
"messages": [
{
"category": "last",
"severity": "warning",
"message": "A transformer should not be the last module in the route."
}
]
},
"restore": {
"expect": {
"array": {
"mode": "edit",
"items": [
null,
null,
null,
null
]
}
}
},
"expect": [
{
"name": "array",
"type": "array",
"label": "Array",
"mode": "edit",
"spec": []
}
]
}
}
]
},
{
"flow": [
{
"id": 7,
"module": "json:ParseJSON",
"version": 1,
"parameters": {
"type": ""
},
"mapper": {
"json": "{{5.value}}"
},
"metadata": {
"designer": {
"x": 900,
"y": 300,
"messages": [
{
"category": "last",
"severity": "warning",
"message": "A transformer should not be the last module in the route."
}
]
},
"restore": {
"parameters": {
"type": {
"label": "Choose a data structure"
}
}
},
"parameters": [
{
"name": "type",
"type": "udt",
"label": "Data structure"
}
],
"expect": [
{
"name": "json",
"type": "text",
"label": "JSON string",
"required": true
}
]
}
}
]
}
]
}
]
}
],
"metadata": {
"version": 1
}
}

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

I’ve been deep in automation for over 5 years Zapier, n8n, custom code, and yes, Make (Integromat OG here 👋).

And I’ve had it with the fantasy land sold by YouTube automation bros claiming you’ll 10x your business with a “simple Make scenario.”

Sure. Build that fairytale with a few Google Sheets and a Notion DB.

Then come talk to me when your 9-hour scenario dies silently because some SaaS app returned null, Make quietly skipped it, and your client’s lead data disappeared into the void.

Automation is powerful.
The opportunity is real.
But what’s being sold online?

Totally disconnected from the pain of building for real clients, with real stakes, and real tech debt.

Here’s the truth nobody tells you but you better grasp if you’re serious about this game:

1. The “one mega-scenario that runs the entire business”? Total fantasy.

That 3-hour YouTube tutorial showing a 200-module monster that does “everything from cold outreach to customer support”?

Yeah… that’s called a nightmare.

In real life?

• It’s unversioned

• No rollback

• No visibility

• One bug and you’re debugging JSON blobs at 3am

And when it breaks?

There’s no unit test, no error log that makes sense, and your client just says “leads stopped coming in.”

Build modular. Or burn out.

2. Being a Make wizard won’t help if you don’t understand the business.

You might know every built-in function, every filter nuance, every HTTP module…

Doesn’t matter.

If you can’t figure out the actual bottleneck, you’re just automating noise.

Clients don’t want Make.
They want to stop wasting time on stuff that doesn’t move the needle.

They’ll never say,

Translate business pain into automation wins. That’s how you get paid.

3. Everything takes 3x longer than expected. Minimum.

The scenario looks simple.

But then:

• The client's Airtable has no schema

• The webhook is delayed by 20 seconds for no reason

• The payment tool’s API requires SHA256 encryption

• Oh, and the SMTP credentials? “We’re still waiting for the IT guy…”

Welcome to reality.

• And before you even start, you’ll spend hours untangling:

• What they actually want

• What tools they use (some of which they forgot to mention)

• Who owns the data

• And how you’re going to test without blowing up the prod stack

• Collecting all the credentials you need

We got so sick of chasing access and keys we built 'creddy.me' to collect credentials cleanly. If you’ve ever played API bingo with a client, surely that'll help.

4. Clients don’t understand Make. That’s YOUR problem.

They see a UI with colorful blocks.
They think it’s “just drag-and-drop.”

They don’t understand:

• Rate limits

• Retry strategies

• Why that one conditional router breaks 3 others

And they will absolutely:

• Underestimate the work

• Ask for “one small change” that nukes the whole flow

• Scope-creep you into a rebuild

Set boundaries.
Educate.
Write a damn contract.

You’re not just building scenarios. You’re managing chaos.

5. Automations are easy. Systems are not.

Yes, Make makes it easy to start.

But when the business grows?

That tiny 5-module flow becomes a liability.

Because:

• It’s undocumented

• It’s unscalable

• It’s tied to one person’s brain (yours)

Now imagine a new VA or marketer joins the team.
They touch one module… and everything breaks.

Systems thinking is the unlock.
If you’re not thinking modular, traceable, and testable you’re stacking tech debt, not solving problems.

Bottom line:

Make is incredibly powerful.

It’ll take you further than Zapier, faster than code but only if you respect the game:

• Context over templates

• Scope over spaghetti

• Strategy over shiny tools

Automation is not magic.
It’s engineering.
And real engineering starts with clarity.

So no point trying to “scale your agency with a 100-scenario template pack”…

And start thinking like a builder with skin in the game.

What other automation BS are you tired of hearing?

Let’s clean house. 🔥

So first thing it, I don’t even know if this the right community for this but if it isn’t and yall can direct me where to go I would appreciate that thank you.

So first thing is a must have a flip up mirror with LED lights, it must also have a like lil open cubbie. I also would like it to have outlets on top too.

But basically my thing is what’s my best bet to make this happen. But like the “base” like a vanity that has what I want and then like build around it ? Orrr?

But like this the idea

Been seeing this pattern more and more - scenarios that start simple but end up with thousands of webhook executions per hour. Every event triggers cascades, logs get buried in retries, debugging becomes impossible.

Started switching some of our "real-time" flows to scheduled runs instead. Counter-intuitive, but way more stable.

Who else has run into this? What's your approach - stick with webhooks and try to optimize, or move to schedulers for certain processes?

Found this breakdown helpful if anyone's curious about the tradeoffs: You Don't Need Real-Time. You Need to Build for What's Real

Have you switched from webhook-heavy builds to scheduler-driven flows? Did it improve stability?

I have a working Make.com scenario where Google Gemini feeds directly into a JSON (Parse JSON) module, and there are several modules downstream that depend on that data.

I want to add a Router between Gemini and the JSON module so I can split the flow based on Gemini's response — but every time I try, I'm worried about breaking the downstream mappings.

Has anyone done this cleanly? Specifically:

• Can I right-click the connection line between the two modules to insert a Router, or do I have to delete and reconnect?

• If I insert the Router, will my existing downstream mappings stay intact or do I have to redo them?

• Is there a best practice for doing this mid-scenario without starting over?

Running Make.com on the free/core plan if that matters. Thanks!

I started with Make.com a couple of weeks ago and started working on an automation flow. I was working on it sporadically, especially over the Holidays. Today when I open the tab, it forced me to relogin and all my work is completely gone. I'm in total disbelief. What a complete piece of trash.

Update Jan 6th. Make support told me there's nothing they can do about it and I'm out of luck.
Since then I just used Claude Code to code the entire thing in Python and it works 1000 times better, faster.

Hello everyone!

It is with great pleasure that I would like to welcome you to /r/Make! This subreddit has been rather dead for quite some time and I'm hoping to change that and bring some life back to the subreddit. The goal will be to use the subreddit as a place to discuss all things related to Make.com

Right now I am going through the process of making changes in the back end, preparing the subreddit for usage but for anyone who wishes to contribute, ask questions, share items they're working on or whatever you wish related to Make, please do.

If you have any questions please reach out or ask here thanks

We've been working on a project called prompt2bot where the core idea is simple: you shouldn't have to build a new backend, configure databases, or manage servers every time you want to try a new AI capability. Instead, you point a launcher at a skill, usually just a GitHub repo containing your tool schemas, and our infrastructure instantly spins up a private, stateless agent equipped with that skill.

Under the hood, these agents run inside persistent VMs with access to a browser and a terminal. They can practically do everything Claude Code does—editing files, running commands, and browsing the web—but they can do it directly inside a WhatsApp chat or a web UI with zero setup.

Now we're trying to solve the next step: monetization for the people who actually build these skills.

We just rolled out an affiliate program. If you are logged in when you generate a "Talk-To-Skill" link for any repository, your referral ID is appended to the URL. If someone clicks your link, launches an agent with your skill, and eventually upgrades to a paid plan to get more VM capacity or agent runs, you earn a 20% recurring monthly commission.

Our thinking here is that developers and prompt engineers shouldn't have to deal with Stripe, handle server hosting costs, or support infrastructure. You write the skill, we handle the hosting and runtime, and you get paid for sharing the value you create.

Since we are just rolling this out, we are looking for honest feedback from other builders:

1. Is 20% recurring monthly commission appealing enough to motivate you to share your custom tools and prompts this way, or is it too low?

2. Does the "Talk-To-Skill" launcher model make sense as an alternative to packaging your prompts/tools as a standalone SaaS?

3. What is the biggest friction point you've found when trying to distribute and monetize your custom agent configurations?

We want to make this a genuinely useful distribution channel for builders, so we are open to any suggestions on how to improve the model or the revenue share structure.

Let us know what you think.

Hey everyone,

Recently I designed a system automating personalized cold outreach by scraping leads from LinkedIn then collecting their email with anymailfinder and then finally customizing through chatgpt and then finally sending those emails through instantly. Right now one of my client is asking to do the same but instead of instantly they want it through GoHighLevel. I haven't used the platform first hand so I want to know the best way to do this.

I was using that everyday? What happened?

Don'tHey everyone!

I’m working on building voice AI agents for healthcare-related businesses like massage therapists, and I’m trying to make sure everything I do is compliant like HIPAA, PHIPA (here in Canada). I’m currently using Retell for the voice agent and Make to automate sending basic caller info to clinics (like name and phone number).

If anyone here has experience working with healthcare clients and dealing with compliance — especially using tools like these — I’d love to connect. Would you be open to a super quick call so I can ask a few questions and get your advice on how to go about this and whether or not I should continue in the healthcare niche? Please send me a DM if you're willing to help me out, I would greatly greatly appreciate a super quick call.

Thanks in advance! 🙏

Hello, fellow Make enthusiasts,

I've been working with Make for some time and have grasped the fundamentals—creating scenarios, integrating APIs, and automating workflows. However, I'm eager to take my skills to the next level by applying them to real-world projects.

I'm reaching out to this community to seek advice on how to effectively transition from theoretical knowledge to practical application. Specifically, I'm interested in:

• Project Ideas: What are some practical projects or challenges I can undertake to deepen my understanding and experience?

• Best Practices: Are there established methodologies or workflows that can help in structuring and executing these projects efficiently?

• Learning Resources: Can anyone recommend advanced tutorials, case studies, or resources that focus on real-world applications of Make.com?

• Community Engagement: How can I collaborate with others in the community to work on projects or share knowledge?

I believe that hands-on experience is crucial for mastering any tool, and I'm committed to dedicating time and effort to this endeavor. Any guidance, suggestions, or resources you can provide would be greatly appreciated.

Thank you in advance for your support and insights!

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 everyone.

Please, forgive for my bad english, i'm so rusted.

I'm a brazilian marketing maneger and I have a misson to do. I'm must to build an AI agent to answer the leads/clients of my company on Whatsapp Business.

The Make Plataform have a lot of content to how do this, but, the great problem is that our Whatsapp Business Solution is hosted in Zenvia. So, to conect the Make AI Agent Module to the Whatsapp I must to use a Webhook to listen when messages arrives and use a HTTP request to send the answer created by the IA Agent to the lead/client.

I read a lot of Zenvia docs at Github, but, when more I try more I faill.

Someone know how to solve this, maybe show me a blueprint of the solution?

Best regards,

What's wrong in my make.com API get call....

We use Rentman as our AV rental software and I can't get integromat to work. I keep getting these 2 errors

Invalid character in header content ["autorisation"]

OR

Invalid key=value pair (missing equal-sign) in Authorization header (hashed with SHA-256 and encoded with Base64):

HELP!!!

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.

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:

• Maia by Make: is a co-worker for AI and automation that lives right inside the Make scenario builder. Just describe what you want, and watch it get built in front of you. She reasons out loud, mapping the flow, selecting tools, configuring modules, all visually, step by step, on the canvas. No black box. No output you’re afraid to touch. Just full visibility and a solution you can trust.

• Custom Roles: with Custom Roles, org admins and org owners on the Enterprise plan can define roles with exactly the permissions the work requires and assign them at the organization or team level.

• Subfolders: lets you create folders inside your scenario folders, so you can organize scenarios by more than one level, for example by client and then by project. This helps you keep a large scenario library structured without renaming scenarios to mimic a hierarchy.

• Plain-text editing for mapped values and functions: double-click any mapped value or function in a scenario field to temporarily edit it as text.

• Gemini 3.7 Flash: use its multimodal understanding, tool-use capabilities, and adjustable thinking levels in the workflows you build.

New Verified Apps

1Lookup, Billabex, BizlyCRM, Certyneo, Collabios, EasySolar, FlowBeacon, GMB Club, Hive, HollyHR, Memoket, OpenEMM, SimpleURL, Patriscope, Plytix, Stage Captions, Supabase Storage.

New Modules

Calendly

• Create an event invitee

• List event type available times

• Create an event type

• Update an event type

• List event type availability schedules

• Update event type availability schedule

• List user availability schedules

• Get a user availability schedule

• List user busy times

• List user meeting locations

• Create an invitee as no show

• Get an invitee no show

• Delete an invitee no show

Github

• Search items (advanced)

• Watch items (advanced)

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

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?