Create Halo Asset
The Create Halo Asset workflow action checks the selected Asset Type, creates one asset in Halo PSA, then returns the saved asset with refreshed details.
When to Use This Action
Use this action when you need to:
- Register an asset found in an alert, form, or other automation
- Assign an asset to a Halo Asset Type and Site
- Set type-specific Asset Fields and asset Custom Fields
Do not use this action when the asset may already exist. Query first, then branch to either Create Halo Asset or Update Halo Asset.
How It Works
Think of the selected Asset Type as the asset template. It tells the action which Asset Fields Halo expects and which fields Halo marks as mandatory.
Mandatory Asset Fields stop an incomplete create
Before creating the asset, the action reads the current Asset Type metadata from Halo. If a mandatory Asset Field has no value, the action lists the missing fields and does not create the asset.
The Site determines the asset location
Site is required. Client helps narrow the Site selector, but selecting a Client does not replace the required Site.
Refreshed details reflect the saved asset
After Halo creates the asset, the action retrieves it again by ID. The stored result contains Halo's current field projections and status details. If that refresh fails, the action does not create a second asset.
Configuration
Connection
| Field | Description |
|---|---|
| Halo Connection | Select the Halo connection to use. |
Type and Location
| Field | Description |
|---|---|
| Asset Type | Required. Selects the asset type and loads its Asset Fields. |
| Client | Optional. Narrows the Site list and is not sent independently. The selected Site determines asset ownership. |
| Site | Required. Selects the asset's Halo site. |
Asset Details
| Field | Description | Default |
|---|---|---|
| Inventory Number | Optional inventory number. Halo does not assign one automatically when you omit it. Supports text expressions. | None |
| Notes | Optional asset notes. Supports text expressions. | None |
| Status | Optional Halo asset status. | Halo default |
| Inactive | Create the asset as inactive. | Disabled |
Asset Fields
| Field | Description |
|---|---|
| Asset Fields | Set fields defined by the selected Asset Type. Complete every field Halo marks as mandatory. |
Custom Fields
| Field | Description |
|---|---|
| Custom Fields | Set asset Custom Fields. Halo field IDs identify each assignment. |
Error Handling
| Field | Description |
|---|---|
| Error Handling | Choose Exception, Bounce, Continue, Stop, or Stop All when metadata, creation, or refresh fails. |
Returned Variables
The stored result is the refreshed Halo asset object.
| Variable | Type | Description |
|---|---|---|
.id | number | New Halo asset ID |
.inventory_number | string | Inventory number |
.notes | string | Asset notes |
.assettype_id / .assettype_name | number / string | Asset type |
.client_id / .client_name | number / string | Client |
.site_id / .site_name | number / string | Site |
.status_id / .status_name | number / string | Asset status |
.inactive | boolean | Whether the asset is inactive |
.fields | array | Asset Field IDs and values |
.customfields | array | Custom Field IDs and values |
For example, use {{custom.createdAsset.id}} to reference the new asset ID.
FAQs
Why can I not save an asset without a Site?
Halo assets require a specific location for this action. Select a Client first to narrow the Site list, then select the Site.
Why did the action report missing fields?
The selected Asset Type currently marks those Asset Fields as mandatory in Halo. Add values for the listed fields and run the action again.