Roadmap · Earn independently
Automation for clients (Make)
Opens with creditsFor students and early-career engineers who want to build workflow automations that real businesses pay for, using n8n, Make or Zapier. By the end you can connect apps and APIs, shape data, handle failures, add AI steps safely, protect client data, and scope, price and hand over the work.
By the end, you will be able to
- Explain triggers, actions, JSON, REST APIs, webhooks, API keys, OAuth and rate limits well enough to connect any app with a documented API
- Build, test and monitor multi-step workflows in your chosen tool, with retries, error alerts and no duplicate records
- Add AI steps that return structured, validated output, with a human check and a cost estimate before anything reaches a customer
- Deliver three common client workflows with least-privilege credentials, client-owned accounts and a written handover
- Scope a job from a discovery call, price it by the value it creates and offer a maintenance retainer
The path
8 stages, in the order to learn them. Open one to start.
1How automation worksThe ideas every automation tool is built on: triggers and actions, data mapping, JSON, HTTP and REST APIs, webhooks, authentication and rate limits. Learn them once and every tool, and every API document, starts to make sense.8 topics · ~4 weeks
- 1Triggers, actions and what to automateEvery automation has the same shape.
- 2JSON and data typesAlmost every app and API (the way one program talks to another) exchanges data as JSON.
- 3Data mapping between stepsData mapping means choosing which output of an earlier step fills each input of a later one.
- 4HTTP requests, methods and status codesWhen no ready-made connector exists for an app, you talk to its API directly.
- 5REST APIs and reading API documentationA REST API is a common way of organising an API.
- 6WebhooksA webhook is a message an app sends to your web address the moment something happens, such as a payment going through or a form being submitted.
- 7API keys and OAuthApps need to know who is calling them.
- 8Rate limits and quotasAPIs cap how many requests you can send, such as 100 per minute or 10,000 per day.
8 in this stageOpen this stage2Make in depthLearn Make properly: scenarios and modules, bundles and mapping, functions, routers and filters, iterators and aggregators, data stores, connections and how credits are billed.7 topics · ~5 weeks
- 1Scenarios, modules and bundlesIn Make, a workflow is called a scenario.
- 2Mapping and functionsMake has built-in functions for cleaning data on its way between modules.
- 3Routers and filtersA router splits a scenario into several routes, like a fork in a road.
- 4Iterators and aggregatorsLists are the most common source of confusion in Make, and two kinds of module handle them.
- 5Data storesA data store is a small table built into Make.
- 6Connections, webhooks and the HTTP appMake stores your access to each app as a connection.
- 7Credits, scheduling and pricingMake bills in credits.
7 in this stageOpen this stage- Shaping data and logicReal client data is lists, dates, messy text and records that already exist somewhere else. Learn to loop, merge, look up, clean and deduplicate so workflows produce correct results on real data, not just the test record.7 topics · ~4 weeksOpens with credits
- Errors, retries and monitoringWorkflows fail: APIs time out, tokens expire, someone renames a sheet column. This stage is about failing safely: retrying the right errors, never creating duplicates, getting alerted before the client notices and keeping a record of what ran.6 topics · ~3 weeksOpens with credits
- AI steps in workflowsAdd language models where they genuinely help: classifying, extracting, summarising and drafting. Learn to get structured output, validate it, keep a human in the loop, estimate cost and protect against hallucinations and prompt injection.7 topics · ~4 weeksOpens with credits
- Common client workflowsThe workflows small businesses pay for again and again: lead capture into a CRM, email and document parsing, invoicing, scheduled reports and team notifications. Build each one end to end, reliably, so you have a portfolio before your first client.7 topics · ~6 weeksOpens with credits
- Data privacy and securityAutomations move customer data between apps and hold keys to a client's business. Learn least-privilege access, client-owned accounts, secret handling, personal data rules and clean offboarding, so trusting you is a safe decision.7 topics · ~2 weeksOpens with credits
- Finding clients and selling the workTurn skills into paid work: pick a niche, find clients, run discovery, scope tightly, price by value, get paid safely, hand over properly and keep clients on a maintenance retainer.9 topics · ~3 weeksOpens with credits
6 more stages, 43 more topics, free with an account.
You have seen the open stages of the Automation for clients roadmap. Every topic it covers is listed above, and an account opens the rest: what each topic means, a question to check yourself, the courses, the practice and Tauseef's advice for every stage. Early access is open: sign up and your account is active shortly after.
Everything here is free to learn from. A few things, like adding a roadmap, keeping a cheat sheet or asking Tauseef a question, use credits. You get 15 when you join, your first roadmap is free, and if you are learning seriously and run out, you can ask for more. Credits only make sure the platform goes to people who are actually learning.
Related on Sefism
Picked from the other libraries by shared topics.
Project structures
See all- Apache Airflow project structureFor data engineers scheduling real pipelines with Airflow 3. It starts from
astro dev init(dags, include, plugins, tests and a Runtime Dockerfile that runs Airflow locally in Docker) and grows into dags grouped by business area, logic in a tested include package, asset-driven scheduling, data quality checks, alerts, CI that parses and tests every dag, and dag-only deploys. A self-hosted docker compose and Helm route is shown alongside. - Discord bot project structureA study buddy bot for Discord servers (focus sessions, streaks, a leaderboard), built on discord.js with TypeScript from the official create-discord-bot template. Node runs the TypeScript directly, commands and events are one file each in folders the loaders read, and the bot grows a PostgreSQL database with Drizzle, background jobs and a Docker deploy. For students who have made a
/pingbot and want one that survives thousands of servers.
Career questions
See all- Which freelance skills is AI replacing, and what should I switch to?AI is squeezing basic, repetitive freelance work first: plain data entry, simple transcription and translation, generic articles, basic logos and simple product descriptions. Work that combines a skill with judgement, client context or systems is holding up better, including automation, AI integration, analytics, specialist writing and full projects that own a business outcome.
- How do I start an n8n automation side business?Learn n8n properly on your own workflows first, pick one type of business and one repeatable problem, build two or three demos that solve it end to end, then offer it to a few real businesses at a fair starter price. What clients pay for is a reliable result with error handling and a handover, not a copied template.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
- 1:1 Mentorship
- Fresh Graduate Mentorship
- Career Guidance
Brand deals, promos and partnerships: tauseeffayyaz@gmail.com