> For the complete documentation index, see [llms.txt](https://docs.getmesa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getmesa.com/connect/algolia.md). # Algolia ## Connection When you're setting up your first workflow with Algolia, you will need to create a [Connection](https://docs.getmesa.com/going-further/credentials) in order to connect MESA with Algolia.
Screenshot of the MESA Algolia step connection setup, creating a Connection to link MESA with Algolia. Spotlight the connection credential fields.
To create your connection, login to your Algolia account and navigate to Settings.
Screenshot of the Algolia dashboard after logging in. Spotlight the Settings navigation item.
Then, select API Keys in the Team and Access section and copy your Application ID. Paste the Application ID in the Application ID field of your MESA Algolia step.
Screenshot of the Algolia Settings, API Keys page under Team and Access. Spotlight the Application ID value to copy.
Next, copy the Write API Key and paste it in the Write API Key step of your MESA Algolia step.
Screenshot of the Algolia Settings API Keys page. Spotlight the Write API Key value to copy.
Once those fields are populated, click the Add connection button in your Algolia step to complete your connection.
Screenshot of the MESA Algolia step with the Application ID and Write API Key fields populated. Spotlight the Add connection button.
--- # 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.getmesa.com/connect/algolia.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.