Dify Plugin

​

Why Use Actionbook in Dify

• Start from verified selectors and action manuals instead of guessing from raw HTML.
• Combine Actionbook search/get tools with live browser automation in one Dify workflow.
• Recover from selector drift by taking a fresh accessibility snapshot and continuing the run.

​

Included Tools

​

Installation

1. Open the Actionbook plugin page.
2. Click Install.
3. Enable the plugin in your Dify workspace.
4. Configure the plugin credentials before running browser workflows.

​

Credentials

​

Actionbook API Key

• Optional for search_actions and get_action_by_area_id.
• Leave it empty to use the free tier, or add a key for higher quotas.
• Get a key from actionbook.app.

​

Hyperbrowser API Key

• Required for browser_create_session, browser_operator, and browser_stop_session.
• Get a key from Hyperbrowser.

​

Recommended Workflow

1. search_actions to find a relevant page area.
2. get_action_by_area_id to retrieve the full selector manual.
3. browser_create_session to start a cloud browser session.
4. browser_operator for navigation and page interaction.
5. browser_stop_session to release the session when the workflow finishes.

search_actions(query="github login", domain="github.com")
get_action_by_area_id(area_id="github.com:login:email-input")

browser_create_session()

browser_operator(
  session_id="<session_id>",
  cdp_url="<ws_endpoint>",
  action="navigate",
  url="https://github.com/login"
)

browser_operator(
  session_id="<session_id>",
  cdp_url="<ws_endpoint>",
  action="snapshot"
)

browser_stop_session(session_id="<session_id>")

• browser_operator accepts either session_id or cdp_url; for multi-step workflows, pass both for the best recovery behavior.
• browser_create_session returns ws_endpoint, which should be passed to browser_operator as cdp_url.
• snapshot is a fallback step when selectors fail or page state changes, not a mandatory success-path step.
• browser_stop_session should be called after each browser workflow to release the remote session cleanly.

​

Browser Operator Tips

• Use fill for form inputs when possible. It clears and writes the value in a single step.
• Use snapshot after navigation, after major page changes, or whenever a selector fails.
• Snapshot responses include accessibility refs like [ref=e3]; these are often the most reliable selectors for follow-up click and fill calls.
• Always call browser_stop_session at the end of the workflow to avoid unnecessary browser billing.

​

Example Use Cases

• Search or filter content on dynamic web apps.
• Combine Actionbook search/get tools with browser automation for agentic task execution.
• Recover from selector drift by taking a fresh snapshot and continuing the workflow.