Ask For Input

How to Use the “Ask for Input” Action in Botassium

If you want your automation to collect structured responses from users—like an email address, a chosen option, or even a shared location—the “Ask for Input” action in Botassium is the right tool. It lets you request specific input types, validate the user’s response, and direct the flow based on success or failure.

This guide explains how to configure the action, set up validation, and handle different response scenarios.

What is the “Ask for Input” Action?

The Ask for Input node is an action that sends a message to the user and waits for a specific type of input. Once the user replies, the input is validated. Based on the result, the automation continues using one of two available paths:

• On Success: The input is valid and matches the requested format

• On Failure: The input is invalid or doesn’t match the expected type

You can then handle each case differently—whether it’s thanking the user for their input or prompting them to try again.

Setting a Variable Name

This action requires you to define a Variable Name, which stores the validated input.
Example: If you're asking for an email, set the variable as user_email. You can later use this variable in:

• Condition nodes (e.g., check if the email domain matches a rule)

• Reply messages (e.g., “Thanks, @user_email”)

• External system integrations (e.g., pass to a CRM or Google Sheet)

Supported Input Types

You can ask for different types of input depending on your use case. Here's what’s supported:

1. Email

• Prompts the user to provide a valid email address.

• Validates the format (e.g., user@domain.com)

• Commonly used in lead capture and support flows.

2. Website

• Requests a valid URL from the user (e.g., https://example.com)

• Great for gathering portfolios, store links, or submissions.

3. Number

• Accepts only numeric input (e.g., quantity, age, price)

• You can later use this value in conditions or calculations.

4. Location

• Asks the user to share their live location through WhatsApp’s built-in location sharing.

• Useful for delivery, dispatch, or service availability.

5. Option (via List)

• Displays a WhatsApp list with selectable options.

• Supports multiple grouped items and long menus.

• Ideal for product selection, FAQs, or service menus.

6. Option (via Buttons)

• Presents up to 3 buttons the user can tap to respond.

• Cleaner and quicker for simple choices (e.g., Yes / No / Maybe)

7. Poll

• Allows you to collect structured feedback or votes from users.

• Useful in communities, customer surveys, or event planning.

8. Free Text

• Accepts any text input.

• You can validate this input later using conditions or AI.

Flow Logic: Success vs. Failure

Each Ask for Input node has two exit paths:

• On Success: The user gave valid input. You can now continue the flow, save the data, send a confirmation, or take further actions.

• On Failure: The user’s input didn’t match the expected format. You can:

  • Send an error message

  • Ask them to try again

  • Route the flow differently

Example Use Case

You’re building a support bot and want to collect the user’s email address:

1. Add an Ask for Input node

2. Set the input type to Email

3. Set the variable name to user_email

4. On success, send a thank-you message and forward the email to your support team

5. On failure, reply with: “Please enter a valid email so we can reach you.”

The Ask for Input action works across all WhatsApp automations, and is especially useful in lead capture, order processing, surveys, data collection, user verification, and personalized experiences where structured user input is needed.