How to Automate Client Onboarding with Make.com (No Code)

Written by

A new client says yes, and then the busywork starts. You copy their details into three tools, write the same welcome email you wrote last month, set up a folder, and try to remember which questions you forgot to ask. With Make.com you can automate the client onboarding process so one signed form kicks all of that off on its own: the folder appears, the welcome email goes out, the task list is created, and you get a short summary of the new client. You build it once, in an afternoon, without code.

Imagine your next client signs on a Tuesday evening. By the time you open your laptop on Wednesday, their folder is ready, they already have a friendly welcome email with next steps, and your kickoff checklist is waiting with their name on it.

No password needed – your reset opens instantly.

No password. Just your email, and you’re in.

This guide is about the first week after a yes. If your problem is chasing proposals before the yes, see our guide to automating proposal follow-up emails. If you want to keep the CRM tidy later on, that is covered in n8n CRM automation for small business.

What a Make.com client onboarding automation actually does

Make calls an automation a scenario: a chain of modules that pass data from one app to the next (Make’s own guide explains the basics). For onboarding, a solid first scenario looks like this:

Trigger: a new response in your intake form (Google Forms, Typeform, Tally or Jotform all connect to Make).
Create a client folder in Google Drive or Dropbox, named after the client.
Add the client to a Google Sheet or your CRM, so you have one source of truth.
Create the onboarding tasks in Trello, Asana, ClickUp or Notion from a fixed checklist.
Draft a personal welcome email with an OpenAI or Claude module, using what they wrote in the form.
Send it through Gmail or Outlook, or save it as a draft if you want to read it first.
Ping yourself on Slack or email with a three-line summary of the new client.

That is seven modules. Most freelancers and small agencies only need these, and you can add more later.

How to automate client onboarding without hiring a developer

You do not need to write code for any of this. Here is the order that tends to work best, because each step can be tested before you add the next one.

Step 1: Write your onboarding down first (15 minutes)

Open a blank doc and list what you do for every new client today. The welcome email, the files you ask for, the kickoff call, the tools you give them access to. If it is not on the list, the automation cannot do it. This is also the moment to cut steps that nobody needs.

If your onboarding only lives in your head, talk it through once and let AI do the writing. Our guide on how to use AI to write SOPs shows how to turn a voice memo into a checklist you can build this scenario from.

Step 2: Build the intake form (20 minutes)

Ask only what you need to start: name, company, email, the main goal, deadline, and links to any files. One open question like “What would make this project a win for you?” gives the AI something real to write the welcome email from.

Step 3: Create the scenario in Make (45 minutes)

Start a new scenario, add your form app as the trigger, then add the modules from the list above one at a time. After each module, click Run once and submit a test form. Check that the folder, row and tasks appear before moving on. Make’s free plan is enough to build and test this, but check the current limits on their pricing page, because a busy month of onboarding uses more operations than you might expect.

Step 4: Add the AI welcome email (20 minutes)

Add an OpenAI (ChatGPT) or Anthropic (Claude) module and map the form answers into the prompt. You need an API key from that provider; usage is billed separately from a ChatGPT or Claude subscription. A prompt that works well:

You write onboarding emails for [your business]. Write a warm, short welcome email (under 150 words) to {{name}} at {{company}}.
Mention their goal in their own words: "{{main goal}}".
List the next 3 steps: 1) book the kickoff call here: [your booking link], 2) upload files to: {{folder link}}, 3) reply with any questions.
Plain language, no hype, no exclamation marks. Sign off as [your name].

For the first few clients, send the result to Gmail as a draft instead of sending it. Read it, fix it, and only switch to automatic sending once you trust the output.

Step 5: Turn it on and watch the first three runs

Set the scenario to run on new form responses and check the history after each real client. If a run fails, Make shows you exactly which module broke and with what data, which makes fixing it a lot less scary than it sounds.

Recurring client reports: use a ChatGPT Project, not a custom GPT

Many onboarding guides tell you to build a custom GPT for each client’s recurring reports. Creating new custom GPTs is no longer possible on the Free, Go, Plus and Pro plans, so that advice has gone stale. A ChatGPT Project does the same job well: it keeps one client’s chats, files and instructions together, and OpenAI suggests reusing a project for recurring tasks like weekly drafts.

Set it up like this:

Create one project per client, named after them.
Upload the brief, the signed scope and last month’s report as files.
In Project settings, add instructions such as: “Write the monthly report for [client]. Use the same headings as last month’s report. Keep it under one page. Flag anything that is behind schedule.”
Each month, open a new chat in that project, paste the new numbers, and ask for the report.

Because the context lives in the project, you stop re-explaining the client every month.

Make a first 30, 60, 90 day onboarding plan with ChatGPT

For longer engagements, a simple 30, 60, 90 day plan sets expectations early. Paste the client’s intake answers into ChatGPT (or into their project) and ask:

Based on this client intake, draft a 30/60/90 day plan.
For each phase: 3 goals, the deliverables, and what I need from the client.
Keep it realistic for a team of [1 / 3 / 5] people. Format it as a short table.

Treat the output as a first draft. You know what is realistic; the AI does not. Edit it, then save the final version into the client folder your Make scenario created.

Common mistakes (and how to avoid them)

Automating a messy process. If your onboarding changes every time, write the checklist first. Automation repeats whatever you give it.
Letting the AI send unchecked emails on day one. Use drafts until you have seen at least five good results.
Collecting too much in the form. Long forms tend to get abandoned. Ask for the rest on the kickoff call.
Forgetting the client’s side. The goal is a smoother first week for them, not only fewer clicks for you. Read the welcome email as if you were the client.
No error alert. Turn on Make’s email notifications for failed runs so a broken step does not go unnoticed for weeks.

What you end up with

A new client fills in one form. Within a few minutes they get a welcome email that sounds like you, their folder and task list exist, and you get a short summary. Your monthly reports come from one ChatGPT Project per client instead of a blank page. For more ready-made message wording, our ChatGPT client communication templates pair nicely with this setup, and if you are watching costs, see these free plan automation examples.

Want step-by-step builds like this one? Start free.