Automation / No-Code
Make.com Automation Agent — Forms → API → Gmail
RRRTX Labs — Public Demo & Blueprint
At a glance
3-module scenario: Sheets → HTTP → Gmail · Scheduled polling trigger · Public LinkedIn demo · Blueprint published for reuse
The challenge
Every business captures enquiries through forms — and most of those submissions die in a spreadsheet nobody opens until Friday. The gap between “form submitted” and “someone actually acts on it” is where leads go cold. The obvious fix is a Make.com scenario, but in practice these are built once, in a hurry, and never maintained: no documentation, no error handling, no blueprint for the next person. When the scenario breaks, nobody knows how it was wired.
The system
We built and publicly demoed a compact automation agent that closes the loop. The scenario — exported as a reusable, documented blueprint — is three modules wired end-to-end: A Google Sheets trigger watches form responses as they land in the sheet, polling on a schedule so no submission waits for a human. Each new row is passed to an HTTP module that calls an external API to process the response — the pluggable brain of the agent, swappable per integration. The outcome is delivered by Gmail straight to the inbox where action actually happens. The demo is public — introduced on LinkedIn as “I am a Make.com agent” — and the complete scenario blueprint is published in an open Drive folder, so anyone can import it into their own Make account, read exactly how it is wired, and extend it. That is the standard we hold ourselves to: automation shipped like production software, with documentation as part of the deliverable, not an afterthought. And when a client's volume outgrows Make's per-operation pricing, there is a migration path: the same pipeline re-implemented as a self-hosted Python automation — fixed monthly server cost instead of a metered bill, on infrastructure the client owns.
The result
A working, publicly demoed Make.com agent with a published, importable blueprint — the loop from form submission to API processing to email notification runs with no one checking a spreadsheet, and the wiring is documented for the next person to run and extend. The blueprint is the deliverable we hand to every automation client: import it, read it, own it. No black boxes. For teams that outgrow per-operation pricing, the migration path to self-hosted Python turns a growing variable cost into a small fixed one — the same shift from rental to ownership we apply across every system we build.
Have a system like this to improve?
Start with the problem, constraints, and outcome. We will map the safest next step.
Discuss Your Project