Connecting machines and sensors to Salesforce unlocks automated service operations. When done correctly, a temperature spike, vibration anomaly, pressure failure, or power alert can instantly create a work order and dispatch a technician.

When done incorrectly, nonstop telemetry can exceed Salesforce API limits and create unnecessary data storage costs.

This guide explains the right architecture for connecting virtually any connected asset to Salesforce.

The Correct Architecture for IoT + Salesforce

The ideal architecture looks like this:

Sensor or Machine → IoT Platform → Bolt Data Connect → Salesforce → Automated Service Action

This applies to:

• Refrigerators and cold storage units
• HVAC systems
• Medical devices
• Manufacturing equipment
• EV chargers
• Industrial pumps and compressors
• Lab instruments
• Retail kiosks
• Fleet vehicles
• Power generation systems

There are three core components:

1. How sensor data is collected
   
2. How that data is intelligently filtered
   
3. How Salesforce reacts to meaningful events
   
   

Salesforce is not a time-series database. It is designed for service automation, asset management, and workflow orchestration. High-frequency telemetry belongs outside Salesforce.

Why You Should Not Stream Raw Sensor Data Into Salesforce

Consider this example:

1,000 connected assets
Each sends 1 reading per minute

That equals:

1,440,000 API calls per day

Most Salesforce environments will exceed daily API limits at this volume. Continuous streaming also increases storage usage and Flow execution load.

Instead of sending every reading, modern architecture sends:

• Threshold breach events
• State changes
• Device offline alerts
• Daily summary records
• Fault codes or error states

This reduces API traffic dramatically while preserving operational intelligence.

Event-Driven IoT Integration (Best Practice)

Industrial IoT architecture is event-driven, not stream-based.

Instead of:

“Send every vibration reading from a motor”

Use logic such as:

IF vibration exceeds threshold for 3 minutes
THEN send event to Salesforce

IF pressure drops below operating range
THEN trigger alert

IF device returns to normal
THEN update asset status

Bolt Data Connect applies intelligent filtering before data reaches Salesforce. It is an IoT middleware layer built specifically for asset-centric Salesforce environments.

Automatically Creating Service Actions in Salesforce

Inside Salesforce, you configure:

Account
Asset
Sensor_Event__c (Custom Object)
Work Order

Using Salesforce Flow:

IF Sensor_Value__c exceeds Threshold__c
THEN
• Create Work Order
• Assign Technician
• Notify Dispatcher
• Send SMS or Email
• Update Asset Health Status

No custom code required.

Real-World Multi-Industry Examples

Cold Storage Unit
Temperature rises above threshold
→ Work Order created automatically

Manufacturing Motor
Vibration anomaly detected
→ Preventive maintenance dispatched

EV Charger
Power interruption detected
→ Technician notified immediately

Medical Imaging Equipment
Error code generated
→ Service case and work order created

Fleet Vehicle
Engine diagnostic fault triggered
→ Maintenance event scheduled

All powered by event-driven IoT integration.

Scaling to Thousands of Connected Assets

As asset volume grows, architecture becomes critical.

Best practices include:

• Event-based processing
• State-change detection
• Intelligent batching of summaries
• Asset-aware filtering logic

Bolt Data Connect is purpose-built to manage high-volume IoT integrations for Salesforce Field Service without exceeding API limits.

Final Takeaway

Do not stream nonstop telemetry into Salesforce.

Instead:

Store high-frequency data in your IoT platform.
Send only meaningful events.
Let Salesforce handle service automation.

That is how predictive maintenance scales across industries.

‍