> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/getting-started/3.-datenquellen-verbinden/niagara.md).

# Niagara

The Niagara integration in Eliona enables seamless connection of your Tridium Niagara framework for building automation. Thanks to this bidirectional communication, you can synchronize control logic, sensor data, and alarms and visualize, analyze, and automate them in Eliona.

The main advantage lies in automatic synchronization: once you have set up the connection, assets, asset types, and their structure are automatically created and updated in Eliona, completely without manual configuration.

## **Installation and connection**

Setting up the Niagara integration is straightforward and takes just a few steps:

1. Install Niagara module: The module is simply downloaded from the Eliona App Store and copied to your Niagara system. A separate license for the module is also required.
2. Generate API key in Eliona: To establish the connection, an API key must be created in Eliona. This key is used for authentication.

After installation, synchronization runs automatically. This means your data, controls, and alarms from Niagara are directly available in Eliona and can be used for dashboards, analyses, and automations.

For a detailed, step-by-step guide to installing the module and configuring it in Eliona, please visit the full documentation in the "Niagara" chapter.

{% content-ref url="/pages/89893b7f29ff991809cb7f2fee9be50f5dffcb2b" %}
[Niagara](/collection/english-v14/apps/apps/niagara.md)
{% endcontent-ref %}


---

# 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.buildings.ability.abb/collection/english-v14/getting-started/3.-datenquellen-verbinden/niagara.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.