SERVICES / PLATFORMS / MAKE

Make scenarios built to survive real data

Make is where I build anything with real branching — multiple document types, multiple suppliers, multiple outcomes from one trigger. It handles complexity better than anything else at the price, provided the error handling is done properly.

INTO MAKEOUT OF MAKEInbound emailWeb formStore orderScheduled runWebhookCloud storageDatabase recordMessagingAny REST APIMakeROUTE · ITERATE · AGGREGATE
Typical Make flows from real builds, simplified.
COMMON REQUESTS

What people ask me to build

These come up repeatedly. If yours isn’t listed, it’s usually still possible — describe it and I’ll tell you honestly.

BRANCHING

Routers that isolate failure

Each supplier, document type or region on its own route, so one broken case can’t stop the other five.

DOCUMENTS

Files sorted without a human

Attachments identified, converted, renamed, filed and logged — the pipeline that gave an accounting firm nine hours a week back.

AI IN THE FLOW

Generated content with a human gate

Drafts produced automatically, then held until someone approves them. Nothing publishes on its own.

RATE LIMITS

Built to stay under the ceiling

Deliberate pacing where a platform caps requests per minute, so a burst doesn’t fail half your records.

AGGREGATION

Many records into one output

Line items collected into a single invoice, report or CSV rather than firing one operation per row.

CUSTOM MODULES

Whatever Make doesn’t list

HTTP modules against any REST API, with authentication, pagination and retries handled properly.

WHERE IT GETS DIFFICULT

The part that isn’t in the documentation

A document pipeline for an accounting firm: attachments arrive in Outlook, get identified by supplier, converted where needed, filed into the correct cloud folder and written to a database. Each supplier format runs on its own branch with its own error handler, and anything missing a required field is held for review rather than filed wrongly. The build took longer than a single happy path would have. It has also never needed rescuing.

Most Make scenarios that break were built as one long chain. Branching costs more up front and far less later.

QUESTIONS

Make specifics

How many operations will my scenario use?

It depends on structure more than volume. A badly shaped scenario can burn ten times the operations of a well-shaped one doing the same work — aggregators and filters placed early make most of the difference.

Can Make replace my Zapier setup?

Often, and usually more cheaply at volume. Whether it’s worth migrating depends on how many Zaps you have and how much they cost you today.

Do you document what you build?

Yes, as standard. A scenario nobody understands is a liability the day something changes.

RELATED

Often built alongside

What should Make be doing that it isn’t?

Describe it in a paragraph. I’ll tell you what it would take — or tell you honestly it isn’t worth it.

Book a 30-minute call