Notifications - AutoLog

Overview

AutoLog’s Notification System provides a powerful, event-driven architecture for sending automated emails and alerts. The system consists of three main components: Events, Groups, and Templates.

System Architecture

How Notifications Work

Event Occurs

An action happens in AutoLog (e.g., vehicle checkout, maintenance due)

Event Triggers

The system identifies the event type and its severity

Groups Identified

Assigned notification groups for this event are located

Template Selected

The appropriate template (by event, channel, locale) is chosen

Notification Sent

Email/message is composed and sent to all group members

All three components (Events, Groups, Templates) must be properly configured for notifications to work.

Dashboard Overview

The Notifications Dashboard provides real-time metrics:

Key Performance Indicators

Today’s Notifications

Total notifications sent today
Resets at midnight
Useful for monitoring activity volume

Sent Successfully

Count of delivered notifications
High percentage indicates healthy system

Failed

Notifications that couldn’t be delivered
Investigate if this number is high

Suppressed

Messages blocked by filters or user preferences
Normal for opt-out compliance

Average Time

Time from trigger to delivery (in seconds)
Lower is better (target: <5 seconds)

Dashboard metrics update in real-time as notifications are processed.

Recent Notifications Table

Displays the most recent notification activity: Columns:

ID: Unique notification identifier
Event: Which event triggered it
Severity: Priority level (Low, Medium, High, Critical)
Status: Delivery state (Delivered, Sent, Failed, Pending, Queued)
Date: When the notification was sent

Status Meanings:

Delivered: Confirmed received by recipient
Sent: Handed off to email provider
Failed: Delivery error occurred
Suppressed: Blocked by rule or preference
Pending: Waiting to be processed
Queued: Scheduled for future sending

Click the filter icon to narrow the notification history by event type, status, or date range.

Events & Routing

What are Events?

Events are triggers that cause notifications to be sent. Each event represents a specific action or condition in AutoLog. Example events:

VEHICULO_SALIDA: Vehicle checked out
VEHICULO_REGRESO: Vehicle returned
MANTENIMIENTO_PENDIENTE: Maintenance due
RESERVA_CREADA: Reservation made
ACTIVO_MOVIDO: Asset moved

Event Properties

Clave (Key)

Unique identifier in UPPERCASE_SNAKE_CASE
Used by code to trigger events
Cannot be changed after creation

Nombre (Name)

Human-readable event description
Displayed in UI and reports

Descripción (Description)

Detailed explanation of when event occurs
Helps administrators understand purpose

Severidad por defecto (Default Severity)

Priority level: Low, Medium, High, Critical
Can be overridden when event is triggered
Affects visual styling and urgency

Estado (Status)

Active: Event can trigger notifications
Inactive: Event is disabled, no notifications sent

Grupos asignados (Assigned Groups)

Number of notification groups configured to receive this event
Click to manage group assignments

Creating an Event

Open Event Manager

Navigate to Notifications > Events & Routing

Click 'New Event'

Button in top-right of the event list

Fill Event Details

Clave: Unique key (e.g., CUSTOM_EVENT_NAME)
Nombre: Display name
Descripción: What triggers this event
Severidad: Default priority level
Activo: Toggle to enable immediately

Save Event

Click “Save” to create the event

Assign Groups

After creation, click the Groups icon to assign notification recipients

Event keys cannot be changed after creation. Choose carefully and follow naming conventions.

Editing Events

Find the event in the list
Click the edit (pencil) icon
Modify properties (except clave)
Save changes

Activating/Deactivating Events

Toggle events on/off without deleting:

Click the toggle switch icon next to the event
Confirm the status change
Red toggle = Inactive, Green = Active

Deactivating an event stops all notifications for that event but preserves configuration for future reactivation.

Assigning Groups to Events

Open Group Assignment

Click the Users icon in the event’s action column

Select Groups

A modal shows all available groups:

Checkboxes indicate current assignments
Search to filter groups
Select/deselect as needed

Save Assignments

Click “Save” to apply changes

Events can have multiple groups assigned. All members of assigned groups will receive notifications when the event triggers.

Deleting Events (Soft Delete)

Click the trash icon next to the event
Confirm deletion
Event is marked inactive and hidden from normal view
Can be restored by administrators if needed

