Sensolus Connector
Bring Sensolus asset-tracking and location data into your warehouse for operational, location, and utilization analytics.
Evaluating against Fivetran? See how Supaflow handles Sensolus pricing, connector quality, and Snowflake deployment side-by-side.
Supaflow vs FivetranWhy Supaflow
All connectors included
Every connector is available on every plan. Pricing does not increase with connector count.
Pay for compute, not rows
Credit-based pricing. Usage scales with your pipelines, not with row counts.
One platform
Ingestion, dbt Core transformation, reverse ETL, and orchestration in a single workspace.
Capabilities
Tracker and Location Analytics
Land Sensolus inventory, geozone, visit, and location data in your warehouse so operations teams can analyze asset movement, dwell time, and tracker health alongside business data.
Per-Tracker Incremental Sync
Geozone visits and device locations advance independently for each tracker. Configure an overlap window to re-check late-arriving tracker data without re-reading the full history on every run. Use MERGE for these objects so overlapping rows are deduplicated; APPEND preserves them.
Inventory Snapshots
Devices and geozones refresh as complete inventories, keeping current tracker status and geozone definitions available for reporting and enrichment.
Production, Sandbox, or Private Service URLs
Use the production service defaults or provide the devices and visits service URLs for a Sensolus sandbox or private deployment.
API Key Authentication
Connect with a Sensolus API key and organization ID. Supaflow reads source data and does not modify your Sensolus account.
Supported Objects
Incremental
Geozone visits
Visit events for eligible trackers, including entry and exit times, duration, and geozone information.
Device locations
Location observations for eligible trackers, including coordinates, timestamps, accuracy, and location context.
Full Refresh
Devices
The complete tracker inventory with status and device metadata.
Geozones
Geozone definitions for the configured Sensolus organization.
Not Yet Supported
Other Sensolus APIs
Push events, alerts, reports, device configuration, and other resources are not exposed by the current connector. Contact support with the objects you need.
How It Works
Prepare Sensolus API access
Ask a Sensolus administrator to enable API access and create an API key with access to the organization data you want to sync. Keep the organization ID available for setup.
Enter the API key and organization ID
Create a Sensolus source in Supaflow and enter the API key and organization ID. The API key is stored encrypted.
Choose sync settings
Leave the production service URLs as their defaults, or enter both service URLs for a sandbox or private deployment. Set the initial history, late-arrival lookback, and offline-tracker options for your use case.
Test and save
Click Test & Save to verify the connection and save the source. After the schema is available, select the Sensolus objects for your pipeline.
Use Cases
Fleet movement and utilization reporting
Combine tracker locations and geozone visits with operational data to report on asset movement, dwell time, route patterns, and utilization.
Geozone flow analysis
Use visit history and geozone definitions to understand how assets move through facilities, staging areas, and production sites over time.
Warehouse-ready asset data
Keep current tracker inventory and location history in your warehouse so analysts can join asset context with orders, work orders, and customer operations.
Frequently Asked Questions
What does the Sensolus connector sync?
The connector syncs Devices and Geozones with full refresh, plus Geozone Visits and Device Locations incrementally. Other Sensolus APIs are not currently exposed as selectable objects.
How does incremental sync work?
Geozone Visits and Device Locations track progress independently for each eligible tracker. The first incremental run uses Initial Sync Days, and later runs can overlap the saved position by Late Arrival Lookback Days to catch data that arrives late. Use MERGE in the destination pipeline for these objects; APPEND retains overlapping rows and can create duplicates.
Can I include offline trackers?
Yes. Enable Include Offline Trackers to include trackers whose current status is OFFLINE in Geozone Visits and Device Locations. The Devices object always remains a complete inventory snapshot.
Can I connect to a Sensolus sandbox or private deployment?
Yes. The source uses production service defaults, and the configuration includes separate Devices API Base URL and Visits API Base URL fields so you can provide the URLs for a sandbox or private deployment.
How does Supaflow handle Sensolus rate limits?
Sensolus applies API quotas and rate limits. Supaflow retries transient rate limiting, server errors, and request timeouts with bounded backoff, but large tracker fleets may take longer and may benefit from narrower selection or off-peak scheduling.
Does the connector write back to Sensolus?
No. The connector is read-only and does not create, update, or delete data in Sensolus.
What happens when Sensolus adds a new field?
The connector exposes a stable declared schema and keeps nested payloads as JSON fields. A newly added vendor field may require a connector update before it appears as a selectable column.
Related Resources
Need a connector we don't support yet?
Build one with AI-powered Connector Dev Skills.
Learn More About the Connector SDK
