Custom Fields — custom fields
Custom Fields (Bot Settings → Custom Fields) — a section for creating additional fields in the customer card. Standard fields already exist in Chatterfy: name, username, status, and Telegram ID. But o
Custom Fields (Bot Settings → Custom Fields) — a section for creating additional fields in the customer card.
Standard fields already exist in Chatterfy: name, username, status, and Telegram ID. But often they are not enough.
Custom Fields let you store any additional user data: trader ID, balance, country, language, source, manager's note, registration date, technical IDs, and other parameters.
When Custom Fields are needed
For example:
- the affiliate program returns trader_id
- AI identifies the user's country
- a manager leaves an internal note
- you need to save the deposit amount
- you need to pass data via webhook
- you need to branch the Flow based on user data.
Custom Fields are additional user variables. A field is created once in the bot settings and then appears in every customer card.

How Custom Fields are filled in
Fields can be filled in automatically or manually.
Method | How it works |
Automatically | Via Webhooks & API, AI Recognition, or external integrations |
Manually | An operator fills in the field in the customer card |
Fields are usually filled in manually for:
- notes
- manual moderation
- sales
- support
- data from external sources.
Where Custom Fields are used
After they are filled in, the values are available:
Where used | Purpose |
Condition | Flow branching based on user data |
AI | Personalizing logic and responses |
Messages | Inserting data into text |
Links | Passing parameters to external services |
Webhook | Updating or sending data |
Filters | Filtering users |
CRM | Displaying data in the customer card |
Custom Fields variables
To use values, use the following format: {{fields.ключ}}
Examples:
- {{fields.country}}
- {{fields.refId}}
- {{fields.depositAmount}}
Use the Field Key, not the field name.
How to create a Custom Field
1. Open Custom Fields
Go to: Bot Settings → Custom Fields. If the bot is new, the list will be empty.2. Click Add Custom Field
Click: Add Custom Field. This will open the form for creating a new field.3. Select the field type
The type determines: the storage format, validation, and input format.The type cannot be changed after creation. If you selected the wrong type, create a new field. You can hide the old field using Visible field.4. Fill in the parameters
For each field, specify:ParameterWhat it meansField KeyTechnical field keyNameField name for the operatorVisible fieldField visibility in the customer cardTypeData typeFor Select and Multiselect, also specify a list of values.5. Click Save
After saving, the field:appears in the systembecomes available in customer cardsstarts working in Flow and AI.
Field types
Type | What it stores | Example |
Text | Short text | Ivan |
Long Text | Long text | manager's note |
Link | Link | https://site.com |
Number | Number | 5000 |
Date | Date and time | 2030-01-30T10:20:30Z |
Select | One option from the list | Registered |
Multiselect | Multiple options | Football, Tennis |
Text
Text — a short text value. Suitable for: name. ID. country. language. short values. Example: India
Long Text
Long Text — long text. Typically used for: notes. comments. descriptions. internal data.
Link
Link — a link. Example: https://partner.com/user/123
Number
Number — a numeric value. Example: 5000
Date
Date — date and time. Format: 2030-01-30T10:20:30Z. The ISO 8601 standard is used.
Select
Select lets you choose one option from a list. For example: Registered. Deposit. Withdraw. Suitable for: status. country. language. category.
Multiselect
Multiselect lets you choose multiple values at the same time. For example: Football. Tennis. Crypto. Suitable for: interests. tags. attributes. categories.
Select and Multiselect — defining a list of values
For these types, you need to define a list of values in advance. Each value is entered on a new line. Example:
Registered
Deposit
Withdraw
Type | Difference |
Select | Only one option can be selected |
Multiselect | You can select multiple options at the same time |
If you need a free-form text value, use Text or Long Text.
Field Key
Field Key is the technical key of the field. It is used in webhook, AI, variables, API, and Flow.
Field Key example: depositAmount
Use in a message: {{fields.depositAmount}}
Use in webhook: ?fields.depositAmount=5000
For Field Key, use only Latin letters, with no spaces or special characters.
Name
Name is the display name of the field. The operator sees it in the CRM.
In Name, you can use: Russian. spaces. emoji. Examples: Deposit amount. Trader ID. User country.
Field Key and Name are different things.
Field Key | Name |
depositAmount | Deposit amount |
Visible field
Visible field determines whether the field is visible to the operator in the customer card.
Value | What happens |
Visible = ON | The field is displayed in the CRM and is available to the operator |
Visible = OFF | The field is hidden in the interface but continues to work in the system |
Visible = OFF is usually used for:
- technical data
- internal IDs
- hidden variables
- service logic.
Webhooks, Condition, and AI
Webhooks
A webhook can write values to fields. Example: ?fields.balance=5000. Learn more: Webhooks & API — receiving data from external sources.
Condition
Condition can check field values. For example: country = IN. After that, the user can enter the required Flow branch. Learn more: Condition — conditional branching.
AI Reply and Send Message
Custom Fields can be used in messages and AI. Examples: {{fields.country}}, {{fields.depositAmount}}.
AI Recognition
AI can extract data from text, screenshots, or images and automatically write it to Custom Fields. Learn more: AI Recognition — media processing.
Use cases
Arbitrage
The affiliate program returns: trader_id. A postback or webhook writes it to: fields.exnovaTraderId.
E-commerce
Fields are created: orderId, orderTotal, deliveryStatus. The webhook updates the order data automatically.
Support
AI determines the request category: Payment, Access, Technical issue — and writes it to a Select field.
What to keep in mind
- The field type cannot be changed.
- The field cannot be deleted.
- If you made a mistake: create a new field. Hide the old field via Visible field.
What the result should be
After configuring Custom Fields:
- the customer card becomes more flexible
- AI gets additional data
- Flow can branch based on values
- webhook can save information
- CRM stores the required user parameters.
If something does not work
The field does not appear
Check:
- whether the field has been saved
- whether the correct bot is open
- whether the field is hidden via Visible field.
The value is not written via webhook
Check:
- whether Field Key exists
- whether fields.* is written correctly
- whether there is an error in the request.
The variable is empty
Most likely, the field:
- has not been filled in yet
- or the wrong Field Key is being used.
You cannot change the field type
This is a system limitation. The type is fixed after creation.
Frequently asked questions
Related
Was this article helpful?








