Skip to content

Make.com course · Included in Osum membership

Make scenarios finish the job.

Your first scenario worked in the tutorial. By week two it meets junk, rate limits and a renamed sheet, and a failed run stops in silence. Learn the Fail-safe Scenario, the route that gets every run back done.

  • Lesson 1: your first lead logged by Make, checked in 15 minutes
  • By lesson 12: a lead desk that routes, recovers and reports on a schedule
  • No code. Your first job runs on your own sheet and test emails
Get my Make plan About 2 minutes. Lesson 1 is a lead logged and checked the same day.
Would you approve this run? Try it first ↓
Lesson 1: Log your first lead without copy-paste
12 hands-on lessons36 exercises1 certificate for LinkedIn30 courses in one membership

Sound familiar?

You wanted an autopilot. You got a screensaver.

“Was banging my head against the wall with make.”

Make user

“Webhooks not working. The first run works, I get an accepted notice, then it doesn’t stay connected in the scenarios.”

Make user

“Took me about 2 weekends of research / Claude Pro and finally got something up and live.”

Make user

Another tutorial rarely fixes it. A scenario designed for failure usually does. That’s the Fail-safe Scenario, and this course teaches it.

What you’ll be able to do

Build it once. Route the failure.

01

Log work without copy-paste

Lesson 1 writes your first lead into your sheet from an email you sent, checked in 15 minutes. The copy-paste step stops happening.

02

Map every field by name

The field map names what each module receives and where it lands, so nothing arrives in the wrong column. Rows read clean the day they land.

03

Stop junk before it costs

One filter after the trigger refuses what no route should touch. Junk costs a check instead of a run, and the history shows the stop.

04

Give failure its own route

Incomplete executions store a broken run with its error named, and a Retry handler tries again on your schedule. A stop becomes a wait, not a loss.

05

Price the run before it runs

Modules, schedule and volume become a three-line budget in the note, read against your plan. The credit email stops being a surprise.

06

Read the history like a gauge

Five points on Monday: errors, waiting runs, credits, junk, one row read. The Fail-safe Scenario ends where the desk proves itself.

Try it first

Would you approve this run?

Lead Desk ran all week on real emails. Here is what the history tab shows and the report the builder is about to send. Take a minute and decide. It is the same call you make on every run your scenarios hand you.

What the history tab shows

RunTriggerStatusOperations
Mon 8:00ScheduleSuccess, with a warning14
Tue 9:14WebhookSuccess3
Tue 9:15WebhookError2
Wed 8:00ScheduleSuccess, with a warning14
  1. Rule 1: A run marked Success with a warning gets read, not trusted.
  2. Rule 2: An Error run is a stored lead, not a lost one.
  3. Rule 3: Every run’s credits fit the budget in the note.

The report the builder is about to send

All runs succeeded except one glitch. The desk handled 12 leads. Safe to leave it as is for the month.

Approve it, send it back, or approve part of it?

See what a checked review finds
  • Send it back. The report reads calm, but the history does not support it.
  • The Tuesday error (row 3) is a stored run: one lead waits in Incomplete executions with its error named. “A glitch” is a lead on hold, and rule 2 says resolve it before you count it.
  • The two warning runs (rows 1 and 4) carry the same 14 operations for the same weekly report. Warnings are content: read which module flagged them before the month goes on autopilot. Rule 1 fails twice.
  • The 12-lead claim is unverified: 11 rows landed and one waits. Nothing here shows the credits fit the budget either, so rule 3 is unchecked.
  • What you can approve: the desk’s design, once the stored run is resolved, both warnings are read and the count says 12 rows you have read one of.

A bigger plan would not have caught this. Reading the history did, and that check is the last step of the Fail-safe Scenario. Lesson 11, “Read the history like a control room”, teaches it on your own runs. Lesson 1 has you log your first lead the same day. Get your plan and run this check on your own scenarios.

Get my Make plan About 2 minutes. Lesson 1 is a lead logged and checked the same day.

The curriculum

The Make.com course: 12 lessons, one real system.

Osum’s Make course is 12 hands-on lessons, about 4 hours in all. Lesson 1 logs a real lead from an email into your sheet in 15 minutes. By lesson 12 you run a lead desk that routes, recovers and reports on a schedule. You need a free Make account and a Google account. You finish with a certificate you can add to LinkedIn.

Module 01

Run your first scenario

You leave with the lead desk started: your Lead Log sheet, one row Make wrote for you from an email, a field map, and a filter that stops junk before it costs a credit. This log is the system you finish in lesson 12.

  1. Log your first lead without copy-pasteEmail one test lead to Make and check the row it writes in your own sheet.
  2. Map every field the next module needsMap the webhook’s fields to the sheet by name, and write down what each field holds.
  3. Filter out junk before it costs youAdd one filter that lets valid leads through and stops junk before the sheet module runs.

Module 02

Route the work and survive failure

