> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/hyperbrowser/connect-hyperbrowser.md).

# Connect HyperBrowser

#### **How to use HyperBrowser**

First, create a connection to HyperBrowser if you are using it for the first time. You must have a HyperBrowser account.

In HyperBrowser, select **Settings** and then select **API Keys.** Create a new key and copy/paste the key into the new connection window in your StackAI workflow. Your connection will now be saved and can be reused across different workflows.

![Connect HyperBrowser setup](https://1957915746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FtsPffOgb0uGcjugKhcMm%2Fhyperbrowser.png?alt=media)

There are two ways to include HyperBrowser in your workflow:

1. As a tool: Allow your LLM to decide when a query necessitates searching the web. Click on your LLM, and choose "Add Tool". Select HyperBrowser. Make sure to reference this tool in your prompt for [best results](https://app.gitbook.com/o/2asIZ16y1YqfkPhoidZ7/s/FSlso1Kjob5CLDrh0dVn/getting-started/core-ai-concepts/prompt-engineering).
2. As a node: Enforce Hyperbrowser usage every run. To set up HyperBrowser as a Node, make sure to reference all the Hyperbrowser actions in your LLM prompt.

You can monitor the job status and retrieve results or errors upon completion.

***

## Connection fields and action reference

See [HyperBrowser](https://docs.stackai.com/integrations/catalog/hyperbrowser.md) for the current connector fields and supported actions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/hyperbrowser/connect-hyperbrowser.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
