Home
Integrations

Using HubSpot Custom Objects in Dusk FSM Forms

## How to Use HubSpot Custom Properties in Dusk FSM Forms

## 📌 Overview

Dusk FSM allows you to display **HubSpot custom properties directly inside field service forms** using read only CRM widgets.

When Work is created from HubSpot, associated Contact, Deal, or Ticket data can automatically appear inside Dusk FSM — giving your field teams real time access to critical CRM information without switching systems.

This creates a seamless integration between **HubSpot CRM and field service operations**, while preserving HubSpot as the system of record.

📘 Before using this feature, ensure HubSpot is connected:
[Connecting HubSpot to Dusk FSM](https://help.duskmobile.com/article/Integrations/Connecting-HubSpot-to-Dusk-FSM)

---

## 🔎 What HubSpot Data Can Be Displayed in Dusk FSM?

You can display properties from:

* **Contacts**
* **Deals**
* **Tickets**
* **Custom properties** within any of those objects

These appear inside your form as **read only reference fields**.

Common examples include:

* Company name
* Contact phone number
* Deal stage
* Contract value
* Ticket priority
* SLA details
* Installation type
* Any HubSpot custom property relevant to field execution

Because the data is pulled directly from HubSpot, it always reflects the latest CRM record.

---

## 🛠️ How to Add HubSpot Fields to a Form

1. Navigate to **Operations → Forms → Form Builder**
2. Create a new form or edit an existing Work form
3. In the left sidebar, locate the **HubSpot Field** widget
4. Drag the widget onto the form canvas
5. In the widget settings:

* Select the **HubSpot Object Type** (Contact, Deal, or Ticket)
   * Select the **HubSpot Property** you want to display
6. Repeat as needed to display multiple properties

📝 HubSpot fields are **read only**.
Data flows one way from HubSpot into Dusk FSM when Work is created or linked via HubSpot. Field users cannot edit CRM data inside the form.

---

## 🔁 How the HubSpot Integration Works

When Work is created from HubSpot:

* The Work record is linked to the originating Contact, Deal, or Ticket
* Selected HubSpot properties automatically populate inside the form
* The data remains locked to preserve CRM integrity
* Field teams can reference CRM information without needing direct HubSpot access

This improves:

* Sales to field handover
* Operational clarity
* Data consistency
* Compliance and audit readiness

---

## 📌 Example Use Case

A technician opens a Service Report form and sees:

* Customer name and phone number from the HubSpot Contact
* Ticket summary and priority from the HubSpot Ticket
* Deal value or contract type from the HubSpot Deal
* A custom HubSpot property such as “Installation Type” or “Service Level”

All CRM data is visible but locked, ensuring alignment between Sales, Support, and Field Operations.

---

## 💡 Best Practice Tips

* Place HubSpot reference fields at the top of the form for context
* Use layout blocks to group CRM data clearly
* Combine HubSpot properties with dynamic Dusk FSM fields for operational capture
* Display contract terms, SLA conditions, or billing references directly in field forms
* Keep CRM data read only to maintain system of record integrity

---

## 🔗 Related Articles

* [Syncing Contacts Products Deals and Tickets](https://help.duskmobile.com/article/Integrations/Syncing-Contacts-Products-Deals-and-Tickets)
* [Accessing HubSpot Contacts in Dusk FSM](https://help.duskmobile.com/article/Integrations/Accessing-HubSpot-Contacts-in-Dusk-FSM)

---

Updated on February 24, 2026

Using HubSpot Custom Objects in Dusk FSM Forms

Need Support?

Error

Delete Article