You leave with the desk split by kind: one connection that touches only what the job needs, routes for each kind of lead, and an error route with incomplete executions turned on, so a failed run waits for a fix instead of dying.

  1. Decide what each connection may touchName your Lead Desk connection, check which account it uses, and write the one-line rule for what it may do.
  2. Route each lead to its own pathSplit Lead Desk with a router: questions and bookings down their own routes, everything else to a fallback.
  3. Give the failure its own routeTurn on incomplete executions and add a Retry handler, so a failed run waits for a fix instead of dying.

Module 03

Make it repeat and keep it cheap

You leave with the desk running without you: a Monday report on a schedule it can afford, a written credit budget for the month, and the desk split into parts you can test and back up as blueprints.

  1. Put the desk on a schedule it can keepBuild the Monday report as a scheduled scenario, and decide on purpose which jobs stay instant.
  2. Price the run before you turn it onWrite the desk’s monthly credit budget from its modules, its schedule and its test data.
  3. Split the desk into parts you can testSplit the desk at its one handoff, connect the parts with a webhook, and back both up as blueprints.

Module 04

Watch it, recover it, finish

You leave owning the desk, including when it breaks: a recovered run that did nothing twice, a Monday check you ran on real history, and the whole lead desk finished and running on three test leads.

  1. Recover a failed run without doing it twiceResolve a stored run from the failed module, and prove nothing in Lead Log happened twice.
  2. Read the history like a control roomRun the five-point Monday check on Lead Desk’s real history and replay one run with existing data.
  3. Finish your lead deskRun the whole desk end to end on three test leads and put the finished system on its schedule.
Get my Make plan About 2 minutes. Lesson 1 is a lead logged and checked the same day.

Us vs. them

Why learn Make.com here

The help center tells you what each setting does. Make Academy teaches the interface. This course takes you from one logged lead to a lead desk that routes, recovers and reports, with an exercise after every lesson.

FeatureOsum courseMake help centerYouTube walkthroughsVideo course
One real system, built across every lesson✓✕✕Follow-along demos
Hands-on exercise after every lesson✓✕✕Partly
A worked example to check each exercise against✓✕✕✕
What breaks in week two, and the fix✓PartlyPartly✕
Practice on your own sheet before real accounts✓Partly✕Partly
Certificate from a final check, one question per lesson✓Badge on Make Academy✕Completion certificate
Every other Osum course included✓✕✕✕
Official, always-current settingsLinks to them✓PartlyPartly
CostMembershipFreeFreePaid course

One membership

Learn Make.com. Get every AI course with it.

The same membership covers Zapier for the handoffs a template already fits, Perplexity for research with sources you can open, and Claude Cowork for finished reports from your own files. Each course has its own certificate.

Certificate

Finish it. Prove it.

Show a client, a manager or a hiring team that you can build automations that survive real work. The certificate records a final check you passed, one question per lesson.

  • 12-question final check, one per lesson
  • Miss one? You see which lessons to review, then submit again
  • A public page you control, one click to add it to LinkedIn
  • Earn one for every course in the library

Questions

Before you start

How much does the Make.com course cost?

One Osum membership covers the Make course, its certificate and every other Osum course. It is a subscription. You see the price after your 2-minute plan, before you pay anything.

Do I need a paid Make plan to start?

No. Every exercise runs on Make’s Free plan: up to 1,000 credits a month, with scheduled scenarios waiting at least 15 minutes between runs (checked 28 September 2026). You also need a free Google account for Sheets and Gmail, connected once in lesson 1.

How long does the Make.com course take?

Osum’s Make course takes about 4 hours: 12 lessons, starting with a 15-minute lead logged into your sheet, checked the same day.

I’m not technical. Can I do the Make.com course?

Yes. Osum’s Make course needs no code: if you can use a browser and a spreadsheet, you can do every exercise. The first job runs on your own practice sheet and test emails you send yourself.

I already followed Make tutorials. Why would this course work?

Tutorials show a build on clean data. Osum’s Make course practices what they skip: the filter rule, the failure drill, the credit budget and the Monday check, each on a real job with a worked example to check against. You finish with one running system, not twenty demos.

Will this course make my scenarios never break?

No: nothing can stop renamed sheets, rate limits or junk from arriving. Osum’s Make course gives every failure a route instead: stored with its error, retried on your schedule, resolved once from where it stopped, and caught by a five-point check every Monday.

Is the Make.com course made by Make?

No. Osum is independent and not affiliated with Make or the apps you connect, and the certificate is an Osum certificate.

Keep watching green ticks. Or run a desk that proves itself.

The Fail-safe Scenario is four habits: plan the route, route the failure, cap the cost, watch the runs. You log your first lead in lesson 1, finish the desk by lesson 12, earn a certificate and get every other Osum course. A few quick questions, then your plan.

Get my Make plan About 2 minutes. Lesson 1 is a lead logged and checked the same day.

Keep exploring

Related learning paths

Learn a useful skill. Put it to work.

Practical courses for AI tools and skills. Course and tool names are the trademarks of their respective owners; Osum is independent and not endorsed by them.