--- title: "Winter '26 Samsara Configuration" slug: "winter-26-setup-configuration" tags: ["Admin", "Compiled from User Guide", "Fleet Management", "Samsara", "Winter '26"] updated: 2026-06-02T15:32:53Z published: 2026-06-02T15:32:53Z canonical: "documents.revenova.com/winter-26-setup-configuration" --- > ## Documentation Index > Fetch the complete documentation index at: https://documents.revenova.com/llms.txt > Use this file to discover all available pages before exploring further. # Winter '26 Samsara Configuration The integration with the Samsara API provides direct integration to drivers and the assets they are driving through an ELD device and a phone application. Revenova’s Fleet Management Module requires the use of Samsara ELD tracking. Samsara provides “push” status updates to the TMS via a sites-based web service. Inbound packets from Samsara are stored in the Queued Transaction object and processed by the **QueuedTransactionJob**. > [!NOTE] > The Summer ‘25 TMS release contains a new job controlling the integration with Samsara. The new [Fleet Manager Job 3](/previous-releases/docs/winter-26-fleet-management-job) is faster and more efficient. It replaces the obsolete Fleet Manager Job. ## Setup ### Enter Credentials Enable the Samsara integration by completing the following steps. 1. Navigate to **TMS Admin**. 2. Select *Credentials*. 3. Select the *Global Services* tab. 4. Find Samsara in the list and open the card. 5. *Check* the Enabled box. 6. Enter the **User ID** and **Password 1** into the text fields. 7. Set the Service URL to: https://api.samsara.com. 8. Set the Test Service URL to: https://api.samsara.com. 9. Click the **Save** button when finished. | User ID | Password 1 | Password 2 | Customer Number | | --- | --- | --- | --- | | "Revenova" | Required API Key | | | ### **Remote Site Settings** Upgrading from previous versions of the TMS may have outdated information. Check that the Remote Site Settings for the Samsara integration URL are up to date. 1. Click the **Setup** gear icon in the top right corner. 2. From the drop-down, click **Setup**. 3. In the Quick Find Toolbar type *Remote Site Settings* and click the link. 4. From the list of remote sites find *Samsara* and click the **Edit** link. 5. Update the Remote Site URL to: [](/previous-releases/docs/javascript%3AsrcUp(%27%2F0rp7z000000UhwJ)https://api.samsara.com. ### **Experience Cloud Site Setup** The Samsara integration requires a webhook to send information into the TMS. Create an API Site to accept inbound traffic. 1. Create a Salesforce Site for API Guest User Access. 2. Set the public access for the Site. 3. Activate and Publish the Site. 4. Enter the API URL into the field for **Inbound API Community URL** under TMS Admin, in the Configuration section. 5. Add the following extension to the end of the URL to match the example below: /services/apexrest/rtms/tmslistener?org=[18-character org id]&source=Samsara&pwd=[credentials code field] 6. Contact Samsara support and provided them this "Post-back" URL to point at your listener.[](mailto:integrations@truckertools.com) **{API Experience Cloud Site URL}**/services/apexrest/rtms/tmslistener?org=[18-character org id]&source=Samsara&pwd=[credentials code field] **Example**: [https://revenova.my.site.com/api/services/apexrest/rtms/tmslistener?org=00D180000008oA9EAI&source=Samsara&pwd=4wGFDgnT950Ovg1](https://revenova.my.site.com/api/services/apexrest/rtms/tmslistener?org=00D180000008oA9EAI&source=Samsara&pwd=4wGFDgnT950Ovg1) > [!WARNING] > The Salesforce-generated API [Experience Cloud](https://help.salesforce.com/s/articleView?id=experience.networks_overview.htm&type=5) Site URL is case sensitive. The bi-directional integration is accomplished with three TMS processes. 1. The **Fleet Management Job** **3** invokes API calls on the Samsara API. 2. Samsara pushes event packets to the application via the **TMS Listener** and **Samsara Event Processor.** 3. The **Load LWC widget** can send text messages to the driver via the Samsara phone application. 1. Driver messages are stored on the Driver record Chatter feed. If the Customer is already using Samsara, it is likely that they have many *Locations* that can be imported into Revenova and create **Account** records using the **Fleet Management Job 3.** > [!WARNING] > The Samsara integration supports multiple stops for the same Account location. See the [Fleet Management Job 3](/previous-releases/docs/winter-26-fleet-management-job) for more information. ### Configuration Navigate to TMS Admin → Configuration, [Fleet Management](/previous-releases/docs/winter-26-fleet-management). - *Check* the **Fleet Management Enabled** box. - Select **Fleet Management 3** from the **Fleet Management Job** picklist selection. - Fleet Management 3 job controls syncing record data between the TMS and the Samsara integration. - Select *Samsara* from the **Fleet Management Default ELD Provider** picklist selection. - Review the **Driver Log Grace Period (Days)** value. The default value is 2 days. Enter another value if necessary. - *Check* the **Enable Routing Consolidate Locations** field to consolidate duplicated Stop locations as one single Stop location. When *Checked* and the Segment contains Legs with consecutive End Stops/Locations of the same location, those locations are sent as a single location to Samsara. When inbound arrival/departure events are received from Samsara, they are applied to both Trip Plan Legs. - This only applies to defined location Accounts and not general addresses or geolocations. - The following is added to the dispatch in the Notes field. “This location has both a delivery and a pickup.” - Enter an email address in the **Fleet Management Email** box. - Search Accounts and select a **Fleet Management Default Carrier**. A Default Carrier is not required, but recommended. - *Check* the **Create ELD Trip On Dispatch** field based on preferred functionality. - When *Checked*, Trips are sent to Samsara when the user clicks the **Dispatch** button on the Trip Plan Segment. - When *Unchecked*, Trips are sent to Samsara when the Trip Plan Segment **Driver Confirmation Status** moves to *Accepted*. - **Save** the information when complete. ### **Record Syncing** Location and Driver records are synced between the TMS and Samsara. Location records that exist in the TMS are sent to Samsara when Fleet Management Job 3 runs. Locations are assessed to determine if they are a *Fleet Load Location*. The following criteria is used to determine which TMS *Fleet Load Location* records are sent to Samsara. - The Account **TMS Type** field is one of the following. - Airport - Border Crossing - Distribution Center - Rail Terminal - Seaport - Seaport Terminal - Shipper/Consignee - Terminal - Warehouse - Waypoint - Location records that were used as a Load Stop and the Stop record was created since the last time Fleet Management Job 3 ran. - The **Fleet** field on the Load must be *Checked*. - The Shipping Latitude must have a value. For these Account location records, the following determines the information sent to Samsara. - If the Account location does not have an associated Account ELD record, one is created. - The Account ELD record is sent to Samsara. - The address is stored in the Samsara portal. - Samsara returns an **ELD ID** that is stored on the Account ELD record. - If the Account location already has an associated Account ELD record and uses a circular geofence, the following occurs. - The address is updated in the Samsara portal. #### **Account ELD Location Fields** One or more TMS Account records are paired to Samsara Locations/Addresses by the Account ELD record created for every Fleet shipping locations and addresses. Before running the Fleet Management Job 3 for the first time, complete the following steps to receive and create Account ELD records from Samsara. 1. Navigate to **TMS Admin → Configuration**. 2. Click the **ELD Location Download** button at the top of the component. 3. A banner at the top of the component confirms that locations are downloading. 4. View download progress by navigating to Setup → Apex Jobs and find the FleetManagementJob Apex Class in the list. #### **Driver Record Fields** Note the following Driver fields that control how records are created or synced between Samsara and the TMS. - **ELD Enabled** - When *Checked*, Drivers that do not exist in Samsara are sent from the TMS to create those records in Samsara. - When *Checked* and the Driver is on a Trip Plan Segment, when the Segment is *Dispatched*, the Trip Plan Segment is Dispatched to Samsara. - **ELD Exempt** - When *Checked*, Hours of Service features and violations do not sync between Samsara and the TMS. ## **Samsara Portal Setup & Configuration** Required API Key/Token: API Tokens for secure access to the API can be viewed and created on the API Tokens Settings page. Below are instructions on how to set up an API token: 1. Log in to the Samsara Dashboard and navigate to Settings → **API Tokens**. 2. Click **+ Add an API Token** to create a new token. 1. Enter *Revenova Integration* as the Name for the API token. 2. Select a Permission Scope for the API token. Give **Full Admin** access for this API Token. For Full Admin access, select the *Global Read* and the *Global Write* scopes under the **Global** Dropdown. 3. Enter a **Name** and **Permission Scope**. 4. Click **Save**. > [!NOTE] > Configure the *Route Tracking Window* setting to control when tracking and status updates are sent to the TMS. ### **Samsara Management Application Setup** 1. Install Samsara ELD in all Fleet Asset tractors/trucks. 2. Install Samsara Driver Phone Application on all driver smart phones. 3. From the Samsara Management Application complete the following steps as necessary. 1. Add all driver documents using the names defined in the [Customer Invoice Documents](/previous-releases/docs/winter-26-customer-invoice-documents) object. 1. The Customer Invoice Document table Synonyms field captures documents from drivers via the Samsara phone application. Existing users of Samsara may use document names that are different from Revenova definitions. Populate this field if this is the case. 2. Add the following required field to all driver Document Types: 1. Is Proof of Delivery (*Yes* or *No*) 3. Configure the [web hook](/previous-releases/docs/winter-26-api-integration-partner-webhooks) for push alerts. 4. Configure push alert types and thresholds. 5. From **Settings → Fleet → Driver App** review setup parameters. 6. From **Settings → Fleet → Dispatch** review setup parameters. ### **Driver Setup** Driver information is tracked through the Samsara integration. Confirm the **ELD Enabled** and **ELD Exempt** fields are set as necessary. - The **ELD Enabled** field controls sending routing information, arrival and departure events, and documents to and from Samsara. - Routing information, arrival/departure events, and documents are sent to and from Samsara when *Checked*. - No routing information, arrival/departure events, or documents are sent to and from Samsara when not *Checked*. - The **ELD Exempt** field controls tracking Hours of Service features and violations. - Hours of Service features and violations are tracked and sent through the Samsara integration when not *Checked*. - No Hours of Service features or violations are tracked and sent through the Samsara integration when *Checked*. > [!NOTE] > The Samsara integration does not pull into or create Fleet Asset (trailer/chassis/container) records in the TMS. Only Tractor/Power Unit Fleet Asset records are created in the TMS. ### **Troubleshooting** If the system administrator receives a Fleet Management email with a list of errors, ‘1) start() method error: invalid token---(rmts)’ This means there are invalid Samsara credentials. The job should be stopped until valid credentials are entered. > [!CAUTION] > 1) start() method error: invalid token- - -(rtms) **Issue** When running the Fleet Management Job, system admin receives an email containing the following. 1) start() method error: invalid token---(rtms) (2) start() method error: invalid token---(rtms) (3) start() method error: invalid token---(rtms) (4) start() method error: invalid token---(rtms) (5) start() method error: invalid token---(rtms) (6) start() method error: invalid token---(rtms) (7) start() method error: Unexpected character ('r' (code 114)): expected a valid value (number, String, array, object, 'true', 'false' or 'null') at input location [1,2]---(System Code) **Resolution** The credentials for the Samsara integration are invalid. Stop the Fleet Management job and enter valid credentials. Start the Fleet Management Job when the credentials are updated.