Skip to content

Free course: 5 steps, 12 real workflows

Learn n8n by taking real business problems apart.

Every messy problem has seams. 12 real workflows show you where to cut: every part, which ones use AI, and how each one was tested. Then you rebuild it in your own n8n.

Free to read. No account needed.

Four work problems on a cutting mat. The inbound lead is cut into its five workflow steps, run on made-up data.
10th in line

“Dashboard down since 9 AM. Thinking about cancelling.”

Shared support inbox, 400 tickets a week (example)

Invoice INV-2207

Hosting, October$1,240.00

Due14 Nov

One of 150 a week, typed in by hand (example)

  1. A lead arrives: FernwayTrigger
  2. Read the homepageRule step
  3. Score fit 80, intent 70AI step
  4. 75.5, tier A, owner setRule step
  5. Reply drafted, not sentPerson step
see how this one is cut

Every workflow is a puzzle you can take apart.

Pick one. Each is a real walkthrough from the library: the problem, every step and its kind, and what comes out, run on made-up data.

Customer Support

Support ticket triage

Support is a shared inbox and the urgent ticket is tenth in line. Someone reads every ticket to decide its priority and team, so outages wait behind how-to questions and churn threats get missed.

What goes in

Example on made-up data: a ticket to Fernway support from a made-up customer: our dashboard has been down since 9 AM and we are thinking about cancelling.

  1. Trigger

    Tickets arrive

    up to 100 a call

  2. Rule step

    Split and cap each one

    6,000 characters

  3. AI step

    AI sorts and drafts

    category, priority, churn

  4. Rule step

    Rules pick team and deadline

    key plans go first

  5. Person step

    A person handles P1 and churn

    sends every draft

What comes out

Category outage, priority P1, churn mention yes. Team and deadline set by rule. Escalated to a person because of the P1 and the churn mention. Reply draft saved, not sent.

When not to automate it

It does not send replies, promise refunds or set timelines.

Read the full walkthrough: Support ticket triageAll workflows in the library

the free course

The path: five cuts, in order.

Five walkthroughs in order. You rebuild each one in your own n8n, on made-up data first. Each step adds one skill.

steps, in order
5steps, in order
real workflows to rebuild
12real workflows to rebuild
checks every build must pass
8checks every build must pass
free to read, no account
$0free to read, no account
  1. Stop 1 of 5: Learn the five parts of a workflow

    A trigger starts it, rule steps check and route, an AI step reads or drafts, a person approves, and the result lands somewhere.

    Inbound lead qualification

    After this, you can read any workflow and say what each step does

  2. Stop 2 of 5: Build a report where rules do the work

    Clean a week of exports, rebuild the tables by key and let code compute every number. The one AI step only words the notes.

    Weekly KPI report

    After this, you can build a scheduled workflow that cleans data

  3. Stop 3 of 5: Add one AI step, with rules around it

    AI sets a ticket's category and priority and drafts a reply. Fixed rules pick the team and the deadline.

    Support ticket triage

    After this, you can use AI for judgement and keep decisions in rules

  4. Stop 4 of 5: Keep a person in charge of what goes out

    AI pulls the summary and next steps from a sales call. A person approves the CRM update and the email first.

    Call notes to CRM

    After this, you can design a workflow where nothing leaves without approval

  5. Stop 5 of 5: Try to break it

    Run the 8 checks on your build: a test set, a prompt attack, run twice, failure recovery, limits, an alert, sign-off and rules around the AI.

    The 8 checks

    After this, you can show a workflow you have tested, not one that ran once

Start step 1: read a real workflow

Free to read. No account needed.

learn together

Nobody learns automation alone.

Todkett is a course and a community in one. You learn a workflow, build it, then bring it to other builders who ask, show and review each other’s work.

My AI step returns empty JSONQuestions, step 3: support ticket triage

Set the output to a fixed schema and add a rule step after it that rejects anything empty. That is check 4 of 8.

Example thread, made up to show how it works.
  • Ask when it breaks

    Post the failing step and what you expected. Get a fix, not a lecture.

  • Show what you built

    Share the run, never your data, and how you fitted it to your tools.

  • Compare approaches

    One problem can take rules, an AI step or a person. See how others chose.

  • Review each other

    Run the 8 checks on a friend's build and find what breaks before it ships.

Stuck today? Ask by form and get a reply by email.

who teaches it

NitinSarkar

Learn from someone who builds automations for real businesses.

Nitin Sarkar runs Todkett from Bangalore and builds and tests every workflow on the site in n8n. The teaching follows the same habits as the building.

48
n8n workflows built from zero for a US education company, in about seven weeks
154
job applications scored by one AI screening run, an estimated 7.7 hours of reading saved
70 to 80%
of manual sales and finance work automated for B2B clients

How the teaching works

  1. 1

    The problem comes first

    Every walkthrough opens with the business problem it solves, and says when a task is not worth automating.

  2. 2

    AI only where a rule cannot do the job

    Every AI step is marked, with what it may read and why a rule would not do.

  3. 3

    You build it yourself

    You rebuild each workflow in your own n8n, step by step, on made-up data first.

  4. 4

    Then you try to break it

    Every workflow lists the 8 checks it has to pass, and you can run them on your build too.

before you start

What people ask first

  • Who is Todkett for?

    People who want to learn AI automation by building it: founders and operators automating their own work, freelancers, students and anyone changing careers. You do not need a team or a budget.

  • Do I need to know how to code?

    No. n8n is a visual builder: you connect steps on a canvas. A few workflows include a short code step for a calculation or a check, and each walkthrough says in plain words what that step does.

  • What is n8n, and what can I build with it?

    n8n is a workflow automation tool you can use in the cloud or run on your own server. It connects apps, moves data between them and can call an AI model as one step. The 12 walkthroughs here cover leads, support tickets, invoices, reports, content, hiring and more.

  • Are there courses?

    Not yet. Today you learn from walkthroughs: each one is a real workflow explained step by step, which you rebuild in your own n8n. The learning path on this page puts five of them in order.

  • How does the community work?

    It is not open yet. When it opens, builders will ask questions and show what they built, in public. Until then, ask by form or book a 30-minute call about your own workflow.

  • How do I go from learning to real projects?

    Follow the path: learn the parts, build with rules, add one AI step, keep a person in charge, then try to break your build with the 8 checks. A workflow that passes them is one you can show to someone else.

  • Can I find paid work or gigs here?

    Not yet. Paid work is the last stop on the line and it is not built. Todkett will not list a job until there is a real one.

  • What does it cost?

    Reading the walkthroughs and using the browser tools is free and needs no account.

Start with one piece.

  1. LearnFive walkthroughs, in order
  2. BuildReal workflows, taken apart
  3. AskBy form, or book a 30-minute call
Start learning

Free to read. No account needed.