ElpidanElpidanLead

Custom Fields Menu

Custom fields are used to store values. They hold structured data collected from users or set by automation. Unlike tags, fields can store information such as numbers, text, dates, or boolean values.

What Custom Fields are used for

Custom fields are commonly used to:

• Store user-provided data (name, email, phone, age, address, education)
• Track numeric values (scores, purchase amounts, counters)
• Save dates (appointments, registrations)
• Power conditions, comparisons, and personalization

Field values can later be used in:

• Condition Nodes
• Message placeholders
• Contact filtering
• Data export


Internal Fields

 At the top of the Custom Fields menu, you’ll see a section labeled Internal Fields. Clicking on this section displays the list of available internal fields.


Internal Fields are predefined fields provided by Elpidan and available by default.

These fields cover commonly used contact information, such as:

• First name and last name
• Gender
• Phone number and mobile
• Email address
• Country, city, province
• Company name
• Social links (Instagram, LinkedIn, etc.)
• starred, and blocked status

Internal Fields behave like regular fields inside flows, but:

• They are created by the system
• They cannot be deleted
• They are always available for use

User-Defined Fields

In addition to Internal Fields, you can create your own custom fields based on your business needs.

User-defined fields are useful for storing data specific to your workflow, such as:

• Age
• Education level
• Job title or industry
• Contest score
• Total purchase amount
• Course progress or internal metrics

These fields are fully customizable and managed by you.


Organizing Fields using Folders

To keep your fields organized, you can group them into folders.

Folders help you structure fields based on purpose, such as:

• General information
• Products or purchases
• Campaigns or contests
• Feedback and surveys

Creating a Folder


Hover over the Folders section in the left panel and click the plus (+) icon

Enter a folder name
Confirm to create the folder


Creating a User-Defined Field

Click Create New Custom Field
Enter a field name
Select the field type (Text, Number, Boolean, Date)
Choose a folder (optional)
Save the field

Field Types

When creating a custom field, you must choose its type.

Common field types include:

Text – names, cities, preferences
Number – age, score, purchase amount
Date – appointment or registration date
Boolean – true / false values

Choosing the correct field type is critical for:

• Accurate conditions
• Valid comparisons
• Reliable personalization


How Field values are assigned

Field values can be assigned in two ways: automatically or manually.

Assigning Fields Automatically (using Flows)

Fields are most commonly populated inside flows using:

User Input Node – saving user replies
Action Node – setting, updating, or clearing values

This allows structured data collection and automation.

 

Once stored, field values can be:

  • Used in Condition Nodes
  • Inserted into messages using placeholders
  • Filtered in the Contacts list
  • Exported

Assigning Fields Manually (from the Inbox)

You can also edit field values manually from the Inbox.


To do this:

Click on then Inbox Menu
Open a conversation
Go to the Contact Details & Management Panel (Section 3)

Edit, add, or remove field values


This is useful for manual corrections or support cases.


Updating and clearing Fields

Fields can and should be updated over time.

Common use cases:

• Update values as users progress
• Clear temporary or outdated data

Example:

• Clear temporary_answer after processing
• Update customer_stage as the user advances

Related guide: Managing Fields (Set / Update / Clear)


Tag vs Field: choosing correctly

Use a Tag when:

• You need yes/no logic
• You are tracking state

Use a Field when:

• You need values
• You need comparisons
• You want personalization

This distinction keeps flows readable, scalable, and predictable.

Was this article helpful?

Didn't find your answer?

Contact us