Skip to content
Skofi
Make.com

Flows and tools that run, sorted by what they do.

30 reusable flows and tools built on Make.com, grouped by the job they do. Each page says where else it would apply; the organisations they were built for are under By organisation.

Sync & integration

Keeping two systems telling the same story: instant events for speed, a scheduled sweep underneath so nothing is lost to a missed webhook.

Flow · 1 scenario

A sweep that adds each missing registrant once

A fifteen-minute Make scenario reads the registrants and the event tracker in one request, works out who is missing by set difference, and adds only them (two operations when there is nothing to do).

Set-difference idempotencyAliased GraphQL readScheduled sweep
rows backfilled in the first run
~57
per run when nothing is missing
2 ops
sweep interval
15 min
Read the case study
Flow · 3 scenarios

Owner stays blocked from an email, and the cleaning cancelled five minutes later

Owners ask for a stay at their own home through a form. Make reads the notification email, works out whether it is a new block, an edit or a cancellation, applies it in the property-management system and tells the owner.

AI as parser, not deciderToken in a data storeWait and retry
polling interval
5 min
runs, no errors recorded
8,657
tries to catch the cleaning task
3
Read the case study
Flow · 3 scenarios

A nightly records mirror that staff can build on

Three Make scenarios copy a clinic's daily activity out of its medical-records system into Airtable (patients, visits and links to diagnosis, medication and billing tables), feed a narrower copy to a follow-up team, and keep a drug-reference sheet aligned.

Day-window syncUpsert by lookupLink arrays appended by hand
modules in the nightly mirror
98
billed-item categories linked per visit
10
nightly runs in a row, all successful
16
Read the case study
Flow · 2 scenarios

Tomorrow's appointments, copied from one system into another

Two Make scenarios copy tomorrow's appointments from a medical-records system into the scheduling system, one branch per site, and backfill each patient's scheduling-system contact id by phone number.

One day, one windowMapping kept in a sheetExternal id as the copy key
sites, one identical branch each
3
modules in the appointment sync
27
scenarios, both switched off
2
Read the case study
Flow · 4 scenarios

Every call on the board, every voicemail a task

Four Make scenarios connect a cloud phone system to a CRM: every call becomes a row on a calls board, a voicemail becomes a routed follow-up task, an unknown caller becomes a lead, and an inbound text is forwarded to a person.

Event to rowPhone match with normalisingRoute by line name
call events logged, no errors
2,783
voicemails turned into tasks
127
scenarios, two proven live
4
Read the case study
Flow · 7 scenarios

Ad campaigns and posts as CRM items, metrics written back every day

Seven Make scenarios register Facebook and Google campaigns and Facebook posts as CRM items, write each one's metrics back by id every day, and mirror every lead's stage onto the same board.

Create then updatePlatform id as join keySub-items for the grain
scenarios: create, update and mirror
7
lead-stage mirrors, no errors
752
errors: two API failures, one rate limit
3
Read the case study
Flow · 4 scenarios

Which enquiries became sales: matching quotes and invoices back to the lead

Four Make scenarios log every website product enquiry with a normalised email and phone, then match the quotes that go out and the invoices that are raised in the accounting system back to the lead. The result is a lead-to-quote-to-invoice log that answers which enquiries paid.

Normalise at intakeAPI poll with If-Modified-SinceOverlapping window plus dedupe
stages linked: enquiry, quote, invoice
3
runs; five early errors, none since
523
between matching passes
4 h
Read the case study

Routing & pipelines

Following a record from the moment it is created to the place it needs to end up, resolving who and what it belongs to along the way.

Flow · 1 scenario

Filing an assessment against the right application, however it was typed

When a candidate assessment is submitted, a Make scenario finds the right candidate and the right application, files the ratings as a subitem and links everything back, with three layers of fallback for untidy form entries.

Layered fallback matchingWait for the formBack-linking
tries to find the application
3
links, for audit from either side
2-way
wait for the form to finish
30 s
Read the case study
Flow · 1 scenario

A website lead becomes a card, a record, a contact and a response clock

One Make scenario takes a website lead email, has an AI tidy it into labelled fields, posts it as a Slack card, writes the lead to Airtable and the CRM, and then escalates until a person claims it.

Fail loud heartbeatDeterministic enum mappingThread-reading response clock
routes from a single parse
4
response clock, two escalations
10 min
runs, three on a lapsed connection
31
Read the case study
Flow · 5 scenarios

From 'Apply now' to a linked, placed record in five small steps

