> For the complete documentation index, see [llms.txt](https://docs.violetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violetlabs.com/integrations/terminology.md). # Terminology * **Application**: A software tool your team already uses (like your CAD tool, project management software, or inventory management system) that you want to connect to Violet * **Connection**: The set of setup information that tells Violet how to reach your application, such as the web address, username, and password so Violet can log in and access the data at that location * **Integration**: The specific instructions for what data Violet should grab from that connection and how often, such as "get all purchase orders every hour" or "only fetch released parts once a day" * **Fetch:** Process to move data from an application into Violet * **Sync:** Process to align data between two applications, fetching data into Violet and pushing it to the subsequent application. Think of it like setting up your email on your phone: the *application* is Gmail, the *connection* is entering your Gmail address and password, and the *integration* is choosing how often to check for new messages. --- # 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.violetlabs.com/integrations/terminology.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.