Notification Groups

Groups define who receives notifications for specific events.

Group Structure

Group Properties:

Nombre (Name): Group identifier
Descripción (Description): Purpose of the group
Activo (Active): Whether group is enabled
Miembros (Members): Users who receive notifications
Canales (Channels): Delivery methods enabled

Creating a Group

Navigate to Groups

Notifications > Groups tab

Click 'New Group'

Opens the group creation form

Set Group Details

Name: Descriptive name (e.g., “Fleet Managers”, “Maintenance Team”)
Description: Who should be in this group and why
Active: Enable the group

Save Group

Click “Save” to create the group

Add Members

After creation, add users who should receive notifications

Managing Group Members

Adding Members

Open the group details
Click “Add Members”
Search for users by name or email
Select users to add
Save changes

Members receive notifications for all events assigned to this group.

Removing Members

Open the group member list
Click the remove icon next to the user
Confirm removal

The user stops receiving notifications immediately.

Channel Configuration

Groups can use multiple notification channels: Email

Most common channel
Sends to user’s registered email address
Supports HTML templates

SMS (if configured)

Text message notifications
Requires phone numbers in user profiles

Push (if configured)

In-app push notifications
Requires mobile app installation

To enable additional channels, contact your system administrator. Email is enabled by default.

Email Templates

Templates define the content and format of notification emails.

Template Structure

Each template consists of: Evento (Event)

Which event this template is for
Example: VEHICULO_SALIDA

Canal (Channel)

Delivery method (usually “email”)

Locale

Language code (es, en, etc.)
Allows multilingual notifications

Asunto (Subject)

Email subject line
Supports placeholders like {{empleado_nombre}}

Cuerpo (Body)

Email HTML content
Full HTML support for rich formatting
Uses placeholder syntax for dynamic data

Metadata

Additional configuration (JSON format)
default_payload: Default values for placeholders
subject_prefix: Prefix for all subjects (e.g., “[FLOTA]”)

Estado (Status)

Active: Template can be used
Inactive: Template is disabled

Es default (Is Default)

Whether this is the default template for the event/channel/locale combo
Only one template can be default per combination

Creating a Template

Open Template Editor

Navigate to Notifications > Templates

Click 'New Template'

Opens template creation wizard

Specify Template Key

Enter the event clave (e.g., VEHICULO_SALIDA)

Design Subject

Write the email subject:

Vehículo {{vehiculo_placa}} ha sido retirado

Design Body

Create the HTML email body:

<p>Hola {{empleado_nombre}},</p>
<p>Has retirado el vehículo <strong>{{vehiculo_placa}}</strong> ({{vehiculo_marca}} {{vehiculo_modelo}}).</p>
<p>Fecha de salida: {{fecha_salida}}</p>
<p>Por favor, devuelve el vehículo al finalizar tu jornada.</p>

Configure Metadata (Optional)

Add JSON configuration:

{
  "subject_prefix": "[FLOTA] ",
  "default_payload": {
    "empresa": "Tecnasa"
  }
}

Save Template

Click “Save” to create the template

Using Placeholders

Placeholders are replaced with actual data when notifications are sent: Syntax: {{variable_name}} Common placeholders:

{{empleado_nombre}}: Employee name
{{vehiculo_placa}}: Vehicle license plate
{{vehiculo_marca}}: Vehicle make
{{vehiculo_modelo}}: Vehicle model
{{fecha_salida}}: Checkout date/time
{{fecha_regreso}}: Return date/time
{{link_detalle}}: Link to details

Nested placeholders: {{cliente.nombre}} for nested objects

The template editor automatically detects placeholders in your content and displays them in a chip list for reference.

Template Preview

Test your template before using it:

Enter Test Data

In the “Payload de prueba” section, provide JSON with sample values:

{
  "empleado_nombre": "Juan Pérez",
  "vehiculo_placa": "HAA-1234",
  "vehiculo_marca": "Toyota",
  "vehiculo_modelo": "Corolla",
  "fecha_salida": "2024-03-15 09:30"
}

Click 'Previsualizar'

System renders the template with your test data

Review Output

Check:

Subject line formatting
All placeholders replaced correctly
HTML renders properly
Links work

