Home
Integrations

How Does the Cumulocity IoT Integration Work in Dusk FSM?

## How Does the Cumulocity IoT Integration Work in Dusk FSM?

Dusk FSM integrates with **Cumulocity IoT** to connect IoT device events with field service operations.

The integration allows alarms generated by connected devices in Cumulocity to automatically create **Work in Dusk FSM**, helping organisations move from an IoT event to a field service response without manually creating the Work.

This can be used to support connected equipment, sensors, infrastructure and other IoT-enabled field service environments.

---

## How Does the Integration Work?

The Cumulocity integration connects IoT monitoring with Dusk FSM Work management.

The process is:

1. A device or sensor is monitored through **Cumulocity IoT**
2. The device generates an **alarm**
3. Dusk FSM receives the alarm through the Cumulocity integration
4. Corresponding **Work is automatically created in Dusk FSM**
5. The Work can be reviewed and configured with the required Customer, Work Type, duration and other Work information
6. The Work can then be assigned and dispatched using the standard Dusk FSM scheduling and dispatch process

This allows an IoT event to become actionable field Work within Dusk FSM.

---

## Connecting Cumulocity to Dusk FSM

To use the integration, your Cumulocity tenant must first be connected to Dusk FSM.

Within Dusk FSM, open the **Cumulocity IoT Settings** and connect your Cumulocity environment.

Once successfully connected, Dusk FSM displays the connected **Cumulocity Tenant ID**.

![How to connect Cumulocity IoT to Dusk FSM](https://help.duskmobile.com/uploads/markdown/20260904-230442-495.png "How to connect Cumulocity IoT to Dusk FSM")

The connected account can also be disconnected from this screen when required.

---

## Creating Work From a Cumulocity Alarm

Once Cumulocity is connected, alarms generated by monitored devices can trigger the creation of Work in Dusk FSM.

For example, the demonstration shows a device generating a: **Sensor alarm (Temperature)** within Cumulocity.

The alarm is then received by Dusk FSM and automatically creates corresponding Work.

In this example, **Sensor alarm (Temperature)** appears in the Dusk FSM Work list as newly created, Unassigned Work.

This removes the need for an office user to manually monitor the IoT platform and recreate the alarm as Work in Dusk FSM. The integration can be configured to prevent all any alarm creating work, so alarms that can be remotely resolved do not create work in Dusk FSM.

---

## Review and Configure the Work

Once the Work has been created, it can be opened and managed using the normal Dusk FSM Work process.

The Cumulocity alarm information provides the starting point for the Work. Additional operational information can then be added as required, including:

* Allocated duration
* Customer
* Work Type
* Customer and Work location
* Other Work configuration required by your workflow

![How work is automatically created in Dusk FSM from Cumulocity](https://help.duskmobile.com/uploads/markdown/20260904-230827-458.png "How work is automatically created in Dusk FSM from Cumulocity")

Once the required information has been added, the Work can be saved and progressed through your normal field service workflow.

---

## Assign and Dispatch the Work

After the Work has been configured, it can be assigned and dispatched through Dusk FSM.

This means an IoT-generated event can move through the same scheduling and field service process as other Work in Dusk FSM.

Your team can use Dusk FSM to manage the operational response while Cumulocity continues to provide the IoT monitoring and alarm capability.

---

## What Can the Cumulocity Integration Be Used For?

The integration is designed for field service environments where connected devices or sensors can identify conditions requiring operational attention.

Examples can include:

* Equipment monitoring
* Temperature alarms
* Connected infrastructure
* Remote sensor monitoring
* Equipment faults
* Condition-based maintenance
* IoT-triggered inspections
* Remote assets requiring field intervention

By connecting IoT alarms directly with Work management, organisations can reduce the manual steps between identifying an issue and initiating a field response.

---

## Frequently Asked Questions

**Q: What does the Dusk FSM integration with Cumulocity do?**  
**A:** The integration allows alarms generated in Cumulocity IoT to create corresponding Work in Dusk FSM, where the Work can then be managed through the normal scheduling and field service workflow.

**Q: Does someone need to manually create Work when an alarm occurs?**  
**A:** No. The integration demonstrated allows a Cumulocity alarm to automatically create Work in Dusk FSM.

**Q: Can I see which Cumulocity tenant is connected to Dusk FSM?**  
**A:** Yes. The Cumulocity IoT Settings in Dusk FSM display the connected Cumulocity Tenant ID.

**Q: Can I disconnect Cumulocity from Dusk FSM?**  
**A:** Yes. The connected Cumulocity account can be disconnected from the Cumulocity IoT Settings.

**Q: Can Cumulocity-generated Work be scheduled and dispatched?**  
**A:** Yes. Once created and configured, the Work can be managed using the normal Dusk FSM scheduling and dispatch process.

**Q: Can I associate the Work with a Customer and location?**  
**A:** Yes. The Work can be configured with the appropriate Customer and location information as part of the standard Dusk FSM Work process.

---

## 🔗 Related Articles

* [What Is Work in the Dusk FSM Platform?](https://help.duskmobile.com/article/Work/What-Is-Work-in-the-Dusk-FSM-Platform)
* [How to Use the Work Calendar View in Dusk FSM](https://help.duskmobile.com/article/Work/How-to-Use-the-Work-Calendar-View-in-Dusk-FSM)
* [How Do I Use the Gantt View in the Dusk FSM](https://help.duskmobile.com/article/Work/How-Do-I-Use-the-Gantt-View-in-the-Dusk-FSM)

---

Updated on September 05, 2026

How Does the Cumulocity IoT Integration Work in Dusk FSM?

Need Support?

Error

Delete Article