> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/external-apps-integration/dynamics-nav.md). # Dynamics NAV Dynamics NAV integration in Lleverage connects your workflows and agents to on-premise Microsoft Dynamics NAV (Navision), so long-standing ERP systems can take part in modern automated processes. ### How to Connect Dynamics NAV is an ERP connection, and ERP connections are set up together with the Lleverage team because they need configuration specific to your environment. 1. **Contact the Lleverage team** via support or your account manager to start the managed setup 2. **Provide the sign-in details** for your NAV environment: the connection authenticates with a username and password 3. **Confirm the connection** appears in Settings > Connections, ready for use in workflows and by agents > 💡 Once connected, you can control which actions the connection allows and which need approval before running, just like any other connection. ### What Dynamics NAV Can Do * **Customers** - create customers, look up individual customers and list them * **Vendors** - look up and list vendors * **Items** - look up and list items * **Sales orders** - create sales orders and look up or list existing ones * **Sales invoices** - look up and list sales invoices * **Companies** - list the companies in your environment > 💡 **Use case**: Feed orders captured by a workflow straight into NAV, or let an agent answer questions about customers and invoices held in your ERP. ### Important Considerations * The account used to connect determines what the integration can see and change in NAV * Most actions ask you to pick the company first --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.lleverage.ai/external-apps-integration/dynamics-nav.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.