Introduction
Set custom field writes a value to a device-level custom field when an automation runs. Use it to record state changes, stamp timestamps, track lifecycle status, or feed custom field data into downstream automations via the Custom Field Changed trigger.
💡 TIP: Combine this action with the Custom Field Changed trigger to build multi-step workflows. For example: automation A sets a field to "Pending Reboot," and automation B triggers on that change to schedule the restart.
Set Custom Field
In Step configuration, two dropdowns are required:
Custom field — Select the field you want to write to. All custom fields in your organization appear here.
Variable — Select from the automation variables you've defined for this automation. The value of the selected variable is written into the field when the action runs.
Click Save.
ℹ️ NOTE: The Variable dropdown is populated by the automation variables you've already configured. If the dropdown is empty, you'll need to define variables on the automation before this action can write anything meaningful.
⚠️ WARNING: This action sets a device-level override. Once written, this device uses its own value and won't pick up future changes to the group or organization default for this field — until the override is cleared. See Device Details → Custom Fields to clear a device-level override manually.
Conditions
The Conditions section lets you restrict when this action runs based on device attributes or the outcome of a previous action.
See Action Conditions for the full reference on condition types, operators, and values.
Additional Options
Expand Additional options for action name, failure behavior, output variable assignment, retries, and the enabled toggle.
See Actions Overview for the full reference on additional options available on every action.
FAQ
Where do I create the custom fields that appear in this action? In Workspace → Custom Fields. Fields must exist before they can be targeted by this action.
Does writing a value via this action trigger the Custom Field Changed automation? Yes, if an automation uses the Custom Field Changed trigger for that field, it will fire when this action writes a new value. Level resolves field values at execution time — the updated value is active immediately for any subsequent automation or script run.
Can I clear a field's value with this action? The action writes a value; it doesn't clear one. To revert a device back to inheriting from its group or organization default, clear the override manually in Device Details → Custom Fields using the ⋮ menu on the field row.
Who can configure this action, and can it write to admin-only fields? Any technician with permission to edit automations can configure this action. For admin-only fields specifically — only organization administrators can see or edit those values. Whether an automation running as a non-admin technician can write to an admin-only field via this action should be verified in Workspace → Custom Fields.