> For the complete documentation index, see [llms.txt](https://docs.linuxfoundation.org/lfx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxfoundation.org/lfx/community-management/integrations/cvent-integration.md).
# Cvent Integration
The Cvent integration already enabled and requiring no additional configuration, facilitates the automatic appearance of events from Cvent under the projects in **CM.**
This is achieved through a series of steps involving data transfer from **Cvent** to LFX and, subsequently, from LFX to CM via an API.
**Steps**
1. **Data Transfer from Cvent to LFX**: Cvent sends event data to LFX.
2. **Integration between LFX and CM**: An integration has been established between LFX and CM.
3. **Data Push to CM**: The integration pushes these events from LFX to CM through an API.
4. **Data Appearance in CM**: The event data, which includes details such as attendees’ or speakers’ names, the name of the event, and the date of the registration, automatically appears under the projects in CM.
---
# 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.linuxfoundation.org/lfx/community-management/integrations/cvent-integration.md?ask=&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.
