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

# Maileon

### How to connect Maileon to Churned <sup><sub>Log in to the Churned platform and go to the “Integrations” section. Click on “New Integration” and select Maileon from the list.<sub></sup>

### Required Credential

* apiKey – The API key used to authenticate with Maileon’s API.

Here’s how you can obtain this credential:

Generate an API Key

1. Log in to your Maileon account.
2. Navigate to Settings > API Keys or Settings > Integrations.
3. If needed, create a new API key and define the required access rights (e.g., contacts, transactions, mailings).
4. Copy the API key and store it securely.

Input the Credential\
Enter the retrieved credential into the Churned integration form:

* apiKey: Your Maileon API key.

Click Save and test the connection to ensure everything is working correctly.

Once connected, notify the Churned team to synchronize data.

### Helpful Links

* Maileon API Documentation
* Managing API Keys in Maileon<br>


---

# 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:

```
GET https://docs.churned.io/churned-docs/integrations/maileon.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.