Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Missing sequenceNumber Field in route_stops / routes Table – Samsara Connector

Answered
Manupriya Hettiarachchi User

Connector name: Samsara Lite

Table name: route_stops

Column to add: sequenceNumber 

API documentation link: https://developers.samsara.com/reference/fetchroutes

 

Additional details:

Hi Fivetran Support Team,

While reviewing the response payload for the Samsara "Fetch all routes" API endpoint (GET /fleet/routes), I noticed that the sequenceNumber field is present in the source API response body for route stops.

However, this field is currently missing from the corresponding route_stops (or routes) table ingested by the Fivetran Samsara connector.

Impact & Query:

  • Business Need: We require the sequenceNumber field to accurately maintain and reconstruct the ordered sequence of stops for fleet route analytics.

  • Request: Pease enable or pass through sequenceNumber in the connector schema, or advise if a schema update can be deployed for our pipeline?

Please sign in to leave a comment.

Comments

3 comments

Date Votes
  • Official comment
    Syead Mujtaba Imam Rizwi Fivetranner

    Hi Manupriya,

    Thank you for flagging this and for providing the additional details.

    We’ve reviewed the request and confirmed that both sequenceNumber and appointmentWindows are available as part of the route stop data in Samsara’s API.

    We’ve added this request to our backlog and will review what it would take to expose both fields in the route_stops table. We’ll keep you updated on this thread as we make progress.

    Best,
    Syead Mujtaba Imam Rizwi

  • Manupriya Hettiarachchi User

    Hi Fivetran Team,

    Following up on my previous request regarding sequenceNumber, we also identified that the appointmentWindows field is missing from the destination schema.

    Just like sequenceNumber, appointmentWindows is present in the Samsara API response payload for the "Fetch all routes" endpoint (GET /fleet/routes). We require this field to track scheduled arrival and departure time windows for route stop SLA reporting.

    Could you please check if appointmentWindows can also be added to the connector schema mapping alongside sequenceNumber?

    Best regards,

  • Kusal Amarasena User

    Hi Fivetran Team,

    As a follow-up to this Route API request, we have identified two additional fields that are available through the Samsara Route API but are not currently exposed through the connector.

    The specific fields required are:

    - ROUTE_TAG.tagIds
    - ROUTE_STOP.actualDistanceMeters

    Could you please enable these two fields and also consider enabling all other fields available through the Samsara Route API in the connector, where possible?

    This would help avoid raising separate enhancement requests whenever additional fields are required in the future.

    Thank you.