> For the complete documentation index, see [llms.txt](https://docs.adminremix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adminremix.com/integrations/lansweeper.md).
# Lansweeper
Let's start creating your new Lansweeper application for this integration. Make sure you're logged in to your Lansweeper account and follow these steps:
## Getting Started
1. Log into your Lansweeper account and follow the steps.
2. Click on your account profile.
3. Click **"Developer tools"**
4. Select **"All applications"**
5. Click **"Add new application"**
6. Make sure "**Cloud Application"** is selected and click "**Continue"** to proceed to the next step.
## Create
7. Using the **"Click to copy"** copy your unique callback URL to insert in to Lansweeper. Click **"Add Application"** to complete this part of the process.
8. After the application is created, a crediental text file will be automatically downloaded from Lansweeper. Open the file to proceed to the next step.
## Setup
9. Using the **"Client ID"** and **"Client Secret"** from the file, fill in the data for the two fields. Click **"Save and Proceed"**.
## Authorize
10. Confirm that the application was authorized successfully, then select **"Next"**.
## Mapping
11. AssetRemix and Lansweeper have different names for our fields. Select which Lansweeper Metadata best matches our fields. "Asset Tag is locked in to Asset Name" You can also select the **"Prefer Local"** box if you'd like the data to be ignored in an update.
## Webhook (Optional)
12. Click **"Webhooks"**
13. Select **"Add new webhook"**
14. Use the **"Click to Copy"** to copy your unique webhook payload URL and insert into the **"Payload URL"** field in Lansweeper.
15. Under **"Deselect entities"** click the boxes next to **"Asset basic info"** and **"Asset custom"**
16. Click the :floppy\_disk:at the top of the screen to save.
---
# 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.adminremix.com/integrations/lansweeper.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.
