> For the complete documentation index, see [llms.txt](https://help.metaforms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.metaforms.ai/survey-programming-qualtrics/metaforms-chrome-extension-qualtrics-guide.md). # Metaforms Chrome Extension – Qualtrics Guide The Metaforms Chrome extension programs Qualtrics surveys from your questionnaire. Upload the document, and Metaforms generates the questions, blocks, and answer choices. ### What You Can Do With This Extension * Generate survey questions from an uploaded questionnaire. * Build the required blocks and questions, including their answer choices. * Review and edit questions after they are generated. * Add generated questions to a survey created from a QSF file. On your first login, add the Qualtrics URLs you program in. The extension works only on the URLs that have been added. After a batch is generated, review the questions in the Builder and in Survey flow before you continue. See [Question types supported](/survey-programming-qualtrics/metaforms-chrome-extension-qualtrics-guide/question-types-supported.md) for the question types Metaforms can create. --- # 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.metaforms.ai/survey-programming-qualtrics/metaforms-chrome-extension-qualtrics-guide.md?ask=&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.