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

# Figma integration

If you use Figma to design and build your prototypes, you can test your designs with participants in Dscout usability tests, intercept studies, and AI moderated studies. Connecting your Figma account gives Dscout read-only access to the Figma files you have access to. You can opt out anytime by removing the Figma integration in Figma or Dscout.

### Using the Figma integration

Using the Figma integration with a Dscout study allows you to:

* Collect prototype heat maps and click events for Task questions. Dscout cannot access the Figma data to generate heat maps and click events without the Figma integration.
* Select a start screen (frame) to easily control the starting point of a task.
* Select a success screen (frame) to easily program success.

### Not using the Figma integration

You can use a Figma prototype without the Figma integration if:

* You don't want to see heatmaps for your prototype.
* You use Figma prototype links outside of a usability test, intercept study, or AI moderated study (i.e., in a diary study).

Learn more about using Figma with Dscout in the following articles:

* [Set up the Figma integration](/integrations/figma-integration/set-up-the-figma-integration.md)
* [Prepare a Figma file for a Dscout study](/study-basics/testing-prototypes/prepare-a-figma-file-for-a-dscout-study.md)
* [Add a Figma prototype to a study](/study-basics/testing-prototypes/add-a-figma-prototype-to-a-study.md)
* [Analyze heat maps and click data](/study-basics/testing-prototypes/analyze-heat-maps-and-click-data.md)
* [Troubleshooting your Figma prototype](/integrations/figma-integration/troubleshooting-a-figma-prototype.md)


---

# 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://help.dscout.com/integrations/figma-integration.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.