Adjust and Re-preview

Make changes and preview again until satisfied

Local vs Server Preview

Toggle between preview modes: Local Preview

Renders in browser using JavaScript
Instant results
Good for quick checks
May not reflect server-side logic exactly

Server Preview

Renders on server (same as production)
Accurate representation
Includes metadata processing
Slightly slower

Use server preview for final validation before publishing a template.

Sending Test Emails

Configure Test Payload

Ensure your test data is complete and valid JSON

Click 'Enviar prueba'

Button in the actions panel

Enter Email Address

Provide the recipient email for the test

Send

Confirm to send the test email

Check Inbox

Verify the email arrived and looks correct

Test emails use real email infrastructure. Don’t send tests to customer email addresses.

Publishing Templates

Once a template is ready for production:

Click “Publicar como default”
This makes it the active template for the event/channel/locale combination
All notifications for that event will use this template

Publishing automatically unpublishes the previous default template.

Template Metadata

Metadata enhances template functionality with JSON configuration: subject_prefix

{
  "subject_prefix": "[AUTOLOG] "
}

Adds a prefix to all email subjects automatically. default_payload

{
  "default_payload": {
    "empresa": "Tecnasa",
    "soporte_email": "[email protected]"
  }
}

Provides fallback values for placeholders not in the event payload. custom_config

{
  "reply_to": "[email protected]",
  "cc": ["[email protected]"],
  "priority": "high"
}

Additional email headers and settings.

Keep metadata minimal. Only add what’s necessary for the template to function.

Notification Workflow Example

Scenario: Vehicle Checkout Notification

Employee Checks Out Vehicle

User scans QR code or completes checkout form for vehicle HAA-1234

System Triggers Event

AutoLog fires VEHICULO_SALIDA event with payload:

{
  "empleado_nombre": "Ana García",
  "empleado_email": "[email protected]",
  "vehiculo_placa": "HAA-1234",
  "vehiculo_marca": "Toyota",
  "vehiculo_modelo": "Corolla",
  "fecha_salida": "2024-03-15T09:30:00Z"
}

Groups Retrieved

System finds groups assigned to VEHICULO_SALIDA:

“Fleet Supervisors” group
“Vehicle Checkout Recipients” group

Template Selected

Gets the default template for:

Event: VEHICULO_SALIDA
Channel: email
Locale: es

Email Composed

Template placeholders are replaced:Subject: [FLOTA] Vehículo HAA-1234 ha sido retiradoBody:

<p>Hola Ana García,</p>
<p>Has retirado el vehículo <strong>HAA-1234</strong> (Toyota Corolla).</p>
<p>Fecha de salida: 15/03/2024 09:30</p>

Notifications Sent

Emails dispatched to:

Ana García (the employee)
All members of “Fleet Supervisors”
All members of “Vehicle Checkout Recipients”

Status Tracked

Each notification is logged with status (Sent, Delivered, etc.)

Permissions and Access

Notification management requires specific permissions: View Notifications

See dashboard and history
View events, groups, templates (read-only)

Manage Events

Create, edit, activate/deactivate events
Assign groups to events

Manage Groups

Create and edit groups
Add/remove members
Configure channels

Manage Templates

Create and edit templates
Publish templates
Send test emails

Template management is powerful and affects all users. Restrict access to authorized administrators.

Best Practices

Event Management

Event Best Practices

Use clear, descriptive event names
Follow naming convention: RESOURCE_ACTION (e.g., VEHICULO_SALIDA)
Document events thoroughly in descriptions
Set appropriate default severity
Review and deactivate unused events

Group Management

Keep groups focused (single purpose)
Regularly audit membership
Remove inactive users promptly
Use descriptive group names
Document group purpose

Template Design

Keep it simple: Clear, concise messages
Use branding: Include logo and colors
Mobile-friendly: Test on mobile devices
Clear CTAs: Make actions obvious
Test thoroughly: Use multiple test payloads
Handle missing data: Use default values or conditional logic

Write email templates at a 6th-grade reading level for maximum clarity.

Troubleshooting

Notifications Not Being Sent

Checklist:

Is the event active?
Are groups assigned to the event?
Do groups have active members?
Is the template published as default?
Check notification history for errors

