Skip to main content

Message Box

Displays a message box with specified text and title.

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

If the ContinueOnError property is true, no error is caught when the project is executed even if Catch node is used.

Input​

  • Text - The text to display on the message box.
  • Title - The title of the message box.

Output​

  • Confirmed - Indicates whether the user clicked on the "Yes" button.

Options​

  • Type - The type of the message box.
    • "Yes / No" - Displays a message box with "Yes" and "No" buttons.
    • "Info" - Displays an information message box.
    • "Error" - Displays an error message box.

How It Works​

The Message Box node performs the following steps:

  1. Pauses Execution - Stops the automation flow and waits for user acknowledgment
  2. Displays Dialog - Shows a modal dialog box with the specified title and message
  3. Applies Type Styling - Displays appropriate icon and buttons based on the Type setting:
    • Yes/No: Shows question icon with Yes and No buttons
    • Info: Shows information icon with OK button
    • Error: Shows error icon with OK button
  4. Waits for Response - Dialog remains open until user clicks a button
  5. Captures Response - For Yes/No type, records which button was clicked
  6. Returns Result - Outputs true if Yes was clicked, false if No was clicked (for Yes/No type)
  7. Resumes Flow - Continues automation execution after user responds

Requirements​

  • Desktop Environment - Must run in an environment where dialog boxes can be displayed
  • User Interaction - Requires a user to be present to acknowledge the message
  • Display Availability - Needs an active display/screen to show the dialog
  • Attended Automation - This is an attended automation node, not suitable for unattended scenarios

Error Handling​

Error CodeDescriptionSolution
DISPLAY_NOT_AVAILABLENo display available to show the dialogEnsure automation runs in a desktop environment
DIALOG_TIMEOUTDialog was not responded to within timeout periodEnsure user responds to the dialog promptly
INVALID_TYPEInvalid message box type specifiedUse one of the valid types: Yes/No, Info, or Error

Usage Examples​

Example 1: Confirm Before Proceeding​

Ask user to confirm before executing a critical operation:

Input:
- Title: "Confirm Deletion"
- Text: "Are you sure you want to delete all temporary files?"
- Type: Yes / No

User clicks "Yes"
Output:
- Confirmed: true

Next: Use If Condition to check Confirmed value and proceed with deletion

Example 2: Display Process Completion​

Notify user when a long-running process completes:

Input:
- Title: "Process Complete"
- Text: "Data import completed successfully. 1,250 records processed."
- Type: Info

User clicks "OK"
Output:
- (No output needed for Info type)

Example 3: Display Error Notification​

Alert user about an error that requires attention:

Input:
- Title: "Connection Error"
- Text: "Unable to connect to database server. Please check your network connection and try again."
- Type: Error

User clicks "OK"
Output:
- (No output needed for Error type)

Usage Notes​

  • Blocking Operation - The automation pauses completely until the user responds to the message box.
  • Yes/No Output - Only the "Yes / No" type produces a boolean output in the Confirmed property.
  • Info and Error Types - These types only have an OK button and don't produce a meaningful output value.
  • Modal Dialog - The dialog appears on top of other windows and requires user action before continuing.
  • Platform Appearance - Dialog appearance and icons vary by operating system (Windows, macOS, Linux).
  • No Timeout by Default - The dialog will wait indefinitely for user response unless timeout is configured.
  • Multiple Messages - For multiple sequential messages, consider combining them into one dialog when possible.

Tips​

  • Clear Communication - Write clear, concise messages that tell users exactly what they need to know.
  • Appropriate Type Selection - Use Info for notifications, Error for problems, and Yes/No for decisions.
  • Avoid Overuse - Too many message boxes can frustrate users. Use sparingly for important notifications.
  • Action-Oriented Text - For Yes/No dialogs, phrase questions to make Yes/No responses clear.
  • Handle Both Responses - For Yes/No type, always implement logic for both true and false outcomes.
  • Error Context - For error messages, include specific details about what went wrong and how to fix it.
  • Log Important Choices - When using Yes/No, log the user's choice for audit purposes.
  • Consider Alternatives - For unattended automation, use logging or notifications instead of message boxes.
  • Input Box - Prompt users to enter text input