Managing IT documentation effectively means keeping your data accurate, consistent, and as automated as possible. With the introduction of Connected Fields in Hudu, this task just became a whole lot easier. This powerful feature lets you link individual fields in an asset layout to specific data points from your integrations—streamlining documentation and offering more layout flexibility.
What Are Connected Fields?
Connected Fields allow you to bind a specific field in an asset layout to a data point from an integration. Once connected, the field is automatically populated with the value from the integration and updates with each sync.
While integration cards in Hudu already reflect live, synced data, Connected Fields allow you to embed that same data directly into custom fields on your asset layouts. This gives you more control over how and where integration data appears, reducing the need to rely solely on integration cards for visibility.
How to Set Up Connected Fields
Fields can only be connected to an integration if the field is in an asset layout that is a sync location for the integration either by sort rule or primary/default sync location.
Navigate to the asset layout connected to an integration and click edit for each field you would like to be connected. Under the Sources section, select the respective Integration from the dropdown. Then select the Integration data point you would like to connect to the field.
Please note, you will not see these dropdowns if the asset layout is not connected to an integration.
Once fields are connected to an integration, an indicator will appear next to each connected field when viewing the asset layout in Admin > Asset Layouts. Additionally, an informational banner will display, noting that the asset layout contains one or more fields linked to an external source. This banner will also be visible on the asset itself. Synced fields from the integration will be displayed above the integration card.
If you would like these fields to show in the asset list view, make sure to check Show in List View for each field.
Supported Integrations
Connected Fields supports integration with the following platforms:
| • Addigy | • Atera | • AutoTask |
| • Auvik | • Kaseya BMS | • ConnectWise PSA |
| • Datto Backup | • Datto RMM | • Domotz |
| • Halo PSA | • Meraki | • N-Central |
| • NinjaOne | • N-able N-sight | • Microsoft Office 365 |
| • Pulseway RMM | • RepairShopr | • Syncro |
| • Watchman | • Intune |
Supported Field Types
You can connect the following field types to integrations:
- Text
- Rich text
- Copyable text
- Phone Number
Note: List select, asset link, heading, and confidential text fields are not supported, and custom fields created in integrations are not yet available for connection.
Required Fields and Sync Behavior
- Assets may be auto-created during sync if at least one field is connected, even if required fields are incomplete.
- These assets are flagged visually (red banner and icon) until the required fields are completed.
- If a required connected field is empty in the integration, it will also be empty in Hudu. Make such fields required in the integration to ensure completeness.
Editing Connected Fields
You can edit the value of a connected field in Hudu, but it will be overwritten during the next sync. Connected fields are not bidirectional, so changes made in Hudu will not sync back to the integration.
Cross-Company Considerations
Connected Fields only work if the company associated with the asset has a match in the integration. Otherwise, the fields behave like standard Hudu fields.
Benefits of Connected Fields
- View integration data directly in table views
- Track changes via activity logs and version history
- Create assets populated by multiple sources (integration + Hudu)
- Reduce manual entry and improve documentation accuracy
Connected Fields mark a significant evolution in how Hudu handles integration data. By making integration data available at the field level, documentation becomes more flexible, maintainable, and powerful, allowing your team to work smarter with less manual effort.
FAQ
Answer: Right now, it isn’t possible to specify which IP address is pulled for the connected field, since data points are standardized across multiple integrations. With NinjaOne in particular, the integration defaults to the public IP address and only uses other addresses if the public IP isn’t available.