Five Make scenarios turn an Apply-now click into an application linked to its candidate, visible to the employer and placed on the right tracker, resolving the candidate through three lookups, and placing each application exactly once.

Status-column hand-offAliased lookups with fallbackMerge and deduplicate
small scenarios, handing off through status
5
lookups to find the candidate
3
runs, two errors, one cause
93
Read the case study
Flow · 7 scenarios

One lead form, one scenario: lead-ad submissions into the CRM, once

Seven Make scenarios turn Facebook lead-ad submissions into CRM leads: each looks the lead up, notes a duplicate rather than creating one, parses the phone number, and routes eligible leads to the right owner.

One scenario per formSearch then createDuplicate becomes a note
scenarios, one per form
7
runs, no errors
286
paths: a new lead, or a note on a duplicate
2
Read the case study
Flow · 23 scenarios

Every page its own webhook: website forms into the CRM with the right course and source

Twenty-three Make scenarios take submissions from website forms (course pages, ad landing pages, a contact page) and create a CRM lead with the right source and course, plus the full questionnaire as a note.

Static label per pageCreate then routeNever auto-create labels
pages, one webhook scenario each
23
routes in the generic-page router
7
errors, all while building
5
Read the case study
Flow · 3 scenarios

A lead's reply lands in their rep's inbox, not the shared one

Three Make scenarios watch a mailbox, match each sender to a CRM lead and forward the email to the rep who owns it, and keep a first-name column filled for personalised outreach.

Match sender to recordRead the owner, don't choose itWorking-hours polling
runs in each forwarder, no errors
441
polling, working hours only
30 min
business lines, one forwarder each
2
Read the case study
Flow · 3 scenarios

When the item moves, something happens: document chasers, milestones and billable rows

Three Make scenarios act when a CRM item moves or completes: chase a prospect for the right documents by pathway, advance a course stage once its sub-items are done, and create a billable row from a completed ticket.

Trigger on a moveTemplate by pathwayTimeline as audit trail
pathways, one email template each
6
follow-up date set on each chase
2 days
runs, no errors
17
Read the case study

AI & decision support

Language models doing the reading, with arithmetic, a second opinion and a person around them, so the model is useful without being the one who decides.

Flow · 9 scenarios

An AI claims adjudicator, a blind cross-check, and a human at every gate

Nine Make scenarios take a guest damage claim from intake to the last gate before the owner's letter: Claude recommends, a second model checks it blind, and people decide, bill and sign off.

Reason then transcribeBlind cross-checkStamp-after-send idempotency
independent AI reads, the second blind
2
scenarios, intake to the final send gate
9
errors in all, on two days, all fixed
8
Read the case study
Flow · 9 scenarios

Review replies drafted by AI, graded by people, watched by a watchdog

Make scenarios turn guest-review emails into region-routed alerts, draft replies with Claude into the alert thread for a person to check, and add the grading, reporting and watchdog around them. Nothing is published automatically.

Claim then workPrompt in dataSilence means healthy
scenarios, none posting publicly
9
independent ways to grade a draft
2
silent-failure checks every six hours
3
Read the case study

Notifications & agent tools

Turning an email, an event or an agent's request into the right message in the right place, and doing it once, in the right voice.

Flow · 2 scenarios

Two inboxes, two jobs: a failed-payment alert and a branded owner email

Make scenarios read notification emails and act on them with plain parsing and no AI: a failed guest payment becomes a Slack alert that says what to do next, and a vendor's visit notice becomes a branded email to the property's owners, photos attached.

Subject line as dataLabels as memoryThread as resolution log
runs across the two scenarios
5,236
errors, all on the build day
9
Read the case study
Tool · 6 scenarios

A Slack voice for each AI agent, and a charge tool with a paper trail

Six small Make scenarios that AI agents and other automations can call: five that post to Slack under a named persona, and one that charges an owner's saved card, only after a human has confirmed it.

Identity fixed per endpointTyped on-demand interfaceErrors surface by design
Slack posters, identity fixed in each
5
runs across the six
224
idempotency key per charge, required
1
Read the case study
Flow · 2 scenarios

Appointment reminders at noon, and a catch-up pass at six

Two Make scenarios message every patient booked for tomorrow at each site: a midday run that sends and logs, and an evening pass that sends only to bookings missing from that log.

Log as the dedupe keyCatch-up passRetry then manual list
passes a day: noon and 6 PM
2
sites, one branch each
3
runs, recent scheduled runs all successful
74
Read the case study
Flow · 10 scenarios

