Overview

This guide steps through the process of replicating common Samsara integration Scenarios in Limble Fuse from one Org to another Org. Within Limble Fuse, each scenario performs a contained integration, and each scenario can only be associated with one Samsara Org.

Because of this, we need to make copies of existing Scenarios whenever we add a new Samsara Org to our account. This allows multiple Samsara Orgs under your account to benefit from the Fuse integrations without having to rewrite them. At the time of this writing, there are 3 separate Scenarios in Limble Fuse that perform functions for Samsara integration. We will walk through replicating each of these. At a high level, this process involves:

• Copying Scenario Definitions

• Creating and using new webhooks in Limble and Samsara for the new Samsara Org

• Creating Triggers in the new Samsara Org for your Fuse integrations

• Updating the copies of the Fuse Scenarios to point to the new Samsara Org

• Organizing your new Scenarios within Fuse by Samsara Org folders

Steps

1. Login to your Limble account and navigate to the Limble Fuse integration portal

2. In the left menu, click 'Scenarios' to be presented with a list of existing Scenarios
   

Click on the dropdown beside one instance (any org) of the first Scenario we will copy, named “[Samsara] DVIR/Fault Code > Limble WO” and click ‘Clone’

3. In the menu that appears, update the name of the org in the new Scenario title (Our example is using the org name “Finley Asphalt and Concrete”) to the name of the new Org

4. Click ‘Add’ beside the prompt to select or create a new webhook. In the panel that appears, name the new webhook ‘Samsara Events: <new org name>’ and click ‘Save’

5. You should now see a blue url link, which is the address for the newly created webhook. Save this address in a note, we will use it in an upcoming step

6. Click ‘Save’. You should now be brought into the management panel for the newly copied Scenario. Leave this browser open, and navigate to your Samsara Account under the new Org.

7. In the Settings menu of the new Samsara Org, click ‘Webhooks’

8. Let’s create a new Webhook, which tells the Samsara Org where to send information about Vehicle and DVIR events.

9. In the new menu that appears, name the webhook “Limble Fuse”. In the ‘Payload URL’ field, paste the address you saved from Step 5. **no changes**. Click ‘Save’

10. Refresh the browser and confirm that the new Webhook appears. You should see that the ‘Configured Alerts’ section is currently empty. We will address this next.
    
    

11. In the left Navigation Bar, click on the Bell icon to view the 'Alerts' Dashboard.

12. Click ‘Create Alert’. Select the 'DVIR Submitted' Alert type and choose "All Assets" in the 'Apply To' field. Rename the alert to “DVIR Submitted -> Limble Fuse Webhook”. In the ‘Triggers’ section, select “DVIR Submitted”. In the ‘Condition’ section, add all desired DVIR types. In the 'Actions' section, remove the existing ‘Notification’ Action, then add a new ‘Webhook’ Action, selecting the “Limble Fuse” Webhook we created earlier, as shown below. Click ‘Save’

13. Let’s add another Alert. This time, select the “DVIR Defect” trigger.

14. In the details page that appears, click ‘Edit asset selection’, then click “All Assets”, then click “Done selecting assets”. 

15. In the ‘Send Webhook Notification’ dropdown, select “Limble Fuse”. Verify your details look like the following screenshot, then click ‘Save’

16. Create one more Alert. Select the “Vehicle Fault Code” trigger and update the details as shown below, then click ‘Save’
    

17. After creating the Webhook and the Alerts to use it, we have one more thing to do before returning to the Fuse portal. In the Settings menu, navigate to ‘API Tokens’ near the bottom. Click ‘Add an API Token’

18. This token will be used by Limble Fuse to send data to the Samsara Org. In the configuration page, give the new token a name of “Samsara:<Org name> <> Limble Fuse”. Under ‘Scopes’, add “Global Read” and “Global Write” permissions. Scroll down and click ‘Save’

