> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/connectors/source-catalog/marketing-growth/lemlist.md).

# lemlist

## **Why syncing my lemlist to** [**Whaly**](https://whaly.io)**?**

Syncing your Airtable can be useful for various cases

* Understand how well your campaigns are performing
* Combining your **lemlist** data with your CRM data (such as [Hubspot](/connectors/source-catalog/sales-crms/hubspot.md)) to get a full view of your acquisition funnel
* Analyse your **lemlist** as cohorts to understand when people are responding to your emails, etc.
* ....

## Which l**emlist** data is synced by [Whaly](https://whaly.io)?

[Whaly](https://whaly.io) 🐳 is currently syncing the following data:

* **Team**: Invite your colleagues to your team so you can share your successes and templates!
* **Campaign**: A Campaign is a sequence of messages that should be sent to Leads.
* **Campaign Activity**: Campaign Activities are events (email sent, email opened) generated by your campaigns.

[You can find the relationship between all those objects here.](https://docs.google.com/presentation/d/1QFDHMrfs5ys0UDdIoEKqgVoefI_LkWjRet5YTymDYPU/edit?usp=sharing)

{% embed url="<https://docs.google.com/presentation/d/1QFDHMrfs5ys0UDdIoEKqgVoefI_LkWjRet5YTymDYPU/edit?usp=sharing>" %}


---

# 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.whaly.io/connectors/source-catalog/marketing-growth/lemlist.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.