Samsara Listener and Alerts

Prev Next

Manage Fleet functions with the integration to Samsara.

Samsara ELD Integration

Fleet Management (FM) requires the use of Samsara ELD tracking. FM integrates with both the ELD device attached to the Fleet Asset and the Driver’s phone with the Samsara Driver Phone Application.

The bi-directional integration is accomplished in three ways.

  • The Fleet Management Job 3 invokes API calls on the Samsara API.

  • Samsara pushes event packets to the TMS via the TMS Listener and Samsara Event Processor.

  • The Load LWC widget can send text messages to the driver via the Samsara phone application.

In the Summer ‘25 TMS release the Fleet Management Job was replaced with Fleet Management Job 3. The new job is faster, more efficient, and should be used to control calls for the Samsara integration.

Samsara Alerts

See Samsara documentation for additional alert configuration information.

  1. Log in to the Samsara Portal.

  2. Select Alerts in the upper right corner.

  3. Under the Configured Alerts tab, filter alerts by Trigger Type, Action Type, or Status (Enabled or Disabled).

  4. Select an alert type to modify the alert configuration or create a new alert by clicking the + Create Alert button. See Alert Types for information about each alert configuration.

  5. Configure the settings for the alert. Settings vary by alert type, but typically include the conditions under which Samsara should send the alert and the specific devices the alert is configured for. Alert configuration can include the following.

    1. Triggers: Select from the available triggers and choose the Conditions and the Drivers/Vehicles the Trigger applies.

      1. Add Geofences and Engine On/Off settings

    2. Actions: Choose the webhook that alerts are sent to.

      1. Add Actions as necessary.

  6. Save the alert configuration.

  7. As necessary, return to the Alerts page to manage your alert configurations and View Alert Incidents.

Create and receive alerts for a variety of incidents including asset alerts, routing and dispatch alerts, safety alerts, gateway and sensor alerts, and compliance notifications.

Once an alert is configured, view incidents from Alerts → Incidents.

Trip Plan Legs containing an actualized Arrival Date/Time or Departure Date/Time are not sent to the Driver.

Samsara Event Processor

The Samsara Event Processor receives “push” packets from Samsara for the following Alert Triggers when configured in the Samsara Portal.

  • Safety Alerts

  • Device Health Alerts

  • Location & Movement Alerts

  • Maintenance Alerts

  • Driver Alerts

  • Forms Alerts

  • Routing Alerts

  • Security Alerts

  • Environment Alerts for Connected Equipment

  • Scheduled Alerts

  • Training Alerts

  • Site Alerts

See Samsara documentation for more specific information.

The Samsara Event Processor receives “push” packets from Samsara corresponding to the events, if the alerts/events are setup from the Samsara portal. These events display as alerts in the current Stop’s Carrier Status Comments field and the Load’s Load Status Comments field.

Trip Plan Segments that have Trip Plan Legs with consecutive End Stops/Locations with the same location may be consolidated. Check the Consolidate Same Locations When Routing field on the Trip Plan Segment to prevent arrival and departure issues for pickups and deliveries at a single location.

When multiple pickup and/or delivery events occur at a single location, this information is included in the call to Samsara in the “Notes” section. The Driver Instruction reads “This location has both a delivery and a pickup.”