19. After saving the new Token, you should see a notice with the full token text (starting with “samsara_api_” and a notification message. Click ‘Copy to Clipboard’ and past in a notepad for use in an upcoming step.

20. Navigate back to your Limble Fuse browser tab. This is the Scenario View. Click on the page one time to enter edit mode. To move around, click and drag the white background. You can also zoom in and out to get a closer view of the modules.

21. You should see that there are several dark blue Samsara modules. These are used by Limble Fuse to send and retrieve data to the Samsara Org. Click on one of these Samsara modules to view its details

21. In this screen, you’ll notice that the ‘Connection’ is still the value of the original Samsara Org. We need to create a new Connection so that this Fuse Scenario can point to and interact with the new Org. Click ‘Add’

22. In the new window, update the name of the new connection to “Samsara: <new Org name>”. In the “Samsara API Access Token’ field, type “Bearer “ (with a single space after), then paste the API token you copied from Samsara. Click ‘Save’

23. If you entered the token string correctly, the Fuse module will return to the details view with the new Connection selected, as shown below. Click ‘OK’ to save this change.

24. Click on another Samsara module within the Scenario. Click the ‘Connection’ dropdown and select the correct Org. It is available in the menu now that we’ve created it. Click “OK” to save.

25. Update all the other dark blue Samsara modules to point to the new Samsara Org, saving each by clicking ‘OK’.

26. Once done, click the save button on the bottom Scenario menu. Confirm that you see the blue confirmation message shown below

27. Click the top left arrow icon twice to leave the Scenario configuration page and return to the list of Scenarios.

28. You should see your newly created Scenario in this list. Click the dropdown beside it and click ‘Move to Folder’. If you haven’t created a folder yet for the new Samsara Org, do so first. Then select that folder to move the new Scenario to.

29. Let’s replicate the next Scenario “[Samsara] Regular Vehicle > Limble Asset Sync”. Select the dropdown beside an existing instance and click ‘Clone’

30. Update the name of the new scenario to include the new Org name.

31. In the Scenario management page, update the ‘Connection’ of each Samsara module to point to the new Org, as we did in the previous Scenario. Remember to click ‘OK’ after each change.

32. Click ‘Save’ and then click the top left arrow icon twice to return to the Scenario list page.

33. Ensure that the new Scenario is enabled. If not already, toggle the switch to “On”

34. Move this enabled Scenario to the correct Org folder

35. Clone an existing instance of the final Scenario: “[Samsara] Asset Sync | Gateway Gateway Association”. Where prompted to select a Webhook, click ‘Add’. Name the new Webhook “Limble Webhook: <Samsara Org Name>”.

36. Click ‘Save’. Copy the blue webhook address for use in a subsequent step and click ‘Save’ to finish creating the new Scenario. You will be brought into the Scenario management view.

37. Leave this browser tab as is and open a new tab. Navigate to your Limble account. In the ‘Settings’ menu, scroll down to the ‘API Settings’ section

38. Add the copied address from step 36 to the following Endpoint fields:
    - 'Asset Webhook Endpoint'
    - 'Asset Field Webhook Endpoint'
    - 'Task Webhook Endpoint'

39. Return to the Fuse browser tab. Your screen should currently show a Scenario that looks similar to this

40. Find and click the filter titled 'Correct Location?', shown below:Update the value to the Limble Location name of the new Samsara Org. The spelling and spacing must match, but letter case (upper/lower) does not matter.

41. Repeat the previous step for the other filter titled 'Correct Location?' on the bottom logic branch, shown here:
    

42. Update the ‘Connection’ for each of the dark blue Samsara modules, as we did earlier. Save each change, then click ‘Save’ for the overall Scenario. Click the back arrow icon twice to return to the list of Scenarios.

43. Enable the newly created Scenario, then move it to the correct Org folder. If prompted when you enable the scenario, choose 'Process Existing'.

44. Navigate to the Org folder from the “Scenarios” tab in Limble Fuse. Ensure that you have the 3 newly created Scenarios and that each is enable, as shown below:

Finished! Your Limble account is now integrated with your newly added Samsara Org.

Check back to this page regularly to see if any errors have stopped your Scenarios from running. If so, they will be automatically toggled to “OFF” and will display helpful information in the logs. Address the issues and then enable the Scenario.

Questions, comments, feedback? Contact integrations@limblecmms.com for guidance, or submit a ticket via our "Submit a Ticket" option in the upper right of this portal.