> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-connect/working-with-connect/connect-to-systems/connectors/nicelabel/getting-started-with-the-nicelabel-connector.md).
# Getting Started with the NiceLabel Connector
This instruction assumes the following programs/components are already set up and available:
* **NiceLabel Automation**
* **NiceLabel DesignerPro** (configured label printers are recommended)
* **Flow Connect** with a configured **NiceLabel connector**
1. Start **NiceLabel DesignerPro** and click **Create a New Label**.
2. Select the printer and click **Next**.
3. Set the **Page Size** and click **Next**.
4. Choose the **Label Layout**.
5. Specify the **Label Dimensions** and then click **Finish**.
6. In the **right-side panel**, click **Variables** and create the required variables.
7. Click on each created variable to configure **General Settings**, **Input Rules**, or **Output Rules**.
8. Design the **label/barcode layout** using the created variables.
9. Then save the created label file. Note that the file extension will be `.nlbl`.
10. Set up the workflow, add a **Script Step**, and set the **connector to NiceLabel Connector**.
11. Define the **local variables** in the flow that will be passed to the NiceLabel server.
12. **Commit the workflow and execute.** Check the status on the NiceLabel Automation server.
---
# 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.novacura.com/flow-connect/working-with-connect/connect-to-systems/connectors/nicelabel/getting-started-with-the-nicelabel-connector.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.
