Workflow Action: Set Field Value
Action: Set Field Value
Use this action when you want a workflow to automatically write a value into a field — for example, recording an internal status marker, a calculated eligibility flag, or a routing code that reviewers or other workflows can use later.
This can be added to a rule's Then step or its optional Otherwise step; configuration works identically in either place.
Configuring it
Step 1: Choose the Field. Only fields that are hidden from submitters appear here. This is a deliberate safeguard: it guarantees a workflow can never silently overwrite an answer an applicant actually typed in. If the field you want to set doesn't appear in the dropdown, it's likely still visible to submitters — go to the Form Builder and change that field's visibility, then come back.
Step 2: Enter the Value. The input adapts to match the field type you picked — a dropdown of that field's own options, a number input, or free text, depending on how the field is set up.
Things to watch for
- "No matching fields in this program" means your program doesn't currently have any hidden-from-submitter fields. You'll need to create one (and set it hidden) in the Form Builder before this action has anywhere to write to.
- Because only hidden fields are eligible, Set Field Value is best thought of as a way to store internal, admin-only data — not a way to correct or overwrite applicant answers.
What's next
- See Choosing a Workflow Action for the full list of available actions.
- Need to combine several numeric fields into one total instead of setting a single value? See Total & Set Field Value.
- See Understanding Execution Logs & Troubleshooting Workflows to confirm a value was actually written for a given submission.