Your software
File 2481
- Status
- Confirmed
- Scheduled date
- 24 September
- Balance due
- €180.00
- Margin
- Closed
- IBAN
- Closed
Reread just now
The collaborator reads your records and answers on its own.
Connect it through its API, or describe it by hand if it publishes none.
It reads, answers, follows up and collects payment. Beyond its mandate, it asks you.
Your software
File 2481
Reread just now
What you do not tick does not exist for it. Writing into your software is born switched off.
Whatever discovery finds arrives switched off. You tick, field by field.
Sensitive fields stay closed, and masked in the logs.
A write needs a human's approval. The collaborator never gives it to itself.
One thread per customer, whichever way they write.
The heart of it: the moment, and a number that is enough to recognise your customer.
Your current inbox, for attachments and records. The same collaborator answers there.
After 24 hours without a message from your customer, WhatsApp only accepts a template approved by Meta. You write and submit them from the console.
The console shows what it settled on its own and what is waiting for you. Step in whenever you want.
Your software connects through MCP, OpenAPI or GraphQL. It calls Nodium with a key and receives signed webhooks.
# Notify a customer: the call decides, it sends nothing.POST https://nodium.io/api/v1/templates/outboundAuthorization: Bearer nod_••••••••Content-Type: application/json{ "externalId": "reminder-2481", "eventType": "appointment.tomorrow", "phone": "+33 6 00 00 00 00", "templateName": "appointment_reminder", "payload": { "reference": "2481" }}Start with the free plan. Writing stays off until you switch it on.