Skip to main content
The Get User Data feature allows you to pause the conversation and wait for specific information from the user. This is essential for collecting leads, qualifying customers, and storing data for later use.

​
How to Configure

1

Add the Block

Inside the Flow Builder:
  1. Click Add Content on any node.
  2. Select Get User Data from the menu.
2

Ask the Question

Type the text prompt the user will see (e.g., “What is your email address?”).
3

Configure Input Type

Click the Edit button (pencil icon) on the input block to open settings.
  • Reply Type: Choose the format you expect (Email, Phone, Number, etc.).
  • Save to Custom Field: Select or create a variable (e.g., {{user_email}}) to store the answer.
Crucial: Always map the user’s response to a Custom Field. If you skip this, the data will not be saved and you cannot use it later in the flow.

​
Input Types Reference

Choose the correct input type to automatically validate user responses.
TypeValidation LogicIdeal Use Case
TextAccepts any text string.Names, comments, feedback.
NumberEnforces numeric values only.Age, quantity, zip codes.
EmailChecks for valid email format (@ and .).Lead generation, registration.
PhoneValidates phone number formats.Contact info, SMS opt-in.
ImageAllows image file uploads.ID verification, product returns.
FileAccepts documents (PDF, Doc).Resumes, contracts.
LinkChecks for valid URLs.Portfolios, social profiles.
LocationRequests GPS coordinates.Delivery, finding nearby stores.
DateOpens a date picker.Birthdays, reservations.
Date & TimeOpens date + time picker.Appointment scheduling.
Multiple ChoiceUser selects from buttons.Surveys, product categories.

​
The “Any Input” Type

New Feature: “Any Input” is the most flexible option. It accepts text, numbers, links, or mixed content without triggering validation errors.
Use Any Input when:
  • You don’t know exactly what format the user will use.
  • You need complex responses (e.g., “Order #12345, see photo here”).
  • You want to reduce friction and avoid error messages during support chats.

​
Best Practices

Use Descriptive Variables

Name your Custom Fields clearly (e.g., {{shipping_address}} instead of {{data_1}}) so you can easily find them later.

Validate Critical Data

Always use specific types like Email or Phone for contact info to ensure you collect usable data.

Provide Examples

In your question text, give the user a hint: “Please enter your date of birth (MM/DD/YYYY).”

Handle Errors

If validation fails (e.g., invalid email), the bot will ask again. Ensure your error message is helpful.