> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/technical-documentation/integrations.md).

# Integrations

Connect Crobox with CRM platforms and external product-data sources.

Crobox integrations connect your experiences with the systems that hold customer or product data.

### Available integrations

#### CRM webhook integrations

Send Product Finder email captures and stated preferences to your CRM. Use the data for personalized follow-ups, segmentation, and customer profiles.

<a href="/technical-documentation/integrations/crm-integrations.md" class="button primary">Explore CRM webhook integrations</a>

#### Data enrichment integrations

Import external product data into Crobox as product properties. Use those properties across Crobox experiences.

Bazaarvoice is available as a managed data enrichment integration.

<a href="/technical-documentation/integrations/data-integrations.md" class="button primary">Explore data enrichment integrations</a>

{% hint style="info" %}
Managed integrations require configuration with the Crobox team. Contact your Account Manager to discuss availability and setup.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.crobox.com/technical-documentation/integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.