Autonomous agents
Automating means connecting systems so one action triggers the next without intervention: a booking comes in, it gets confirmed, scheduled, reminded, and the review gets requested.
Each card is a workflow: a trigger and the actions that follow on their own.
new message → agentThe inquiry gets an answer in seconds; whatever the agent can't solve goes to the team.reserva.creada → confirm → remindThe customer's reply to the buttons updates the schedule.Meta lead → CRM → alert to salespersonThe contact comes in with its source and the salesperson gets the alert within seconds.quote sent + 48 h → messageIf there was no reply, a message with the most common question or the price expiration.failed payment → notice + new linkThe customer gets a new link, and the team is only notified if that one isn't paid either.payment → CFDI → emailIn Mexico, the electronic invoice can be issued through an API with an authorized provider, using the details the customer left in the chat.last visit > 90 days → messageA specific reason to come back, sent to people who agreed to receive messages.Monday 9 a.m. → reportBookings, sales by channel, no-shows and hours saved, by email or in a team group chat.Count how many times a week each task repeats and how many minutes it takes. In the sample dashboard: 640 initial replies of about 1 minute each add up to 12 hours a week.
Recommendation. Automate what is frequent and simple first. What is rare and complex stays with a person.
A webhook notifies you the moment something happens. Checking a system every 15 minutes adds delay and spends runs when nothing changed.
Recommendation. Use a webhook whenever the system offers one; periodic checks only as a backup.
Webhooks sometimes arrive twice. Each event carries an identifier and, if it was already processed, it is ignored. That way nobody gets two confirmations or is charged twice.
event pago_confirmado · evt_3Pq8 · booking R-2291
processed? yes, at 14:02:11
action ignore: no second message and no second recordIf an API doesn't respond, the workflow retries with increasing waits: 1, 5 and 30 minutes. If it fails all three times, it alerts a person with the data that didn't go through.
Recommendation. Each workflow has a named owner who receives its alerts.
All three platforms connect tools without coding everything from scratch. The choice depends on volume, logic and where the data has to live.
| Criterion | Zapier | Make | n8n |
|---|---|---|---|
| How it charges | Per task | Per credit (formerly "operation") | Per execution; free when self-hosted |
| Ready-made integrations | |||
| Branches, loops and complex logic | |||
| Custom code inside the flow | |||
| Self-hosting | |||
| Best for | A few steps across many apps | Visual flows with several branches | High volume, sensitive data and agents |
● yes · ◐ partly · ○ no. When the business's own tool already includes the automation (for example, reminders from the booking system), we use that and avoid adding another piece.
| Industry | First workflow | Second workflow |
|---|---|---|
| Restaurant | Booking confirmation and reminder | Review request after the visit |
| Hotel | Initial reply and quote | Pre-arrival information and transfer |
| Clinic or aesthetics | Reminder with required confirmation | Follow-up appointment based on the treatment |
| Online store | Failed payment or abandoned cart | Shipping notice and review request |
| Professional services | From the form to the CRM with an alert to the salesperson | Quote follow-up |
Active workflows
| Workflow | Runs | Hours |
|---|---|---|
| First reply to messages | 640 | 12 h |
| Confirmation and reminder | 210 | 6 h |
| Inquiry follow-up | 180 | 5 h |
disparador: reserva.creada
pasos:
- whatsapp: { plantilla: confirmacion_reserva, cuando: inmediato }
- calendario: { crear_evento: recepcion }
- whatsapp: { plantilla: recordatorio_24h, cuando: "inicio - 24h" }
- si_responde: { "cambiar": enviar_enlace_reprogramar }
- email: { plantilla: pedir_resena, cuando: "fin + 3h" }Outside the 24 hours after the customer's last message, WhatsApp only allows templates approved by Meta. That is why the confirmation and the reminder are templates.
Case analysis
The network of 390 dental clinics sent SMS reminders that almost nobody answered, and manual confirmation overwhelmed the teams.
Why it worked. The patient handles everything with one tap, in the app they already open every day.
Analysis of a public case. North Marketing did not take part in this work. The figures are self-reported on the WhatsApp Business case studies page.
Sources: WhatsApp Business
30 minutes to see where your business is losing customers and what to do first. If you don’t see results in 30 days, we give your money back.
Book your diagnosisWe’ll message you on Instagram with times.