Benjamin

AI Automation Expert

EMAK Solution • Freelance

Aug 2026 - Sep 2026 • 1 mo

What I built: A 17-module production scenario that identifies the source form and runs the correct sequence for it: Webflow watches all form events on the site. A Router with three filtered routes inspects each submission and identifies which form it came from (Footer, Form Prelaunch/Redemption, Boîte à idées). Route 1 & 2 each run a full four-step chain: log the entry in Coda, notify the team in Slack, send a tailored Gmail response to the submitter, and add the contact to the correct MailerLite Classic subscriber group. Route 3 (idea submissions) runs an abbreviated chain — Coda, Slack, Gmail — deliberately skipping the mailing list, since idea submitters hadn't opted into marketing. Why it was tricky: Consent handling was the design constraint: it would have been easier to add everyone to MailerLite, but only two of the three forms carried marketing opt-in. The scenario respects that distinction at the routing level. The build also runs on Webflow's deprecated watch trigger, which I've since scoped for migration. Result: Three separate form workflows run from a single scenario, each with its own logging, notification, autoresponder and list-management behavior — and the client's mailing list only contains contacts who actually opted in.

Make.com Specialist

RE-NETWORK • Freelance

Jul 2026 - Aug 2026 • 1 mo

What I built: A single scenario triggered by new and edited Survey123 submissions, split by a Router into three independent paths: Applicant acknowledgement — an automated confirmation email sent to the applicant the moment a submission lands. Sanitary Board notification with dynamic attachments — a second Router evaluates how many photos the applicant uploaded and sends down one of four branches: no attachments, one, two, or three. Each branch pulls the images from their hosted URLs via HTTP modules before building the outbound email, so the Board always receives the correct set of files with nothing missing or duplicated. Feature report generation — on edited records, the scenario fetches the feature layer attributes, parses the returned payload with a JSON module, triggers report creation, retrieves the finished document over HTTP, and emails it out as an attachment. Why it was tricky: Survey123 returns attachments as references, not files, so the images had to be retrieved individually and mapped into the right email slot. The conditional attachment logic was the core of the build — one generic branch would have produced broken or empty emails. Result: Applications are acknowledged instantly instead of within a day or two, the Sanitary Board receives complete, correctly-attached submissions with zero manual file handling, and report generation on edits is fully hands-off.

Make.com Automation Consultant

Roasty Coffee • Freelance

Jul 2026 - Jul 2026 • 0 mos

What I built: A resilient ingestion scenario running every 2 minutes: Tools — Set Multiple Variables builds the request parameters at the start of each run (dynamic date ranges, pagination values, API keys), so the request adapts to each execution instead of being hardcoded. HTTP — Make a Request calls the API endpoint with those variables. Google Sheets — Add a Row writes the returned records, handling up to 100 bundles per run so multi-record responses are written in full rather than just the first result. Catch all → Ignore error handlers are attached to both the Tools and Google Sheets modules. When a run hits an API failure, malformed response or write error, that execution is logged and skipped cleanly — the schedule keeps running and the next cycle recovers. Why it was tricky: Most scenarios are built for the happy path. This one is built around what happens when the API misbehaves — which, on a 2-minute schedule, is a question of when, not if. The error routes are what turn it from a demo into something that runs unattended. Result: A self-recovering data pipeline that ingests API records around the clock without manual restarts, and without a single bad response taking the whole scenario offline.