> For the complete documentation index, see [llms.txt](https://documentation.pushly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pushly.com/platform/platform-integrations/blueconic.md).
# BlueConic
Instructions for setting up your BlueConic Platform Integration
## Setting up the BlueConic Integration
To setup a BlueConic Integration, users will have to reach out to their Account Manager to enable the integration. Once its enabled, users will be able to configure the integration.
To successfully integrate with BlueConic with the Pushly platform, users will have to provide the following details:
| Title | Description | Required |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
| Tenant Name | This should match the blueconic.net url that has been assigned by BlueConic | Yes |
| Application Name | The user can select an application name of their choice | Yes |
| Application Client ID | This will be provided by BlueConic | Yes |
| Application Client Secret | This will be provided by BlueConic | Yes |
| Associated Content Stores | The users can create multiple stores within their BlueConic accounts and link one or multiple of them to Pushly by providing the **Store Name** and **Store ID.** Users can link up to 10 different Stores to their Pushly account | Yes |
Once all the details have been entered, users can click "Save" to complete this one time integration configuration
---
# 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://documentation.pushly.com/platform/platform-integrations/blueconic.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.
