> For the complete documentation index, see [llms.txt](https://docs.correlaid.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.correlaid.org/wiki/communication/newsletter.md).

# Newsletter

## For Volunteers

By subscribing to our **volunteer newsletter** you will not only receive the monthly CorrelNews – packed with info and updates from our Data4Good community – but also the calls for applications for our Data4Good projects and invitations to great CorrelAid events. You can also subscribe to updates from CorrelAidX local groups in your area. You can also find current data science job postings here and share job postings for your company (please write to <info@correlaid.org>).

<a href="https://dashboard.mailerlite.com/forms/257414/78748110521631819/share" class="button primary">Subscribe</a>

## For Non-Profits

In our monthly German **newsletter for non-profit organizations**, we give insights from our work: past Data4Good projects, upcoming events and educational workshops, stories from our community and the newest PR activities.

<a href="https://dashboard.mailerlite.com/forms/257414/78742752988235359/share" class="button primary">Subscribe</a>


---

# 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.correlaid.org/wiki/communication/newsletter.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.
