Save to Contact Field
Write a value onto a custom contact field, so an answer collected in the conversation lives on the record, not only in the transcript.
Quick start
- Go to Automate → Workflows and open a workflow. Click + and pick Save to Contact Field.
- Under Contact field, pick from the list. If it is empty, first create a field under Settings → Custom fields.
- Set Value — usually
{{answer.text}}, what the customer answered, right after an Ask a Question step. - Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.
Watch out
- It cannot create a field — the field must already exist under Settings → Custom fields, or the step fails.
- The AI agent can write fields too. Which ones it may write is chosen on the agent's Actions page.



Details
Getting here
Automate → Workflows, open a workflow, click + on the canvas, then pick Save to Contact Field under Add Steps.
Before you start
- An owner, admin or agent can add this step and save the workflow. Publishing that workflow — the thing that makes it run on live conversations — is an owner or admin action.
- Building and running workflows depends on your plan; see pricing.
- The custom field must already exist under Settings → Custom fields. This step cannot create one.
Set up
- Open the workflow and click + where the write belongs.
- Pick Save to Contact Field.
- Choose the field under Contact field — only fields already defined for this workspace are listed.
- Set Value, usually a placeholder like
{{answer.text}}right after an Ask a Question step, or plain text. - Save the step. To publish: set Status to Published in the toolbar at the top of the editor, click Save, then confirm with Publish. The dropdown on its own changes nothing until you save.
Fields
- Contact field
- Which of this workspace's declared custom fields to write.
- Limits: Lists only fields already created under Settings → Custom fields; this step cannot create one.
- Value
- The text to store, usually a placeholder that resolves from the run.
- Limits: A value that resolves to nothing fails the step rather than clearing the field — see When it fails.
How it works
- The step resolves the contact behind this conversation and writes the value onto that field on their record, replacing whatever was there before — it never merges or appends.
- The field key is checked against this workspace's declared custom fields before anything is written; a key that is not one of them is refused rather than saved into a place nothing else reads.
- The value is rendered through the run's placeholders and trimmed before it is written, so
{{answer.text}}becomes the customer's actual answer. - If this same run also tries to send the customer something, and every one of those sends fails, the field goes back to what it held before.
- That rollback does not happen if something else has changed the value again since. And a run that never tries to send anything to the customer is not affected by any of this.
- The same writer backs Ask a Question's own "save response as a contact field" option, so a value saved either way behaves identically once it lands on the record.
When it fails
- No field chosen: the step fails outright — this can only happen on a step an AI builder saved with no key, since the drawer requires picking one.
- The field named is not one this workspace has declared: the step fails and nothing is written. The message reads “‘<field>’ is not a contact field in this workspace — create it under Settings → Custom fields”. Publishing refuses such a flow with the same words, so a published flow can only reach this if the field was deleted after it went live.
- This conversation has no linked contact: the step fails with this conversation has no contact to write to.
- The value resolves to an empty string — a missing placeholder with no fallback text, for example.
- The step fails with nothing to store in “<field>” — the value resolved to empty, rather than writing a blank that a later condition on “exists” would then wrongly pass.
- A failed write does not stop the run: the step shows as failed in the run's Activity tab and the flow moves straight to the next one, with the field left exactly as it was.
Limits
- It cannot create a custom field — only write to one that already exists.
- It cannot clear a field to empty. Writing an empty value fails the step instead of blanking the record; there is no “remove this field's value” action.
- It always replaces the field's value; it cannot append to, or merge with, whatever is already stored.
- It only writes to the contact behind this one conversation — not to any other contact, and not to the conversation itself.
- It does not fire this workspace's Contact Field Updated trigger for other workflows. Only a change made in Contacts, the inbox sidebar, the app or the public API does that — use Trigger Another Workflow to hand off on purpose instead.
- There is one exception, though: writing a date-typed field is still visible to Contact Date Reached.
- That trigger checks every 10 minutes the date field each published Contact Date Reached workflow names — regardless of who wrote the value.
- So a date this step saves can still start those workflows.
Best practices
- Place it directly after the Ask a Question step whose answer it stores, so the placeholder it reads is still fresh in the run.
Use cases
- After asking "What's your monthly budget?", save
{{answer.text}}into abudgetcontact field so it shows on the contact sidebar for the next conversation, not just this one. - Save a customer's plan name, posted by an Incoming Webhook, onto a custom field named “Signup Plan”, so a later broadcast can segment by it.
Reading this with an AI assistant? Plain Markdown version.