> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/build/workflows/steps/set-field.md). # Set Field Step Write a value to a field on the lead partway through a workflow. The **Set Field** step writes a value to a field on the lead when the workflow reaches it. Use it to stamp the outcome of an engagement onto the lead record — a status, a tag, a flag your CRM or your team reads later. Unlike the [API Step](/build/workflows/steps/api.md), [CRM API Step](/build/workflows/steps/crm-api.md), and [Research Step](/build/workflows/steps/research.md) steps, which save fields as a side effect of calling out to something, Set Field does nothing but write. The value it writes is fixed by you, not discovered. ## Configuration ### Field Pick the field to write. The list covers your [Data Model](https://app.spara.co/data-model) fields plus any fields produced by API or Research steps earlier in the same workflow. You can also type a name that isn't in the list — useful for a CRM field Spara doesn't track yet. Read-only fields are not selectable, and a write to one is ignored. ### Value The value to write. It supports variables, so you can compose it from lead data: ``` {{ first_name }} — engaged via {{ channel }} ``` ## Behavior * **The step always runs.** Set Field has no conditions of its own. To make a write conditional, put a [Condition Step](/build/workflows/steps/condition.md) step in front of it. * **The trust hierarchy still applies.** A Set Field write is trusted at the same level as self-reported and CRM data, so it will not overwrite a value that came from a more trusted source — see [Data Model](/build/data-model.md). * **It syncs like any other field.** If the field is mapped to your CRM, the new value is pushed there. Test leads are the exception: a test run writes the field in Spara but never pushes it to your connected systems. ## Example: Flag leads the agent finished with ``` Condition: engagement_outcome is defined → Set Field Field: spara_engagement_status Value: Complete ``` A downstream Condition step, a CRM sync, or a Leads filter can then act on `spara_engagement_status`. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.spara.com/build/workflows/steps/set-field.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.