Human Interaction Node Guide

Introduction

Learn how to use the Human Interaction node in BrowserAct to handle manual login, verification, and decision-making steps. Step‑by‑step guide with a Quora login example.

Detail

Empower your workflow with human decision-making when automation alone isn’t enough. The Human Interaction node temporarily hands browser control to the user—perfect for login flows, captchas, manual reviews, or any step requiring human judgment.

What Is the Human Interaction Node?

The Human Interaction node pauses your automated workflow and allows a human to directly operate inside the browser. Once the user completes the required action and clicks Resume, the workflow continues automatically.

When Should You Use It?

Use the Human Interaction node when your workflow involves:

Login or verification steps requiring manual input (e.g., email/SMS codes)
Captcha-protected websites
Platforms with unpredictable human-first UI elements
Steps requiring judgment (e.g., choosing a category or confirming an action)

Key Features

Flexible Notifications
Supports in-app notifications and optional email notifications.
Two Execution Modes
Perform actions directly in the BrowserAct interface or via a standalone Web interface accessible from email.
Automatic Workflow Resume
Once the human step is completed, control returns to the AI workflow seamlessly.

Usage Rules

The node can be placed anywhere in the workflow.
You can customize the human intervention time limit.
Email notifications can be sent to any valid email address.
Each Human Interaction node can include multiple required tasks before exiting.

Setup Guide (Step-by-Step)

1. Insert the Human Interaction Node

Click the + button in your workflow, then select Human Interaction from the node library.

2. Configure Basic Settings

Instruction for Human

Write clear instructions that explain what the user must do.

Example:

"Please enter your username, password, and verification code."

Time Limit

Sets the maximum duration allowed for human intervention.

When the time expires, the workflow exits this step immediately.

Notify When This Step Starts

Checked: Send an email notification to the entered address. The user can perform the task through a standalone Web interface—ideal when they are away from the computer.

Unchecked: The user performs the intervention directly inside the BrowserAct interface.

Example: Quora Post Scraper (with Human Login)

This example demonstrates how to use the Human Interaction node to log in to Quora and extract post data.

Before You Start

Set up required parameters:

Keyword: Default = “Scraper”
Datelimit: Default = “5” (number of posts to extract)

Adjust based on your scraping needs.

1. Start Node – Parameter Settings

Set:

Keyword = Scraper
Datelimit = 5

2. Add a Visit Page Node

Goal: Navigate to Quora
Action: Enter URL: https://www.quora.com/

3. Add Condition Node

Goal: Detect whether the user is logged in.

Action:
Enter: Does a login box appear on the page?

You may customize this based on platform (e.g., check for login button in the top-right corner).

4. Add Human Interaction Node (True Branch of Condition)

Goal: Allow manual login using username/password and any required verification.

Actions:

In the instruction field, enter:
“Please enter your username and password to complete the login process.”
Leave Notify when this step starts unchecked to complete the action directly in the interface.
You can adjust this behavior depending on your workflow.

5. Add Input Text Node

Goal: Enter the keyword into Quora’s search box.

Actions:

Input Field Position: “The search box at the top”
Text to Input: Type “/” to reference the Keyword parameter
Check Press Enter after typing

6. Extract Data

Goal: Extract post information from the search results.
Actions:

Enable Full Page
Data Field:
“Extract the POST title, description, number of followers, and POST URL from the current page.”
Filtering Criteria:
“Extract only the first /Datelimit entries”