Node-RED + Atendalia
Node-RED helps you branch appointments by location.
- Type
- Third-party automation
- Data direction
- Atendalia → Node-RED
What information is shared?
Depending on the notification and what this connection supports, it can send the name, phone, service, date, time, and location. Choose the notifications you need and review the example before connecting real customers; it does not send a complete copy of your business.
Do I need Zapier or another account?
This connection does not require Zapier or Make. You need your own system or server to receive alerts. It can avoid an automation subscription, but hosting and maintenance are your responsibility.
Who it is useful for
Businesses already using Node-RED that want to connect their customer service with that tool.
How information flows
For example: Branch appointments by location. Update a tool not listed in the catalog. Add validation before another action runs.
Practical use cases
- Branch appointments by location.
- Update a tool not listed in the catalog.
- Add validation before another action runs.
View connection steps and technical details
What your Node-RED receives every time an appointment is booked
Your AI phone assistant answers the call, books the appointment in your calendar and sends it to Node-RED. You choose what we notify you about:
- New appointment
- Appointment moved
- Appointment cancelled
- Call ended
- chat.handoff_creado
- chat.handoff_respondido
- contacto.bloqueado
- contacto.desbloqueado
Depending on the notification and connection, it can include: Customer name · Phone · Service · Date and time · Branch · Notes · Table or space.
How to connect it
- 1Hire your assistant at atendalia.com.mx/signup and forward your business calls. Nothing to install.
- 2In your dashboard, open Integrations → Add and choose Node-RED.
- 3The address of your Node-RED "http in" node (POST, must start with https://).
- 4Hit Test: Node-RED receives a sample notification instantly, with the real look of every appointment.
Requirements and permissions
url— endpoint or webhook URL
Relevant limits
- This adapter sends outbound events; Node-RED does not automatically read calendar availability.
- A Debug node does not acknowledge HTTP delivery. Include HTTP Response instead of leaving the request open.
- The endpoint must be publicly reachable and verify the event signature before executing actions.
- Only the events listed above are sent. The connection is one-way and does not import changes made directly in Node-RED.
What an appointment looks like when it arrives
Your system receives the same event as signed JSON:
{
"evento": "cita.creada",
"negocio": { "nombre": "Tu Negocio" },
"cita": {
"inicia": "2026-09-10T17:00:00",
"termina": "2026-09-10T17:30:00",
"servicio": "Corte",
"estado": "confirmada",
"canal": "llamada",
"cliente": { "nombre": "Ana", "telefono": "+52 81 1234 5678" },
"sucursal": { "nombre": "Centro" },
"notas": "Viene por LinkedIn"
}
}How to verify and troubleshoot
- Deploy an HTTP In → Debug → HTTP Response flow and copy its public HTTPS URL.
- Send a test from Atendalia and inspect evento, cita, and cliente in msg.payload.
- Check the HTTP response before adding event and location filters.
- Use “Test” in the dashboard and check the result in Node-RED before enabling real events.
- If you see 401 or 403, review the token, its validity and the provider permissions.
- If no data arrives, review the integration log and confirm that the event is enabled.
Specific questions
Can Node-RED change my Atendalia appointments?
No. This connection sends information in one direction only.
Can I test it without affecting a call?
Yes. The test starts from Integrations and does not open or modify an assistant call.
Hear your assistant answering for real
Call it now and hear how it books an appointment — then review how to connect it with Node-RED.
More automation
Explore all 167 connection guides · Atendalia: AI phone assistant that books appointments for businesses in Latin America.