> For the complete documentation index, see [llms.txt](https://docs.netsimpler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.netsimpler.io/en/integration-interne/email/mailerlite.md).

# MailerLite

**Connecting your Mailerlite account and adding users to your email lists.**

Go to Settings > **Applications** > **Add application** and select **Mailerlite**.

**Note:** You can add multiple applications if required.

### **Add your API key**

If you don't know your Mailerlite API Key follow this link: [**Mailerlite API document**](https://help.mailerlite.com/article/show/35040-where-can-i-find-the-api-key)

Once you have your email service connected, a new button will appear on your forms and checkout widgets. This button will show your email service providers name. 'Highlighted in this case with Mailerlite'

### **Adding your customers to email lists**

From here, you can add your visitors to your selected email lists, you can add to more than one if required.


---

# 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.netsimpler.io/en/integration-interne/email/mailerlite.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.