Max Igoshev.
Email

Automations for online schools

Five chains that producers and agencies launching online schools ask for most often, from a website form to a report by channel. Each has a diagram, the steps in order and an n8n file you can import.

Five recipes: form to amoCRM, GetCourse payment, webinar, source tags in the bot, weekly report by source
Recipes
5, each with a diagram and an n8n file
Stack
Tilda, Taplink, GetCourse, amoCRM, Telegram
Built on
n8n, same steps work in Make
Scope
Demo built for this page

What this is. My own demo recipes for the portfolio, not projects for a particular school. Each one is built as a real n8n workflow: the file imports through Import from File, and what is left is connecting the school’s accounts. These recipes have not run for a school yet, so the pages carry no result numbers.

Why these five. When a producer or an agency looks for a technical specialist for a school, the request almost always lists the same set: a site on Tilda or Taplink, GetCourse, a Telegram bot with an auto-funnel, amoCRM and API integrations between them. Inside that set five places break most often. The source of a request gets lost. Access after payment is granted by hand. The webinar depends on manual reminders. Nobody can tell which channel brought a person into the bot. The report is put together on Friday evening in a spreadsheet.

What each page has. The problem in the school’s words, the chain step by step with the same numbers as the diagram, what the school provides, what it gets, where the chain breaks, and the n8n file to download.

If the school runs on Make. The steps stay the same and only the nodes change: webhook, HTTP request to amoCRM or GetCourse, Google Sheets and Telegram all exist in Make.

How I work. You describe the funnel: where people come from, where they pay, where the base lives. I pick the recipes that fit, build them on the school’s accounts, test them with a dummy request and hand them over with short instructions. Communication in writing.