> For the complete documentation index, see [llms.txt](https://guia.fenicio.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guia.fenicio.help/integraciones-y-herramientas/marketing-automation-and-crm/mailchimp.md).

# Mailchimp

## **¿Qué se necesita para integrar una cuenta de Mailchimp con la tienda?**

\- API KEY

\- ID LIST

Estos datos deben ser proporcionados por el cliente a Fenicio para realizar la integración.

### ¿Cómo encontrar la API KEY?

1. Ingresar a tu **cuenta de Mailchimp**.
2. Clic en el **nombre de la cuenta** (ubicado abajo a la izquierda de la pantalla).
3. Clic en **Profile**. Clic en **Create a Key**.
4. Se generará un **código automático** que se verá en el campo **API Key**. Éste debe ser copiado y enviado a Fenicio.

### ¿Cómo encontrar el ID List?

1. Clic en **Audience y All contacts**.
2. Clic en **Settings y Audience name** and defaults.
3. El **List ID** se encuentra en color rojo debajo del título **Audience ID**. Éste debe ser copiado y enviado a Fenicio.


---

# 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://guia.fenicio.help/integraciones-y-herramientas/marketing-automation-and-crm/mailchimp.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.
