Notification Channels

Configure notification channels for email, WhatsApp, and in-app with multi-language support.

When to use this

Configure notification channels when you need your team to receive alerts about assigned tasks, equipment alarms, or status updates. Each channel has different strengths: choose the right one based on urgency and context.

Decision tree: which channel to use

Situation	Recommended channel	Reason
Formal notification, needs attachment or record	Email	Full traceability, supports documents
Urgent alert, field technician, mobile	WhatsApp	Immediate delivery, high read rate on mobile devices
Dashboard user, non-urgent update	In-App	No external interruptions, latency < 1 second
Critical equipment alarm	WhatsApp + Email	Dual channel to guarantee message delivery
Weekly SLA compliance report	Email	Extended format with tabular data

Real-world example: A compressor triggers a critical alarm at 3:00 AM. The system sends a WhatsApp notification to the on-call technician (because it needs immediate field attention) and an email to the supervisor (for the formal record when they arrive at the office).

Overview

Rela AI supports three notification channels to keep teams informed. Each notification is sent through configured channels based on tenant and user preferences.

Channel	Provider	Typical latency
Email	Postmark	< 5 seconds
WhatsApp	Evolution API	< 3 seconds
In-App	Ably (real-time)	< 1 second

Email (Postmark)

Email notifications use Postmark as the transactional email provider.

Subject and body templates

Each notification type has templates in all 3 supported languages:

{
  "template_id": "task_assigned",
  "subject": {
    "es": "Nueva tarea asignada: {task_title}",
    "en": "New task assigned: {task_title}",
    "it": "Nuovo compito assegnato: {task_title}"
  },
  "body": {
    "es": "Se te ha asignado la tarea '{task_title}' con prioridad {priority}.",
    "en": "You have been assigned the task '{task_title}' with priority {priority}.",
    "it": "Ti è stato assegnato il compito '{task_title}' con priorità {priority}."
  }
}

Variables within curly braces {variable} are dynamically replaced at send time with the actual notification data.

Postmark configuration

The Postmark server is configured at the tenant level with the corresponding server_token.

WhatsApp (Evolution API)

WhatsApp notifications are sent through Evolution API, which connects to a WhatsApp Business instance.

Message templates

{
  "template_id": "alarm_triggered",
  "message": {
    "es": "Alarma activada en {asset_name}: {alarm_message}. Severidad: {severity}.",
    "en": "Alarm triggered on {asset_name}: {alarm_message}. Severity: {severity}.",
    "it": "Allarme attivato su {asset_name}: {alarm_message}. Gravità: {severity}."
  }
}

The recipient's WhatsApp number must be verified and in international format (e.g., +56912345678). Numbers without country code will be rejected.

In-App

In-app notifications appear in real-time within the dashboard.

Components

Bell icon in the header with unread badge
Dropdown with list of recent notifications
Navigation to the related resource on click

Real-time updates

In-app notifications are delivered via Ably, ensuring instant delivery without needing to refresh the page.

Language resolution

The notification language is resolved in the following order:

User language preference (if configured)
Tenant language (general configuration)
Spanish (default fallback)

Results tracking

Each sent notification records its result per channel:

Status	Description
`sent`	Successfully delivered to the provider
`failed`	Send error (reason is recorded)
`pending`	In send queue
`skipped`	Channel not configured for the user

GET /api/v1/notifications/{notification_id}/results

The response includes the status for each attempted channel, send timestamp, and error message in case of failure.