A dispatcher and nine day-by-day SMS sequences, with the CRM as the cursor

Ten Make scenarios run timed SMS follow-up sequences: one dispatcher reads a CRM status change and routes to one of nine per-offer sequences, each of which sends the message for the current day and moves the day forward.

Dispatcher and childrenCRM as state machineFire-and-forget fan-out
scenarios: a dispatcher and nine sequences
10
messages in the longest sequence
8
Read the case study

Billing & finance

Turning a status change into an invoice and a reminder, and keeping the money side visible in the system staff already use.

Flow · 6 scenarios

A status change raises the invoice; a schedule chases it

Six Make scenarios raise and email an invoice when a CRM status changes, write the invoice back onto the record, and chase unpaid invoices on a schedule with friendly, firm and sales-toned reminders.

Status as triggerWrite the invoice backContact fallback
invoice types: recurring, enrolment, upfront
3
days from issue to due date
7
runs, one error
78
Read the case study
Flow · 3 scenarios

The invoice carries the handover: delivery packs filed, units released when paid

Three Make scenarios file everything signed at handover (the delivery note, ID, payment proofs, registration document and photos) onto the invoice in the accounting system, with the unit's VIN as its reference. When that invoice is fully paid, a prefilled release form is raised and the branches are emailed so the unit can leave.

Invoice as the document storeData store as a bridgeRetry, then fail soft
router branches per handover, each fail-soft
11
between release checks, in business hours
15 min
runs in the last 30 days
1,926
Read the case study

Compliance & operations

Recurring obligations (sign-offs, vendor paperwork) sent, chased and filed without someone holding the calendar in their head.

Flow · 3 scenarios

Vendor onboarding packets: sent with a token, chased on a cadence, filed for review

Make scenarios email each eligible vendor a personal onboarding link, remind them at fixed intervals, and when the signed packet comes back, match it to the vendor, file it and log every document for a person to review.

Tokenised linkCadence as a formulaFind or create
scenarios: send, remind, collect
3
reminders, at 7, 14, 21 and 28 days
4
document types logged per packet
6
Read the case study
Flow · 3 scenarios

A monthly sign-off loop that files its own evidence

Three Make scenarios email each active staff member a pre-filled compliance form on the first of the month, file the signed PDF as evidence when it comes back, and chase anyone still unsigned on the fifth.

Status as state machineIdentity in the linkDual evidence storage
scenarios: send, collect, remind
3
acknowledgements captured per signature
5
places the evidence is filed
2
Read the case study
Flow · 1 scenario

Filing a signed document in the right folder, and never losing it

When a lease is signed, a Make scenario finds the signed PDF, files it in the right region and property folder in Google Drive, logs it in Airtable and tells the team in Slack, and if it cannot find the folder, it files the document in a holding folder and says so.

Tiered fallbackResolve by nameWait for the file
tiers of fallback, so nothing is lost
3
wait for the signed file to land
10 s
Read the case study
Flow · 8 scenarios

A vendor compliance lifecycle, from review to renewal

Eight Make scenarios take a vendor from a submitted packet through review, cure and approval, watch their documents for expiry, close the annual cycle, reconcile payments and block new work for anyone who lapses, never their invoices.

One status vocabularyNotices on exact daysBlock new work, never payment
scenarios, built as one cycle
8
expiry stages: 60, 30, 15 days, then day 0
4
Read the case study

Onboarding & access

Turning an approval into the right seat, the right team and the right boards, without somebody doing it by hand.

Flow · 8 scenarios

Approving a person should give them the right seat, team and boards

Eight Make scenarios turn an approval or a status change into a guest invitation, the right team memberships and the right boards: for candidates on several tracks, for the organisations that refer them, and for employers.

Direct API where the module stopsBreak and retryTeam-scoped access
scenarios across three audiences
8
boards per provider team
4
reconciliation sweep interval
12 h
Read the case study

Every figure on these pages is read from the scenarios’ own run history, and each page says what is switched off or has not yet run. Looking for the wider portfolio of systems? See all work.

Page copy drafted with AI assistance. Skofi is accountable for it. Editorial policy

Start here

Tell us about the process that keeps costing you.

A 15-minute call is usually enough to say whether this is an automation, an integration, or something that should be built, and whether we are the right people for it.

Book a 15-minute callsaveez@skofi.tech

What happens on the call

  • 15 minutes, no deck
  • We map the process on the call
  • A written scope, or an honest no
Book a call