Salesforce Field Service
Turn a device fault into a field-service case with telemetry and asset history attached.
Detection without dispatch is just a well-documented failure. This connector turns InfiIoT rule triggers into Salesforce Field Service cases and work orders: the fault, the telemetry that proves it, and the asset's history arrive together, and resolution status flows back to the twin.
The data path, including the hand-offs that usually cause trouble.
Detect
The rules engine identifies a threshold crossing, failed heartbeat, or drift signature.
Create the case
A Salesforce case or work order is created via API with device identity, location, telemetry snapshot, and suggested severity.
Dispatch
Field Service scheduling assigns the technician; they arrive with the asset's live data and history on their device.
Resolve & sync
Closure status and technician notes return to the InfiIoT asset timeline, while the service record stays in Salesforce.
Where teams use this integration.
Send the fault context with the work order
The technician receives telemetry, location, and asset history before travelling to the site.
Schedule service from an early fault signal
A degrading device can become a planned visit before it reaches an outage or triggers a customer complaint.
Measure service cost against the asset history
Detection, dispatch, and resolution timestamps provide a common basis for calculating service cost per asset.
Want this wired into your stack?
Bring the source system, target system, and security constraints. An engineer will map the interface and the unresolved questions.