> 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/custom-integrations-and-marketplace.md).

# Custom integrations

Unlock the full potential of Secoda by creating custom integrations tailored to your unique data environment.

Custom integrations help bridge the gaps in your data ecosystem. In Secoda, there are two types of custom integrations: **File Uploads** and **Marketplace**. Both options offer flexible and effective ways to bring your entire data stack into Secoda.

### File Upload

Ideal for less technical users and resources that don’t require frequent extractions, this option allows users to create and upload a CSV or JSONL file directly into Secoda.

{% content-ref url="/pages/52bVCgTksTyFcP5UNGYV" %}
[File upload](/integrations/custom-integrations-and-marketplace/custom-integration.md)
{% endcontent-ref %}

### Marketplace (Secoda SDK)

Marketplace integrations are built using the Secoda Software Development Kit (SDK). Users can upload their code to Secoda, allowing the integration to run automatically on a set schedule. Those who build a Marketplace integration with the Secoda SDK are encouraged to publish it for other Secoda users to benefit from.

{% content-ref url="/pages/eVVF5ZmlJN679xq5VB7g" %}
[Marketplace](/integrations/custom-integrations-and-marketplace/secoda-sdk-custom-integration.md)
{% endcontent-ref %}

{% hint style="info" %}
Not sure which option is the best for your team? Feel free to get in touch with the [Secoda support team](mailto:support@secoda.co)!
{% endhint %}


---

# 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/custom-integrations-and-marketplace.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.