Read and write assets in an automation

Use Read assets to retrieve existing asset and Write assets to create or update asset.

Example: Register application using existing asset context

Scenario: IT asset owner needs new application record based on existing asset information, without overwriting original.

1. Use Read assets to load reference application and store it under asset.

2. Add Write assets with correct asset type, year, month, required Application ID and name.

3. Leave Asset selector empty to create new asset; selecting an existing asset updates that record. Use a distinct ID for test.

4. Store written output as new_asset, then log asset.name and new_asset.name.

5. Run once and verify new application appears with expected identity and fields. Do not repeatedly test writes with same identifiers until update behavior is understood.

Read existing asset

1. Add Read assets step.

2. Choose Asset type such as Applications, Servers, or Projects, or use variable.

3. Set Year and Month using fixed values or variables.

4. Select Asset.

5. Enter Store as variable, such as asset.

Create or update asset

1. Add Write assets step.

2. Set Asset type, Year, and Month.

3. Leave Asset unselected to create asset, or select existing asset to update it.

4. For new asset, fill all required fields shown for selected asset type. For Applications, screenshots show Application ID and Application Name as required.

5. Add optional fields, including owners, lifecycle, cost center, vendor, and custom values as applicable.

6. Set Store as variable, such as new_asset.

7. Save and run test.

Fields vary by asset type. Date fields expect YYYY-MM-DD; numeric custom fields expect numbers. Missing required values cause create run to fail.

Check outcome

Use Log step to record asset.name and new_asset.name. Log does not change variables or affect next step and messages capped at 10,000 characters.

Test against non-production example before scheduling asset updates.