Email Delivery Issues

Problem: Emails sent but not received Solutions:

Check spam/junk folders
Verify recipient email addresses
Confirm email server configuration
Review suppression lists
Check email service provider logs

Template Placeholders Not Replaced

Problem: Email shows {{variable_name}} instead of value Solutions:

Verify placeholder name matches payload keys exactly (case-sensitive)
Check that event payload includes the variable
Use default_payload in metadata for fallbacks
Test with known-good payload data

Preview Shows Different Content Than Production

Problem: Server preview differs from actual emails Solutions:

Always use server preview for final checks
Verify template is published as default
Clear template cache (contact administrator)
Check if event payload differs from test payload

Advanced Configuration

Custom Event Payloads

Developers can trigger events with custom data:

import { triggerNotification } from '@/services/NotificationService';

await triggerNotification({
  event: 'CUSTOM_EVENT',
  payload: {
    user_name: 'John Doe',
    action: 'completed task',
    timestamp: new Date().toISOString()
  },
  severity: 'medium'
});

Conditional Logic in Templates

While not fully implemented, you can simulate conditions:

{{#if maintenance_required}}
<p style="color: red;">Maintenance is required!</p>
{{/if}}

Advanced template features may require custom implementation. Contact your developer for assistance.

Dashboard: View notification activity
Vehicle Operations: Events triggered by vehicle actions
Reservations: Reservation-related notifications

Technical Reference

Source Files:

Notifications UI: src/pages/Notificaciones/Notificaciones.jsx
Event services: src/services/NotificacionesEventosService.js
Group services: src/services/NotificacionesGruposService.js
Template services: src/services/NotificacionesPlantillasService.js

Key Functions:

listEventos(): Fetch all events
createEvento(data): Create new event
setEventoGrupos(eventId, groupIds): Assign groups
listGrupos(): Fetch all groups
addMiembros(groupId, userIds): Add group members
apiCreatePlantilla(data): Create template
apiPreviewPlantilla(config): Preview template
apiPublishPlantilla(templateId): Publish template as default

Get Started

Core Features

User Guides

Administration

Advanced

​Overview

​System Architecture

​How Notifications Work

​Dashboard Overview

​Key Performance Indicators

​Recent Notifications Table

​Events & Routing

​What are Events?

​Event Properties

​Creating an Event

​Editing Events

​Activating/Deactivating Events

​Assigning Groups to Events

​Deleting Events (Soft Delete)

​Notification Groups

​Group Structure

​Creating a Group

​Managing Group Members

​Channel Configuration

​Email Templates

​Template Structure

​Creating a Template

​Using Placeholders

​Template Preview

​Local vs Server Preview

​Sending Test Emails

​Publishing Templates

​Template Metadata

​Notification Workflow Example

​Scenario: Vehicle Checkout Notification

​Permissions and Access

​Best Practices

​Event Management

​Group Management

​Template Design

​Troubleshooting

​Notifications Not Being Sent

​Email Delivery Issues

​Template Placeholders Not Replaced

​Preview Shows Different Content Than Production

​Advanced Configuration

​Custom Event Payloads

​Conditional Logic in Templates

​Related Features

​Technical Reference

Build docs developers (and LLMs) love

Overview

System Architecture

How Notifications Work

Dashboard Overview

Key Performance Indicators

Recent Notifications Table

Events & Routing

What are Events?

Event Properties

Creating an Event

Editing Events

Activating/Deactivating Events

Assigning Groups to Events

Deleting Events (Soft Delete)

Notification Groups

Group Structure

Creating a Group

Managing Group Members

Channel Configuration

Email Templates

Template Structure

Creating a Template

Using Placeholders

Template Preview

Local vs Server Preview

Sending Test Emails

Publishing Templates

Template Metadata

Notification Workflow Example

Scenario: Vehicle Checkout Notification

Permissions and Access

Best Practices

Event Management

Group Management

Template Design

Troubleshooting

Notifications Not Being Sent

Email Delivery Issues

Template Placeholders Not Replaced

Preview Shows Different Content Than Production

Advanced Configuration

Custom Event Payloads

Conditional Logic in Templates

Related Features

Technical Reference