TL;DR: Make.com News, November 2026: AI Agents, Credit Math and Smarter Automation for Founders
This Make.com news, November, 2026 update shows you how to run AI agent workflows on Make without letting the credit meter drain your budget. Make, formerly Integromat, now positions itself as an AI and agentic workflow platform. Every step you run costs one credit. Violetta Bonenkamp (Mean CEO), founder of CADChain and Fe/male Switch, breaks down what this means for your wallet.
- Credit math decides your bill. The free plan gives you 1,000 credits a month. A five-step lead flow handling 200 leads uses all of it. Paid plans start at $12/month.
- Filter early and poll less. A filter placed right after the trigger cut one polling scenario from 14,400 to about 4,080 credits, roughly 70% less. Webhooks beat constant polling.
- AI agents need a human checkpoint. Make connects to 350+ AI apps and runs JavaScript or Python. Add an approval step before AI output reaches customers, investors or your bank account.
- Choose by fit, not app count. Make gives deeper branching and visual control. Zapier wins on quick linear setups, and Lindy suits inbox-style AI assistants. Check that your 6, 12 daily tools have deep connectors.
Have a technical cofounder? The Make vs n8n guide compares managed and self-hosted costs. The October Make.com update tracks how AI-heavy scenarios push credit use up.
Your next move is small. List five repetitive tasks and map one on paper. Then multiply its steps by monthly runs and build it on the free plan this week.
Check out other fresh startup news and trends that you might like:
This edition of Make.com news for November 2026 covers a quiet shift that every founder paying for automation should notice: Make now positions itself as an AI and agentic workflow platform, and every step you build runs on a credit meter. I am Violetta Bonenkamp, better known as Mean CEO. I run CADChain, a deeptech company for CAD and IP protection, and Fe/male Switch, a startup game and online incubator built entirely on no-code tooling. My team and I live inside automation tools every single day. So this article is my opinionated breakdown of where Make stands right now, what the numbers mean for your budget, and how to avoid the traps I see founders fall into.
A quick note on naming, because “make” is also a verb and that confuses search engines and humans alike. In this article, Make (or Make.com) refers to the visual workflow automation platform formerly called Integromat. It lets you connect apps like Gmail, Slack, Google Sheets and your CRM (Customer Relationship Management software) and run automated workflows without writing code. If you have seen old tutorials mentioning Integromat, they describe the same product before the rebrand.
Let’s break it down.
What is the state of Make.com in November 2026?
Here is the snapshot I would hand to any founder asking me over coffee in Amsterdam whether Make is still worth their time. I pulled these facts from public company records, 2026 pricing guides, reviews and tutorials, and I cross-checked them where the sources disagree.
- Company identity: Make operates under the legal name Celonis s.r.o., headquartered in Prague, Czechia. Its official company description now reads as “AI workflow automation software and tools that allows users to visually build, scale, and automate AI and agentic workflows.”
- Audience size: Make’s LinkedIn page sits at roughly 114,391 followers, a solid signal of a large professional community.
- Free plan: 1,000 credits per month, good for testing and learning.
- Entry paid plan: starts at $12/month, according to Zapier’s 2026 pricing analysis.
- Higher plans: a Teams plan for shared scenarios with roles and permissions, and an Enterprise plan with SSO (Single Sign-On), audit logs and stronger security controls.
- AI features: AI agents, an AI toolkit and connections to over 350 AI apps.
- Developer escape hatch: the Make Code app runs JavaScript or Python inside scenarios.
- App library: anywhere from 1,000+ to 3,000+ connectable apps, depending on which guide you read (more on that discrepancy below).
If you want the full beginner walkthrough of the terminology, the team at Cloudwards keeps a beginner’s guide to using Make.com in 2026 updated, and it explains scenarios and modules clearly.
What do the Make.com terms mean?
Make has its own vocabulary, and new users stumble over it. Here is the short glossary I give my Fe/male Switch players when they build their first automation.
- Scenario: a complete automated workflow. Think of it as one “recipe” from trigger to final action.
- Module: a single step inside a scenario, such as “watch new form submissions” or “create a row in Google Sheets.”
- Trigger: the event that starts the scenario, like a new email, a webhook call or a schedule.
- Router: a module that splits one flow into several branches.
- Filter: a rule that lets data pass only when a condition is met (for example, “deal value above €5,000”).
- Credit (formerly called operation): the billing unit. Each trigger, filter, action or other step consumes one credit when it runs.
- Agentic workflow: a workflow where an AI agent makes some decisions inside the process, such as classifying a lead or drafting a reply, instead of following only fixed rules.
How did Make go from Integromat to an AI agent platform?
The story has three acts, and each act changes how you should use the tool. Act one was Integromat, a Czech automation builder loved by power users who found Zapier too rigid. Act two was the rebrand to Make in 2022, which Cloudwards documented in its February 2022 update noting that Integromat changed its name. Act three is happening now: the company description, the AI toolkit and the 350+ AI app connections all point to AI agents and agentic workflows as the headline product.
Why should a founder care about corporate positioning? Because positioning tells you where the product team spends its time. When a company rewrites its own description around AI agents, new features, templates and pricing experiments will follow that direction. If your automations are classic “form to CRM to email” flows, you will still get updates, but the flashy releases will target AI use cases. Plan your stack with that in mind.
My Mean CEO take: I welcome this shift, with conditions. I see AI as a force multiplier for small teams and solo founders, and Make’s visual canvas gives you something many pure AI agent tools lack: you can SEE every step the agent touches. Visibility matters when an AI is sending emails to your customers on your behalf.
How does Make.com pricing work in 2026?
Make charges by credits. Every step that runs in a scenario costs one credit. That sounds harmless until you do the math. Zapier, a direct competitor, wrote a surprisingly fair analysis of Make.com pricing and its credit model, and one line stuck with me: “the credit math demands more of your attention as your scenarios grow, and the consequences of miscalculating (scenarios stopping mid-month, bills climbing faster than expected) are real.”
Yes, a competitor wrote that, so read it with a pinch of salt. But the arithmetic does not lie. Here is how I calculate credit burn before building anything.
The credit math every founder should run (my own calculations)
- Scenario A: lead capture. Trigger + CRM entry + welcome email + Google Sheets row + Slack alert = 5 credits per lead. With 200 leads a month, you burn 1,000 credits. That is the ENTIRE free plan gone on one modest workflow.
- Scenario B: scheduled polling. A 5-step scenario that checks for new data every 15 minutes runs 96 times a day, around 2,880 times a month. At 5 credits per run, that is 14,400 credits per month, even on days when nothing new happens if the extra steps run anyway.
- Scenario C: the same polling, smarter. Put a filter right after the trigger so the expensive steps run only when there is new data. If only 300 runs a month contain real data, you pay roughly 2,880 trigger checks plus 300 × 4 follow-up steps, around 4,080 credits. Same outcome, about 70% fewer credits.
Lindy, another competitor, puts it bluntly in its breakdown of Make.com plans and costs for 2026: “the free plan is not enough for real workflows and only works for testing and learning.” I agree with the conclusion, and my math above shows why. Treat the free plan as a sandbox, the way I treat the first quests in Fe/male Switch: a safe place to fail before real money is on the table.
Which Make plan fits which founder?
- Free plan: testing, learning, one tiny personal automation.
- Entry paid plan ($12/month): solo founders and freelancers with a handful of predictable scenarios.
- Teams plan: agencies and startups where several people edit shared scenarios and need roles and permissions.
- Enterprise plan: companies that need SSO, audit logs and stronger security controls for automations the business cannot run without.
Which Make.com numbers should shock founders into action?
Numbers change behavior faster than opinions do. Here are the ones I would pin above your desk.
- From 2 weeks to 2 hours. Scalevise, an automation consultancy, reports cutting a client intake process from two weeks to two hours with Make. Their complete guide to Make.com features, costs and business use cases documents projects from Shopify automation to fintech KYC (Know Your Customer) verification.
- 350+ AI apps connect to Make, so your scenarios can call language models, transcription tools and image generators inside one flow.
- 1,000 credits on the free plan disappear with just 200 five-step runs.
- 1,000 vs 1,900 vs 3,000+ apps. Cloudwards cites over 1,000 platforms, Boldtech cites over 1,900 applications and Zapier cites 3,000+ apps. The spread reflects different update dates and counting methods, and it proves my point that app count is a vanity metric (see my take below).
- Every step = 1 credit, including filters, according to Zapier’s breakdown. Poorly ordered scenarios cost real money.
Make.com vs Zapier vs Lindy vs IFTTT: which tool fits your startup?
Comparison articles usually crown one winner. I refuse to do that, because the right tool depends on your stage, your team and your tolerance for tinkering. Here is how I map them.
- Make.com: deeper workflow control and data transformation, routers, filters, custom code and AI agents on a visual canvas. Best for founders who like to SEE the logic and want low entry pricing. Expect a learning curve.
- Zapier: prioritizes simplicity and quick setup for linear automations, as Nexalab notes in its comparison of Make.com with other automation tools. Best for teams that want “set and forget” and will pay more for less thinking.
- Lindy: focuses on AI assistants that make decisions with context, built from templates. Best for founders who mainly want AI agents handling inbox, scheduling or support, with less interest in multi-app data plumbing.
- IFTTT: simple consumer-style applets. Best for personal productivity, rarely for business processes.
One more honest data point: The Digital Project Manager’s Make.com review covering pros, cons, features and pricing calls the platform a practical choice for small to mid-sized teams but notes that “the platform’s support team may be less responsive than some alternatives.” If you cannot debug your own scenarios, factor that in, or budget for a consultant.
How do you build your first Make.com scenario? A step-by-step guide
I will use the classic lead capture flow, the same example featured in this step-by-step Make.com tutorial for beginners in 2026: someone fills out a form on your website, and Make adds them to your CRM, sends a welcome email, logs a Google Sheets row and pings you on Slack. Here is how I would build it with credit costs in mind.
- Map the process on paper first. Write every step, every app and every decision. If you cannot draw it, you cannot automate it.
- Create a free Make account and use it as your sandbox. Do not connect production customer data yet.
- Create a new scenario and add the trigger. Use your form tool’s module or a webhook. Webhooks fire instantly and avoid wasting credits on empty polling checks.
- Add a filter immediately after the trigger. Block spam, test entries and incomplete submissions before they consume credits further down the chain.
- Add your action modules: CRM contact creation, Gmail welcome email, Google Sheets row, Slack message.
- Map the fields carefully. Drag the form’s “email” field into the CRM’s “email” field, and so on. Mismatched fields cause most beginner errors.
- Add a router if you need branches. Hot leads (budget above your threshold) go to a personal follow-up task, cold leads go into a nurture sequence.
- Run the scenario once manually with a test submission and inspect every module’s output bubble.
- Add error handlers so a failed CRM call does not silently drop a lead. Send failures to a dedicated Slack channel.
- Turn the scenario on and check your credit usage weekly for the first month. Compare actual burn with the math you did in step one.
Pro tip from my own stack: name every scenario with a verb, an object and an owner, like “Capture website leads | Sales | Violetta.” Six months later, you will thank yourself when you have 40 scenarios and need to find the one that broke.
What can entrepreneurs automate with Make.com? 8 practical examples
Here are use cases I recommend to founders and freelancers, ranked from “do this tomorrow” to “do this once you have traction.”
- Lead capture and routing: form to CRM to welcome email to Slack, as described above.
- Invoice follow-ups: when an invoice in your accounting tool passes its due date, send a polite reminder and log it in a sheet.
- Content repurposing: a new blog post triggers an AI module that drafts LinkedIn and newsletter versions, which land in a review folder for a human to approve.
- Customer support triage: as one Medium case study describes, a SaaS company routed incoming tickets to the right agent, sent follow-up emails and updated the CRM automatically.
- Chatbot lead qualification: the same Medium article on how small businesses use Make.com automation describes a gym whose AI chatbot collects, qualifies and categorizes client info automatically.
- New client setup: contract signed triggers folder creation, project board setup, a welcome packet and a calendar invite.
- Investor update prep: pull monthly numbers from your sheets and payment tools into a draft update document on the first of each month.
- IP and file hygiene (my CADChain brain talking): when a design file lands in a shared folder, log who uploaded it, when, and under which project. Proof of authorship becomes a byproduct of your daily work.
For agencies and teams inside larger companies, Boldtech’s guide explaining what Make.com is and who it suits makes a strong case: non-technical departments like marketing, sales and operations can manage their own automations without waiting in the IT queue.
What are the most common Make.com mistakes to avoid?
I have watched founders burn money, data and sleep on these. Avoid them and you are already ahead of most Make users.
- Polling every minute “just in case.” Schedule frequency multiplies credit burn. Use webhooks or sensible intervals.
- Placing filters at the END of a scenario. Filter early, so expensive steps run only on data that deserves them.
- Building one giant “god scenario.” One 40-module monster is impossible to debug. Split it into smaller scenarios linked by webhooks.
- Skipping error handling. Silent failures are the most expensive kind. A lost lead never complains.
- Connecting personal accounts. If a team member leaves and the scenario runs on their Gmail, everything breaks. Use shared service accounts.
- Letting AI agents act without a human checkpoint. AI drafts, humans approve, especially for anything customer-facing or financial.
- Ignoring GDPR. As a European founder, I see this constantly. Know which personal data flows through which apps and where it is stored. Document it.
- Automating a process you have never done manually. Automation multiplies whatever you feed it, including a broken process.
- Counting on fast support during a crisis. Given review feedback about support responsiveness, keep someone on your team (or a freelancer) who can debug scenarios.
What is Mean CEO’s take on Make.com in 2026?
Now for the part where I get opinionated. These takes come from running multiple ventures in parallel, building an entire incubator game on no-code tools, and spending years at the intersection of linguistics, game design and IP law.
Take 1: The credit meter is a game economy, so play it like one
I design game economies for a living, and Make’s credit system behaves exactly like one. Every action has a cost, scarcity forces choices, and players who understand the rules win. Founders who complain about credits usually never read the rules. Treat credits as your in-game currency: budget them per scenario, track spending weekly, and reward yourself for cutting waste. My principle applies here: “Gamification without skin in the game is useless.” Credits ARE the skin in the game, and they make you think before adding a lazy extra step.
Take 2: App count is a vanity metric
1,000 apps, 1,900 apps, 3,000 apps. Nobody needs 3,000 apps. You need the 6 to 12 tools your business runs on, with DEEP connectors that cover the actions you actually use. Before committing, open the module list for each of your apps and check whether it supports the exact triggers and actions you need. A connector with only “create record” and no “update record” will force workarounds and burn credits.
Take 3: Default to no-code until you hit a hard wall
This is one of my operating principles, and Make fits it well. Early-stage founders should treat no-code and AI as their first engineering team. I proved with Fe/male Switch that a complex role-playing incubator can run on no-code infrastructure. So when do you hit the wall? Nexalab describes the signal well: workflows start carrying approval rules, internal data and business decision logic. When a scenario becomes something your company cannot survive without, and it needs version control, testing and strict access control, that is the moment to consider custom code for that specific workflow. Keep everything else in Make.
Take 4: Agentic workflows need a human in the loop
An AI agent inside a scenario is like a junior employee who never sleeps and never asks questions. That second part is the danger. I advocate human-in-the-loop AI: the AI handles pattern recognition and mechanical tasks, and humans keep judgment, ethics and narrative. In Make terms, add an approval step (a Slack button, an email confirmation, a review folder) before any AI output reaches a customer, an investor or a bank account.
Take 5: Compliance should be invisible, so build it into scenarios
At CADChain, we embed IP protection directly into CAD workflows so engineers stay compliant without becoming lawyers. Apply the same thinking to Make. Add logging modules that record who did what and when. Add data deletion scenarios for GDPR requests. Make consent checks part of the lead flow. When protection lives inside the workflow, your team does the right thing automatically.
Take 6: Women founders need infrastructure, and automation is infrastructure
I often say “Women do not need more inspiration; they need infrastructure.” A solo female founder with ten well-built scenarios operates like a small team. She answers leads in seconds, chases invoices automatically and ships content on schedule. That is real leverage over structural barriers like limited access to capital for hiring. If you are a woman building a business alone, your first “hire” can be a $12/month automation plan and a weekend of focused building.
Make.com FAQ: quick answers for busy founders
Is Make.com free?
Yes, Make offers a free plan with 1,000 credits per month. It works for testing and learning, but most real multi-step workflows exceed it quickly.
What was Make.com called before?
Make.com was previously called Integromat. The rebrand happened in 2022, which is why older tutorials still use the old name.
Who owns Make.com?
Company records list Make’s legal name as Celonis s.r.o., headquartered in Prague, Czechia.
How much does Make.com cost in 2026?
Paid plans start at $12/month for the entry tier, with Teams and Enterprise plans above it. Your real cost depends on how many credits your scenarios consume.
What is the difference between Make.com and Zapier?
Make offers deeper workflow control, branching and data transformation on a visual canvas. Zapier focuses on simplicity and fast setup for linear automations.
Can Make.com run custom code?
Yes. Advanced users can run JavaScript or Python through the Make Code app inside scenarios.
Does Make.com support AI agents?
Yes. Make includes AI agents, an AI toolkit and connections to over 350 AI apps, so you can add AI steps such as classification, drafting and summarizing to your workflows.
What should you do next with Make.com?
The big Make.com news for November 2026 comes down to direction and discipline. The direction is AI agents and agentic workflows on a visual canvas. The discipline is credit math, because every step costs money and sloppy scenarios punish you at the end of the month. Founders who learn both will run leaner companies than competitors who hire people to copy and paste between apps.
Next steps, in order:
- List the 5 most repetitive tasks you or your team did last week.
- Pick ONE and map it on paper, including every app and decision.
- Calculate the monthly credit cost using the formula: steps × runs per month.
- Build it on the free plan with filters early and error handling from day one.
- Add a human approval step to anything involving AI output or customer communication.
- Review credit usage weekly for a month, then decide whether to upgrade.
- Repeat with task number two.
My final word as Mean CEO: “Education must be experiential and slightly uncomfortable.” The same goes for automation. Reading about Make will not change your business. Building one scenario this week, breaking it, fixing it and watching it run while you sleep will. Your competitors are already doing it, so open the canvas and start.
People Also Ask:
What is Make.com?
Make.com is a visual, no-code automation platform that connects apps and runs multi-step workflows without writing code. It was formerly known as Integromat. Users build automations, called scenarios, by dragging modules onto a canvas and linking apps like Gmail, Slack, Google Sheets, Shopify, and Airtable.
What does Make.com cost?
Make.com has a free plan with 1,000 operations (credits) per month, which suits beginners and light automations. Paid plans start at roughly $9 to $10 per month. They scale up based on how many operations your scenarios run each month. Higher tiers add team access, priority scenario execution, and custom enterprise pricing. Prices can change, so check the Make website for current rates.
Is Make.com free to use?
Yes. Make.com offers a free monthly plan with 1,000 operations. You can test the platform, build simple scenarios, and connect a few apps at no cost. If you need more operations, faster scheduling, or more active scenarios, you can move to a paid plan.
How does Make.com work?
Make.com works through scenarios. Each scenario starts with a trigger, such as a new form submission or a received email. One or more actions in other apps then follow. You build the flow on a visual canvas and can add filters, routers, and conditional logic to control where data goes and when each step runs.
What apps can Make.com connect to?
Make.com connects to more than 3,000 apps, including Gmail, Slack, Google Sheets, Shopify, Airtable, Stripe, and Google Calendar. It can also send HTTP requests, receive webhooks, and connect to custom APIs. This lets you link tools that don't have a ready-made Make module.
What was Make.com called before?
Make.com was previously called Integromat. The company rebranded to Make in 2022 and kept the same visual automation approach. It later added a refreshed design, AI modules, and AI agents.
What is the difference between Make.com and Zapier?
Both tools connect apps and automate tasks without code. Make.com uses a visual canvas where scenarios can branch in several directions with routers, filters, and loops, which suits multi-step workflows with conditions. Zapier uses a more linear, step-by-step builder that many people find simpler to start with. Make.com often costs less per automated step, while Zapier supports a larger catalog of apps.
What is AI process automation?
AI process automation combines artificial intelligence with workflow automation so software can handle tasks that need judgment, not just fixed rules. AI models can read emails, sort support tickets, pull data from documents, summarize text, or decide the next step in a process. Platforms like Make.com let you add AI models and AI agents to automated workflows that connect with everyday business apps.
What is the best platform to create an app?
The best platform depends on your skills and the type of app you want. No-code builders like Bubble, Adalo, Glide, and FlutterFlow let beginners create web or mobile apps without programming. Developers often choose Flutter or React Native for cross-platform mobile apps, Xcode for iOS, and Android Studio for Android. Tools like Make.com can then connect your app to other services and automate backend tasks.
Can I create my own software?
Yes, anyone can create their own software. You can learn a programming language such as Python or JavaScript and build programs from scratch. You can also use no-code and low-code platforms to design apps and automations with visual tools. AI coding assistants help beginners write and fix code faster. A small first project, like a simple automation or a to-do app, is a good way to learn.
FAQ on Make.com Automation, AI Agents and Credit Costs in 2026
Should a bootstrapped startup choose Make.com or n8n?
Pick Make.com if nobody on your team wants to manage servers and you need working automations this week. Choose n8n if you have technical talent and want self-hosting for data control. Self-hosted n8n still costs hosting, maintenance, security patching and debugging time. Compare Make.com vs n8n for bootstrapped startups
How do I know my startup needs a workflow orchestration tool?
If you spend time every day copying data between your CRM, inbox, forms and spreadsheets, you have become the API between disconnected tools. Track one week of manual transfers. Any task repeated more than five times a week is a strong candidate for a Make scenario. Explore why workflow orchestration matters for startups
Do AI agent steps in Make.com cost more than regular modules?
Often, yes. AI-powered steps can consume extra credits depending on the model and token usage, and one agent may call several tools in a single run. Test each agent on 20 sample inputs and log credits per run. Then multiply by your expected monthly volume before going live. See how AI agents work inside Make.com
Which marketing automation should a startup build first in Make.com?
Start with content publishing. A finished article can trigger social drafts, newsletter snippets and a scheduling entry. Only automate tasks you could do in your sleep, meaning work that is stable, repeated and well understood. Leave positioning and messaging decisions to humans. Join the AI for startups marketing automation workshop
How can founders avoid lock-in to Make.com?
Export every scenario blueprint as a JSON file each month. Keep a plain-language document describing each workflow's trigger, steps and owner, and store credentials in a password manager. For your three most critical flows, identify a backup tool such as Zapier or Airtable automations. Read about reducing automation platform dependency
Can Make.com connect to apps without a native integration?
Yes. The HTTP module can call any REST API using an endpoint, headers and an authentication token, and custom webhooks receive data from tools that send events. Read your app's API documentation first. Test requests in a free tool like Postman, then rebuild the working request inside Make.
Where does Make.com store data, and is it GDPR-friendly?
Make offers EU and US hosting regions, so European founders should select an EU region when creating their organization. Review Make's data processing agreement and minimize the personal data passed between modules. Enable the "data is confidential" setting for scenarios that handle sensitive customer information.
What technical skills help non-technical founders master Make.com?
Learn three concepts: JSON structure, arrays, and the iterator-aggregator pair that splits and recombines lists. Then master built-in functions such as formatDate, if and get. Be careful with iterators. Processing 50 line items multiplies the credit cost of every downstream step by 50, so filter items before iterating.
Should founders hire a Make.com consultant or build scenarios in-house?
Build simple linear flows yourself so you understand your own processes. Hire a certified Make partner for payment, KYC or multi-system workflows where errors are costly. At handover, insist on documentation, error handling, scenario blueprints and a recorded walkthrough so your team can maintain everything afterward.
How should startups measure ROI from Make.com automations?
Track three numbers per scenario: hours saved monthly, credits spent per successful outcome, and error rate. Multiply hours saved by your hourly value and compare the result against your plan cost. Retire scenarios that cost more in maintenance than they save, and reinvest those credits elsewhere. Get the AI automations for startups guide
