Flow builderSet field

Save a value on the contact, or add to a score

Start your free trial

Free for 7 days, no credit card required

A question saves what they said; Set field saves what you decide. Write up to 10 values on the person in one step, checked against each field’s type, and every later flow, condition and teammate can read them.

  • Meta's official API, no password, nothing installed
  • Unlimited contacts on every plan
  • AI replies in your customer's language
  • From $29 a month
What you set

Every setting, in the editor’s words

The labels you will see in the app, what each one does, and the rule behind it.

The step

Its settings, in the inspector’s words.

Save a valueWrite a value

Type a value, or insert a variable from an earlier step: an answer, a built-in like {{first_name}}, or an HTTP answer like {{order.status}}.

A value that does not fit the field’s type is left out and shown in the run.

Add to itKeep a score

Adds a number to what the field holds, 0 when empty; a negative number takes away. Add 10 when they ask for the price, then route the hot ones with a condition.

The value must be a number; an empty field counts as 0.

Clear itEmpty a field

Removes what the field holds, like a coupon that has been used.

ChangesUp to 10 changes, in order

One step makes up to 10 changes, each field once, run top to bottom.

The fields

What a Set field step can write to.

New field…Make a field from the step

Name a new field right in the step; it is created when you save the flow, so you never leave the canvas to set one up.

Names start with a letter; built-in names like email have their own place.

Your fieldsSix types

Custom fields hold text, a number, a date, a date and time, yes or no, or one of your choices, and are checked against that type on every write.

On the contactName, email and phone too

The contact’s own Name, Email and Phone can be set or cleared from a flow, never added to.

Read everywhere

Fields show on the contact in People, any message can say them back, and a condition can compare them.

In the app

Set field, as you set it

On the Roast menu flow: every visit adds 1 to Menu visits, a number field on the contact.

Changes
Up to 10 in one step: set, clear, or add to it.
Add to it
Adds to what the field holds, 0 when empty; a negative number takes away.
In the app

Every field, in People

Your custom fields in People, with how many people have each filled and which step fills it, above the built-in fields every contact has.

Filled by
The question or Set field step that writes it.
Built-in fields
Name, username, email, phone and more, on every contact.
The limits

The numbers behind it

What one Set field step allows.

WhatThe limitSet by
Changes in one stepUp to 10, each field once, in orderCommentWatchDog
What a change doesSave a value, add to it, clear itCommentWatchDog
Field typesText, number, date, date and time, yes or no, choiceCommentWatchDog
Add to itNumbers only; empty counts as 0; a negative takes awayCommentWatchDog
Name, Email, PhoneSet or cleared, never added toCommentWatchDog
A value of the wrong typeLeft out, the rest still run, the run says whichCommentWatchDog

All numbers are the Set field step’s own; Meta sets no rule on what you store about a contact.

Questions

Questions about fields

What people ask before they store data on a contact.

Yes. Choose Add to it on a number field: each time someone reaches the step the number grows (from 0 when empty), and a negative number takes points away. A condition can then read it, like lead_score is at least 50.

Six: text, number, date, date and time, yes or no, and choice. Every value a flow writes is checked against the field’s type.

Yes. Values can use variables, and an HTTP request earlier in the same run makes its answer one, read with a dotted path like {{order.status}}.

Yes, Name, Email and Phone can be set or cleared from a flow. They cannot be added to, which only makes sense for numbers.

That change is left out, the other changes still run, and the run’s history says which field was left out, so a typed “sometime soon” never lands in a date field.

No. Pick New field… in the step and name it; the field is made when you save the flow. Fields made in People show up here too.

Turn tonight's comments into conversations

Meta API approved Start your free trial

Free for 7 days, no credit card required

Save answers on the contact

Try free