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, CRM API Step, and Research Step 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 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 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.
• 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.