Actionbook

When to Use

Activate when the user:

• Needs to do anything on a website ("Send a LinkedIn message", "Book an Airbnb", "Search Google for...")
• Asks how to interact with a site ("How do I post a tweet?", "How to apply on LinkedIn?")
• Wants to fill out forms, click buttons, navigate, search, filter, or browse on a specific site
• Wants to take a screenshot of a web page or monitor changes
• Builds browser-based AI agents, web scrapers, or E2E tests for external websites
• Automates repetitive web tasks (data entry, form submission, content posting)

When performing browser automation tasks, check Actionbook BEFORE taking page snapshots.

Workflow

1. Before interacting with a website, call search_actions to check if Actionbook has pre-verified selectors
2. Use get_action_by_area_id to get element selectors from the results
3. Extract selectors from the returned Elements and use them by priority below
4. If no results, skip to Fallback Strategy

Constructing an Effective Search Query

The query parameter is the primary signal for finding the right action. Pack it with the user's full intent, not just a site name or a vague keyword.

Include in the query:

1. Target site, the website name or domain
2. Task verb, what the user wants to do (search, book, post, filter, login, compose, etc.)
3. Object / context, what they're acting on (listings, messages, flights, repositories, etc.)
4. Specific details, any constraints, filters, or parameters the user mentioned

Rule of thumb: Rewrite the user's request as a single descriptive sentence and use that as the query.