Plugin Development with Actions SDK

The official developer path

If you want a distributable integration that appears in the Logitech ecosystem, build a Logi Actions SDK plugin.

1. What the SDK supports

The public SDK docs say you can build plugins with:

• C#
• Node.js

The current docs position the SDK as the way to:

• create plugin projects,
• package plugins,
• verify packages,
• distribute them through the Marketplace.

2. Host model

The host stack is:

• Logi Options+
• Logi Plugin Service
• supported devices and overlays such as Actions Ring or MX Creative Console

During development, the plugin is linked into the host service rather than copied by hand.

3. Core toolchain

Official docs currently call out:

• latest Logi Options+ or Loupedeck software,
• .NET 8 for the C# path,
• LogiPluginTool for C# packaging and verification,
• @logitech/plugin-toolkit for the Node.js path.

4. Development modes

Path	Best for	Why
Node.js / TypeScript	Fast iteration, web/API integrations, JS teams	Quick scaffold, npm ecosystem, watch workflow
C# / .NET	Heavier desktop integrations, strong typing, mature architecture	Official tooling, strong plugin structure, great for Windows-heavy apps

5. What a plugin can do

The SDK docs and marketplace examples show plugins can provide:

• commands,
• adjustments,
• settings,
• dynamic folders,
• icons,
• profiles,
• stateful actions,
• external service login flows,
• local data storage,
• haptic feedback for supported devices.

6. What a plugin is not

Do not think of it as:

• firmware flashing,
• raw USB/HID driver programming,
• unrestricted remapping of every Logitech device,
• direct universal support for older non-MX devices.

It is an application/plugin platform.