> For the complete documentation index, see [llms.txt](https://docs.guideflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guideflow.com/help/capture-a-guideflow/how-to-capture-a-guideflow.md).

# How to capture a guideflow

{% hint style="info" %}
Make sure that you have the [Chrome extension](https://chrome.google.com/webstore/detail/guideflow/neabdmkliomokekhgnogbeonopbjmajc) downloaded and installed on your browser before you get started.
{% endhint %}

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/qkqmm8xh1p>" %}

* Open Guideflow's Chrome extension.
* Select the capture type.
* Click Start capture.

### Available options

There are three methods used to capture content for interactive demos:

* [**Screen capture**](/help/capture-a-guideflow/how-to-capture-a-guideflow/screen-capture.md) - enables you to create guideflows using screenshots and videos
* [**HTML capture**](/help/capture-a-guideflow/how-to-capture-a-guideflow/html-capture.md) - enables you to create guideflows using HTML code

{% hint style="info" %}
You can combine Screen and HTML capture in a single guideflow.
{% endhint %}

* [**Sandbox capture**](/help/sandbox/how-to-capture-a-sandbox.md) - enables you to create a self-contained demo environment by stitching multiple HTML captures together

{% hint style="info" %}
Which capture method to use:

* Screen capture - when you prioritize fast demo creation
* HTML capture - when you prioritize advanced demo customization
* Sandbox capture - when you prioritize self-guided, authentic simulation
  {% endhint %}


---

# 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.guideflow.com/help/capture-a-guideflow/how-to-capture-a-guideflow.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.