Lansweeper Custom Field Creation

Creates custom fields in Lansweeper, or writes a calculated value onto specific assets’ custom fields — with a full preview and your explicit go-ahead before anything is sent.

The Lansweeper Custom Field Creation & Population skill sends a single, validated request to your Lansweeper Flow Builder webhook to either create new custom fields or write a value into an existing one on one or more assets. It resolves every asset key through the Lansweeper MCP rather than asking you to supply one, validates type-specific requirements (a currency code, a valid URL, or a min/max range) before building the payload, and always shows a full summary table and waits for explicit confirmation before making any real change in your environment. It’s a natural next step after any other skill computes a per-asset value — a risk score, an EOL countdown, a compliance status — that’s worth writing back into Lansweeper.

image 158

Why Custom Field Creation & Population Matters Here

  • Automation/Ops perspective

    “I just calculated something per-asset — how do I get it back into Lansweeper without re-entering it by hand?”
    Handoff: any other skill’s per-asset output becomes a proposed custom field write, not a dead-end chat table.
    Batch: many fields or many assets in a single call, instead of clicking through the UI one at a time.

  • Governance perspective

    “This writes real data into production — how do I know exactly what’s about to happen?”
    Preview and consent: a full before-you-send summary table every time, with no memorized or reused webhook URL.
    Traceability: an execution ID plus an explicit instruction to verify the result actually landed, rather than trusting a 200 response blindly.

Requirements

Lansweeper MCP

https://mcp.lansweeper.com/mcp

Lansweeper plan

Pro, Enterprise

Need Lansweeper’s Flow Builder

LLM

Claude 3.5+, Gemini, ChatGPT, Copilot

Step by step setup guide

Step 1 — Download
Download the skill package for your platform. Select Claude, ChatGPT, Gemini, or Copilot.

Step 2 — Install

  • Claude: install as a plugin/skill in Claude Desktop or Code.
  • ChatGPT: install as an app.
  • Gemini (Antigravity): load it into your skill folder.
  • Copilot: import it as a solution in Power Platform / Copilot Studio — this creates the “Custom Fields Creation” agent.

Step 3 — Confirm the platform can fire the webhook
Each platform dispatches the webhook POST a different way — this isn’t a nice-to-have, it’s what makes the write actually go through.

  • Claude: requires the Claude in Chrome browser extension connected — that’s how this package fires the webhook, since the sandbox has no direct outbound network access.
  • ChatGPT: works best in Codex Work Mode with a curl-capable command tool available — this package’s verified dispatch method, which explicitly avoids browser fetch as unreliable for this webhook.
  • Gemini (Antigravity): needs a Lansweeper MCP-equivalent connector for asset-key resolution, plus either direct outbound HTTP or a browser-automation path to fire the webhook. The package itself flags this as environment-dependent and unverified — check what your setup actually supports before relying on it.
  • Copilot: needs a native HTTP-capable action wired in (e.g. a Power Automate “HTTP” step). If none is available, it doesn’t just fail — it hands you a ready-to-run PowerShell script, curl command, or Postman-importable request with the exact confirmed payload, a real tested fallback rather than a gap.

Step 4 — Ask, review, confirm
All four follow the same flow: ask naturally (e.g. “create a custom field called Contract Value, currency USD”), you’ll be asked for your Flow Builder webhook URL fresh every time, shown a preview table of exactly what will be sent, and nothing is sent until you explicitly confirm.

  • Claude: fires the webhook via the browser extension once confirmed.
  • ChatGPT: fires the webhook via curl once confirmed.
  • Gemini (Antigravity): fires the webhook via whichever HTTP path your environment supports once confirmed.
  • Copilot: fires the webhook via its native HTTP action once confirmed, or gives you the manual fallback if none is wired in.
Related Skills
See all skills