LearningFlow LearningFlow vs Make.com
Make and LearningFlow both hand you a node canvas. Make wires your business systems together and runs the result quietly in the background, which it does better than we do. LearningFlow's canvas runs in front of a class, and its Work with AI sandbox hands back a finished .xlsx or .docx.
Automation · Sources last read 13 September 2026
Choose Make.com if
Choose Make when the job is getting systems you already pay for to talk to each other.
- An enquiry form has to create the applicant in the SIS, file the signed PDF in SharePoint and chase non-responders after 72 hours.
- You need a connector for a system nobody outside the bursary has heard of, and Make has 3,000+ plus a path to build your own against any REST API.
- The back office wants scenarios firing every minute with retries and error handlers, and nobody outside IT ever needs to see them.
Choose LearningFlow if
Choose LearningFlow when what you build ends up in front of a student, or hands a colleague a finished file.
- The flow that writes the quiz is also the assignment a Year 8 class works through, using their own student accounts and a join code.
- You want back an .xlsx whose formulas still calculate, or a narrated MP4, not a file parked in a Drive folder.
- A teacher leaves in July and the school keeps the flows, the bases and the apps, because the organisation owned them from the moment they were created.
Where the two are built differently.
Nodes that run behind the scenes.
The canvas is excellent and its audience is machines. Nothing here is something you hand to a person and ask them to work through.
The same canvas. Two audiences.
Connections are typed, so the canvas refuses a wrong wire while you are dragging it rather than at three in the morning. And every flow has an address, so your own software can run it.
What each one does.
Written from each product's own documentation. Where something is true only on a higher tier, the row says so.
| Make.com | LearningFlow | |
|---|---|---|
| Student accounts | There is no learner user type, and no roster, class, assignment or grading object; every user is an organisation or team member. | Students are a first-class user type with their own accounts, join codes and assignments. |
| Per-member capabilities | Access comes from six organisation roles and six team roles; custom roles are Enterprise only and are all-or-nothing per resource type. | Seven capabilities are switched per member: org-library, chat, flow-creator, assignment-creator, solution-designer, base and work-with-ai. |
| Learning records | No learning-record standard is documented, so anything an LRS needs has to be assembled module by module. | xAPI is built in: package ingest, a self-hosted SQL LRS, or point at the organisation's own LRS. |
| Wrong connections | Modules are mapped field by field, with error handlers and a run history that shows what failed after it ran. | Connections are typed, so the canvas refuses a wrong wire while you are still dragging it. |
| Calling it from your code | Scenarios take webhook triggers, and the REST API is paid-plan only, with limits from 60 requests a minute on Core to 1,000 on Enterprise. | Every flow has an address: POST /task/:taskId with an x-api-key, optional SSE streaming, and per-key credit top-up and usage reporting. |
| When someone leaves | Scenarios, connections and data stores belong to the team, so removing the person leaves them in place. A scenario can be cloned into another team, or exported as a JSON blueprint. Connections, webhooks, keys and data stores stay in the team they were made in. | orgId is stamped at creation and never moves between organisations; removing a member deletes the membership row, not the work. |
| Third-party connectors | 3,000+ standard app connectors, plus a documented way to build your own against any HTTP or REST API. | Published apps call a fixed set: Gmail, Resend, WhatsApp, Firecrawl, document parse, file upload, image and video generation, speech-to-text, web search and crawl. |
| What you pay for | A monthly credit allowance with unlimited users, from $9 a month on Core for 10,000 credits, but credits reset each cycle and top-ups cost 25% more. | Credits rather than seats, no subscription required, and personal, organisation and enterprise wallets kept separate. |
What comes with it here.
A file, not a route to one
Work with AI runs a sandboxed Linux machine with Python, pandas, openpyxl and LibreOffice, and returns a real .xlsx whose formulas still calculate, or a .docx, .pptx, .mp3 or .png.
59 tools already written
Flow Designer ships a public gallery of 59 teacher tools, including lesson plans, marking rubrics, quizzes, text levelling and questions drawn from a YouTube video.
A contract per app
One solution can hold three apps over a single database: the one students open, a webhook and a nightly scheduler. Each gets its own contract, naming the tables and columns it may read or write, the rows it may see, and the date the access runs out. Suspend or revoke one app and the other two keep running.
Model choice is not a tier
Claude, OpenAI, Gemini, Grok and DeepSeek among others are on the list whatever you pay. No plan, seat or free tier changes it. The only gate is a per-organisation admin override.
Where Make is the better choice
If the problem is systems that do not talk to each other, Make is the better tool and it is not close. An admissions office that needs a web form to create the applicant in the SIS, copy the record to the CRM, file the signed PDF in SharePoint and chase non-responders after three days should buy Make rather than us. It has 3,000+ connectors, one-minute scheduling, retries and error handlers, a large community publishing templates, and it starts at $9 a month with unlimited users. LearningFlow has nothing like that reach, and a school paying for both is a sensible outcome.
The whole stack against Make.com.
The table above compares the two at the job they share. This one runs every capability past both, because what a school is choosing between is usually a tool that does one job and a workspace that does many. Hover any mark to see what it means, and a partial one to see exactly what is limited.
| LearningFlow | Make.com | |
|---|---|---|
| Ask and read | ||
| Chat with AI | ||
| Research the web and write it up | ||
| Read text off an image or a scan | ||
| Agent browses the live web | ||
| Make | ||
| PowerPoint deck | ||
| Spreadsheet with working formulas | ||
| Word document | ||
| Image generation | ||
| Video generation | ||
| Narrated whiteboard video, corrected scene by scene | ||
| Voice-over | ||
| Song generation | ||
| Interactive web page | ||
| Edit what it made, online | ||
| Slide and design templates | ||
| Presenter on camera, from a photo you supply | ||
| Teach | ||
| Ready-made teacher tools | ||
| Build your own tool, no code | ||
| Lesson that branches on the answer | ||
| Hears them read aloud, checks pronunciation | ||
| Assign to a class with a join code | ||
| Assignments and submissions | ||
| Student accounts | ||
| LTI link from your LMS | ||
| Learning records to your own LRS | ||
| SCORM 1.2 package out | ||
| Build | ||
| Working app | ||
| Full working platform templates | ||
| Several apps over one database, rights each | ||
| App sends email or WhatsApp | ||
| App runs on a schedule | ||
| App accepts webhooks | ||
| Generate real-time apps | ||
| Generate AI-driven apps | ||
| Shared database | ||
| Revoke one app's access, not the others | ||
| Run | ||
| Run any tool from your own software | ||
| Choose the AI model, on every plan | ||
| Switch a feature off per group | ||
| Organisation keeps the work when staff leave | ||
| We do not do this | ||
| Transcribe a video or audio file | ||
| Custom domain for a published app | ||
Before they decide.
Can we run both?
Yes, and that is the usual answer. Every LearningFlow flow has an address, so a Make scenario can call POST /task/:taskId with an x-api-key as an HTTP module, and published LearningFlow apps accept signed webhooks and cron schedules. Make keeps the SIS, CRM and finance plumbing; LearningFlow makes the thing a class actually opens.
Can I move my existing Make scenarios across?
Not by import. There is no scenario export that LearningFlow reads. Make does export a scenario as a JSON blueprint and clones a scenario into another team, but nothing on our side imports either. The practical route is to leave the integration scenarios where they are and rebuild only the classroom-facing parts, which often means picking one of the 59 gallery tools instead of building anything.
How does the money compare?
Make is $9 a month on Core for 10,000 credits with unlimited users, which is cheap for a whole institution, but credits reset at the end of each cycle and extra credits carry a 25% premium, so 1,000 top-up credits cost $1.125 rather than $0.90. Make's own AI provider charges credits by input and output tokens, so those runs are the hard ones to budget. With your own OpenAI or Anthropic key it is one credit per operation, and the model provider bills the tokens separately. LearningFlow charges credits with no subscription, and keeps personal, organisation and enterprise wallets separate, so a teacher's free monthly grant never spends the school's money.
Does Make support students?
Not as a user type. There are no learner accounts, rosters, classes, assignments or grades, and everyone is an organisation or team member. Make does run Teach Make, which gives students six months of free Core and educators free access, but those are individual accounts for learning automation rather than a class you manage.
A teacher leaves in July. What happens to what they built?
In Make the assets survive, because scenarios, connections and data stores belong to the team, though connections, webhooks, keys and data stores stay in the team they were made in, and only the scenario itself can be cloned across. In LearningFlow the orgId is stamped at creation and never moves, so removing the member deletes their membership row and not the object, and an admin can list org-library tools whose owner has left and reassign them.
Where this came from. Read on 13 September 2026. Make.com changes its product and its prices without telling us, so check anything that decides a purchase.
- Make Help — Teams (team-owned resources, team roles, items locked to one team) ↗
- Make Help — Custom roles (Enterprise only, all-or-nothing per resource type) ↗
- Make Help — Working with files (retrieving and mapping files, per-plan size limits) ↗
- Make Help — Extra credits (credits reset each cycle, 25% top-up premium) ↗
Try it on your own work.
Teachers get credits every month, free. No card, no seat count.