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.
Make.com course · Included in Osum membership
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.
Sound familiar?
“Was banging my head against the wall with make.”
“Webhooks not working. The first run works, I get an accepted notice, then it doesn’t stay connected in the scenarios.”
“Took me about 2 weekends of research / Claude Pro and finally got something up and live.”
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
Lesson 1 writes your first lead into your sheet from an email you sent, checked in 15 minutes. The copy-paste step stops happening.
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.
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.
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.
Modules, schedule and volume become a three-line budget in the note, read against your plan. The credit email stops being a surprise.
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
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.
| Run | Trigger | Status | Operations |
|---|---|---|---|
| Mon 8:00 | Schedule | Success, with a warning | 14 |
| Tue 9:14 | Webhook | Success | 3 |
| Tue 9:15 | Webhook | Error | 2 |
| Wed 8:00 | Schedule | Success, with a warning | 14 |
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?
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.
The curriculum
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
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.
Module 02
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.
Module 03
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.
Module 04
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.
Us vs. them
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.
| Feature | Osum course | Make help center | YouTube walkthroughs | Video 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 | ✓ | Partly | Partly | ✕ |
| 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 settings | Links to them | ✓ | Partly | Partly |
| Cost | Membership | Free | Free | Paid course |
One membership
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
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.
Questions
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.
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.
Osum’s Make course takes about 4 hours: 12 lessons, starting with a 15-minute lead logged into your sheet, checked the same day.
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.
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.
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.
No. Osum is independent and not affiliated with Make or the apps you connect, and the certificate is an Osum certificate.
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.
Keep exploring