Skip to main content
Samsara is a fleet management and IoT platform designed for transportation companies. It provides tools for vehicle tracking, driver safety monitoring, fuel management, and operational analytics to help businesses optimize their fleet operations and improve efficiency.

​
Configuring Samsara as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Samsara option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need to provide your credentials to authorize Nekt to access your Samsara data. The following configurations are available:
  • API Token: The token to authenticate against the API service.
  • Start Date: Starting point for data extraction. Only records created or updated after this date will be synced.
  • Base URL: The base URL to access the API for your company account.
  • Timezone: The timezone that should be used to convert datetime values.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization. You can inform things like what data it brings, to which team it belongs, etc. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Available streams

The table below lists every stream the Samsara connector can extract, along with the sync type supported by each one.
  • Incremental streams keep track of the last synced record and only fetch new or updated data on each run, starting from the configured Start Date.
  • Full Table streams fetch the current state of the data on every run.
Streams are only listed during setup if your API token has the corresponding Samsara API scope. The required scopes are: Addresses (addresses), Assignments (driver_vehicle_assignments), Documents (documents, document_types), Drivers (drivers), ELD Compliance Settings (US) (hos_logs, hos_daily_logs), Routes (routes), and Vehicles (vehicles). If a stream you expect is missing, review your token’s scopes in the Samsara dashboard.

​
Skills for agents

Download Samsara skills file

Samsara connector documentation as plain markdown, for use in AI agent contexts.