Live automation
A new lead comes in, gets scored on its own, and you have a reply ready to send.
Live. Uses the AIM API.
What your client sees
- The problem it solves
- Leads come in through the form at any hour, and going through them one by one takes time. Meanwhile, the most urgent client waits like everyone else and may go elsewhere.
- A real-life example
- Picture a remodeling company. A request comes in with a good budget and in a hurry. It gets marked as hot, with a call suggested within 24 hours and the reply email already drafted.
- What you'll see
- You pick who's writing to you, send their request and see, side by side, what the workflow does with it and what would reach you, with the reply already drafted. Nothing is sent or saved.
Under the hood
What it does, in technical terms
Send a test request and watch, step by step, how a workflow designed in n8n validates it, scores it, picks a route, drafts the reply and records it.
- Technologies
- n8n
- Cloudflare
- SSE
- Hono
- Backed by
Architecture
1.Designed in n8n
The workflow is built and tested in n8n and exported as JSON to the repository. The business rules live in its "Reglas del flujo" (workflow rules) node.
2.Turnstile
Every run goes through the security check, with a single-use token.
3.The edge on Cloudflare (Hono)
It runs the workflow in memory with the rules from that JSON and sends each step via Server-Sent Events. Nothing is sent or saved.
4.Parity with real n8n
The tests compare each step with what n8n returned for the same test leads, and with the workflow's fingerprint.
By the numbers
- the workflow takes on the edge
- < 1 ms
- from click to result, the demo's goal
- < 2 s
- test leads recorded with real n8n
- 11
- steps in the workflow
- 7
The code
Decisions
- DEC-023: The workflow runs on Cloudflare and n8n is for designing it (opens in a new tab)
- DEC-021: Live automation with n8n on Render (replaced) (opens in a new tab)
Recorded in docs/DECISIONES.md (in Spanish), with their context and the alternatives ruled out.
What it shows
- Designed in n8n: the workflow is built and tested in n8n and exported as JSON to the repository. The site reads its rules from that file.
- Fast: the site's API, on Cloudflare, runs it in milliseconds, with no server to wake up, and sends you each step with Server-Sent Events.
- Tested against real n8n: the tests compare each step with what n8n returned for the same test contacts.
- Nothing is saved: your request is processed in memory and the email the workflow drafts is never sent.
- Bot protection: every run goes through the Turnstile security check.
See the n8n workflow on GitHub (opens in a new tab): it's the JSON exported from n8n that the site takes its rules from.
Who's writing to you today?
Pick a case and send its request: the real workflow handles it right away.
Moment 1: Your client writes on your website
They fill in the contact form. Here you send it yourself, with one of the sample cases.
- Name
- Emily Carter
- Company
- Blue Harbor Coffee
- [email protected]
- Service
- Automations
- Budget
- $500 to $2,000
- Timeline
- In under 2 weeks
- Message
- We want the orders that come in through WhatsApp to go into a spreadsheet on their own, and the team to get an alert with every new order.
Moment 2: Your automation works on its own
The rules check the details, score the lead hot, warm or cold and decide what comes next.
The request comes in. pending.
Waiting for your client to send it.
It gets checked. pending.
That the details are complete and look real.
It gets scored. pending.
Based on the budget, the timeline, the service, the email and the message.
It picks the next step. pending.
A call, a proposal or helpful content, depending on the priority.
It writes the reply and records it. pending.
A different email for each type of client.
Moment 3: What reaches you
An alert with the lead already scored and the reply email drafted, ready to send.
This is where you get an alert when a lead worth your time comes in.
Test request
Fill in the form as if you were a client. The workflow validates the request, scores it, picks a route, drafts the reply and records it.
Use test data: the email isn't sent, it's only shown. The request is processed in memory and isn't saved. Privacy policy.
There are 3 examples: high priority, medium priority and a request the workflow rejects.
Workflow run
Each step shows up with the time it took since the workflow started.
Step 1: Received. Pending.
The site's API receives the request.
Step 2: Validated. Pending.
Checks the business rules.
Step 3: Scored. Pending.
Adds points for budget, timeline, service and detail.
Step 4: Routed. Pending.
Decides what comes next and how soon.
Step 5: Reply drafted. Pending.
Writes the reply email. It isn't sent.
Step 6: Recorded. Pending.
Saves the request with a reference.
Step 7: Done. Pending.
The workflow returns the result.
Want it for your business?
This is part of what I build in the automations service. See what's included or get a reference estimate for your case.
Curious how it is built? Look under the hood
How it works
The workflow is designed and tested in n8n, then exported as JSON to the repository. This site’s API, on Cloudflare, checks that you’re human, runs the workflow in memory with the rules from that file and sends you each step with Server-Sent Events. The workflow takes less than a millisecond, and there’s no server to wake up.
The business rules live in a node of the workflow in n8n: what counts as a business email, how many points each budget adds and which reply each type of client gets. They’re changed there and exported, without touching the site’s code. The tests compare each step with what n8n returned for the same test contacts, so the site can’t drift from the workflow without it showing.
Use test data: your request is processed in memory and not saved, and the email isn’t sent: it’s only shown.