Update Contact Field with Dynamic Values in Sparkforge Workflows

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Update Contact Field action writes to standard or custom fields, or clears custom fields, at runtime. Dynamic Values pull live data from earlier steps so you avoid hard-typed values.

The Update Contact Field action writes new data to a contact at the exact moment the workflow runs. Use it to keep records accurate for personalization, segmentation, and downstream branching.

What you can do

  • Update a standard or custom field with a static or dynamic value.
  • Clear a custom field (standard fields cannot be cleared).
  • Update multiple fields in a single action.

Add the action

  1. Open Automation → Workflows.
  2. Open or create a workflow.
  3. Click the + where you want the action.
  4. Pick Update Contact Field from the actions panel.

Configure the action

Action name

Use a description that reads clearly in Execution Logs (e.g., Set Confirmation Type).

Action type

  • Update field data — write a value.
  • Clear field data — wipe the value (custom fields only).

Update field data

  1. Pick the contact field.
  2. Enter a static value or switch to Dynamic Value to pull live data.
  3. Save. The new value overwrites the existing value when the workflow reaches this step.

Clear field data

  1. Set Action Type to Clear field data.
  2. Select one or more custom fields.
  3. Save. Field values become empty when the action runs.

Caution: clearing values changes Smart List membership, filter results, and downstream branching. Audit dependencies before publishing.

Dynamic Values

Dynamic Values resolve at runtime per contact. They are supported on these field types in this action:

  • Numeric — scores, counts.
  • Select / Dropdown — no option ID required here (this differs from If/Else conditions, which do require option IDs).
  • Monetary — totals, amounts.

Use a Dynamic Value

  1. Add an Update Contact Field action.
  2. Pick Update field data.
  3. Select the target field.
  4. In the value input, switch to Dynamic Value.
  5. Pick from an earlier step’s output or a stored contact field.
  6. Save and publish.

Example

A patient confirms an appointment. The workflow captures the confirmation type (Follow-up or New Visit) and writes it dynamically into a custom field, so the next branch sends the right reminder.

Validation

  • Text / Number: match the format of the field.
  • Date: use a valid date or date-based dynamic value.
  • Dropdown / Checkbox / Radio: value must match an existing option.
  • Email / Phone: use proper formatting.

Fields must already exist on the contact record. The action does not create new fields.

Frequently Asked Questions

Can I update standard fields like Email or Phone?
Yes. Update field data supports both standard and custom contact fields.
Can I clear standard fields?
No. Clear field data is restricted to custom contact fields.
Can I update multiple fields in one action?
Yes. Use Add field to stack multiple field rows inside one action.
How are Dynamic Values different from tokens?
Dynamic Values pick live outputs from earlier workflow steps or fields. Tokens still work, but Dynamic Values skip the manual mapping.
What happens if the value format is wrong?
The update fails validation. Check the field type and review Execution Logs for the failure reason.

Was this article helpful?