Make.com Tutorial: 7 Automations Small Teams Actually Use

Make is glue: a canvas where a form, a CRM, Slack, a work OS, and invoicing pass a bundle without a copied row. Small teams do not need 80 scenarios. They need seven boring automations that survive a Friday when the author is out.

This is the how. The brand fight is Zapier vs Make for SMEs. Verify current pricing, operation packs, and transfer limits before you subscribe. The Make link is a placeholder affiliate URL.

If a job is entirely inside one vendor (HubSpot workflow, Pipedrive automation, monday.com recipe, ActiveCampaign journey), start there. Buy Make when the job crosses products.

Who this tutorial is for

Use this if you are:

• A founder or operator on a team of roughly 2–25 people with a real CRM, a real inbox problem, and at least one other SaaS tool.
• Comfortable clicking a visual builder. You do not need to be an engineer. You do need to own the scenarios when they fail.
• Trying to replace copy-paste, not trying to build an internal platform.

Skip this if nobody on the team will open a canvas. Make’s power is wasted if it becomes folklore. Take Zapier, or stay native. Skip it if you wanted self-hosted n8n — that is a different ops posture.

Before you build anything

1. One system of record per object. People in the CRM, money in invoicing, work in the work OS. Make stores recipes. See the lean stack rules.
2. Company-owned connections, not a founder’s personal Gmail.
3. Name scenarios like tickets: lead/form-to-crm-slack, deal/won-to-monday. Future you will search those strings.
4. Decide what a failure does (mailbox or Slack). Do not fail silently.
5. Write the field list first. “Email, first name, source, owner” is a spec. Thirty “just in case” properties is junk.

Make bills around operations — typically “a module ran.” Count runs × modules, add retry headroom, then verify current pricing.

View Make (placeholder)

The seven automations (build these, not a museum)

Each build is the job, the shape, the filter, and what to refuse. Swap HubSpot/Pipedrive and monday.com/ClickUp to match the stack — ClickUp vs monday.com if that tab is still open.

1. Inbound form → CRM contact + Slack

Job: A form creates or updates a person, notifies a channel, and skips junk. Ship this first.

Shape: Webhook or form app → valid-email filter → CRM create/update → Slack.

Prefer a native webhook over polling a sheet. Deduplicate on email. Map source so Friday’s meeting can see “web form.” A landing page is not a second database — landing page builders. Discard empty emails, noisy role accounts, and honeypot fields. Refuse a Slack ping on every spam submit.

2. Won deal → project + kickoff task

Job: Stage becomes “won”; delivery gets a project (monday.com or ClickUp) and a kickoff task.

Shape: CRM deal updated → filter (stage changed to won, not already handed off) → search-or-create project → kickoff task → Slack delivery.

Write the project ID back on the deal so the scenario is idempotent. Missing owner is a branch, not hope. A watch-deals module without the stage-change filter burns operations and duplicates projects. Refuse a project for every stage “for the audit.”

3. Overdue invoice → owner ping

Job: FreshBooks, Wave, or QuickBooks emits overdue; the client owner hears about it. Shortlist: invoicing for freelancers.

Shape: Invoice overdue (or scheduled search) → CRM lookup → Slack DM or a small finance channel → optional CRM task.

Match on a stable key. If you cannot match, ping finance with the invoice number. Skip invoices below a chase threshold. Refuse a ping on every view. Views are noise. Overdue and paid are signals.

4. Meeting booked → CRM activity + owner task

Job: A Calendly / HubSpot meeting lands on the contact and creates a next step after the call.

Shape: Booking webhook → CRM find-or-create → log activity → task dated meeting day + 1 → Slack the owner.

Put title and timezone on the task. Handle cancel as a branch that completes the old task. Refuse a five-email nurture in Make because someone booked — that is ActiveCampaign or HubSpot, not glue.

5. Weekly digest: deals with no activity

Job: Monday, open deals with no activity in seven days land in the pipeline channel.

Shape: Weekly scheduler → CRM search → aggregator (stale) → one Slack table (cap ~25 rows: name, owner, days silent, link).

Exclude parked/nurture stages. Refuse a CRM task and Slack and email. One surface. If the CRM cannot search this way, fix the CRM habit before you automate a dead board.

6. Nightly Google Sheet → CRM (status column)

Job: The sheet is a staging table, not a second CRM.

Shape: Nightly scheduler → rows with status empty/new → router → CRM create/update → write status, timestamp, and CRM ID back.

The write-back is the product. Without it you double-create every night. Skip empty emails and synced rows. Refuse keeping the sheet as truth “because Make can sync it.” The CRM wins.

7. Invoice paid → mark the deal and stop the wrong email

Job: Money landed. The deal shows won if it should, delivery knows, and a “please pay” sequence stops.

Shape: Invoicing paid → CRM lookup → update open deal → Slack delivery → tag/exit in the email tool.

The email step is the one teams forget. Prefer native ActiveCampaign or HubSpot if the event can go there directly. Ignore $0 and test invoices. Refuse auto-issuing a contract from three tools at once. Humans still own exceptions.

Operations hygiene

Price five flows: runs × modules + 30% retries. Verify current pricing. Turn on error handling you understand — infinite retries become the bill. Do not poll every minute if hourly is enough. Review quarterly; offboard connections when people leave; least privilege (invoicing does not need all of Drive). The canvas does not make you safer. The review does.

When not to use Make

Stay native when the CRM can assign an owner on submit, or when ActiveCampaign / HubSpot can tag a deal-stage change inside that vendor. Take Zapier (or stay manual) if nobody will debug a failed bundle. Do not sync HubSpot and ActiveCampaign and Pipedrive “so everything stays aligned.” Pick one email stack and one CRM.

A 14-day build plan

Days 1–3: form → CRM → Slack (one real fill = one contact). 4–6: a money event (overdue or paid only). 7–10: won → one project. 11–12: weekly digest in a private channel. 13–14: sheet sync only if a sheet still exists — then stop using it as a CRM. Judge time to first success, time to first explainable failure, and 90-day volume. Do not also run the same flows in Zapier.

FAQ

Do we need Make if we already have Zapier?
No. One hosted glue layer. Stay on Zapier if the task bill is fine. Switch only if branching or volume made the canvas cheaper and clearer. Verify current pricing with a real run count.

Is Make free enough?
Free/low tiers work as a sandbox. Production volume is a paid conversation. Verify current pricing. Do not plan a company on a free-tier assumption.

Can Make replace our ops hire?
No. It replaces copy-paste. Someone still owns exceptions and offboarding.

Should we put AI in these scenarios?
A summary step is fine. Keep a human in the loop for customer-facing text.

Are you a Make partner?
No. The CTA is a placeholder. We do not claim partnership or publish rates. See the affiliate disclosure.

What to do next

Write the five flows that already waste an hour a week. Build the three that cross products — usually form → CRM, won deal → work OS, and one money event. Leave native automations inside HubSpot, Pipedrive, monday.com, and ActiveCampaign where they already work. Put a calendar reminder in 90 days to kill unused scenarios.

That audit is the tutorial. The seven builds above are only the ones small teams actually keep.