> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/data-transformation-tools/coalesce.md).
# Coalesce
An overview of the Coalesce Integration with Secoda
{% content-ref url="/pages/12OQRxjDDvDN37RibAaJ" %}
[Coalesce Metadata Extracted](/integrations/data-transformation-tools/coalesce/coalesce-metadata-extracted.md)
{% endcontent-ref %}
## **Getting Started with Coalesce**
There are three steps to get started using Coalesce with Secoda:
1. Retrieve your Coalesce Host
2. Retrieve your API key
3. Retrieve your Environment ID
4. Connect Coalesce to Secoda
#### **Retrieve your Coalesce Host**
You can determine your Coalesce host by logging into Coalesce and taking the base url from the link. In the example below, the host would be `https://app.coalescesoftware.io`
#### **Retrieve your API key**
For Secoda to retrieve metadata from Coalesce, you need to get your Access Token. To do this, go to **Deploy > Generate Access Token** and copy the token.
**Retrieve your Environment ID**
On the **Deploy** page, get the ID of the environment that you want to import into Secoda. For the example below, it would be 3.
**Connect Coalesce to Secoda**
The next step is to connect Secoda:
1. In the Secoda App, select **Add Integration** on the Integrations tab
2. Search for and select the **Coalesce** integration
3. Enter your Coalesce Host, Access Token, and Environment ID. This information is kept encrypted
4. Click on **Test Connection** to save the integration.
5. Once integration is created, click on **Run Sync** to run your first extraction
---
# 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.secoda.co/integrations/data-transformation-tools/coalesce.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.
