Plug-in Composer (IDE)

Important: Plug-in Composer (IDE) requires Plug-in Composer (Appian Site) to be installed on your Appian site. Without it, sign-in will fail. Your site must be on the Advanced or Premium tier and running Appian 26.9 or later. Learn more: [https://appmarket.appian.com/listings/plug-in-composer-appian-site]

Building Appian plug-ins often requires developers to understand the Plug-in SDK, set up dependencies, create project scaffolding, and determine the appropriate APIs and configuration before writing business logic. Plug-in Composer reduces this development effort by letting developers describe their requirements in plain English directly in IntelliJ IDEA.

Developers can:

Generate: Create complete plug-in projects, including source code, configuration, and build files, from a plain-language requirement. Plan and advise: Determine the appropriate plug-in type, operations, dependencies, and authentication, while asking clarifying questions before generating. Discover: Check AppMarket first and recommend an existing plug-in when one meets the requirement, reducing duplicate development. Modify and fix: Extend existing plug-ins or provide build errors and stack traces to identify root causes and propose fixes. Learn: Ask questions about Appian plug-ins, SDKs, APIs, and existing AppMarket plug-ins without making code changes. Use Appian knowledge: Generate solutions based on a curated knowledge base of Appian Plug-in SDKs, documentation, and AppMarket best practices. Reduce the learning curve: Enable developers to build plug-ins without needing to understand the SDK in depth.

Plug-in Composer does not store or persist credentials. Generated projects use configuration placeholders that developers populate with their own credentials.

For installation and usage instructions, see https://docs.appian.com/suite/help/26.9/install-plug-in-composer.html

Key Features: AppMarket-first discovery — Before generating a plugin, Plugin Composer searches AppMarket and recommends existing plugins when one already meets your needs, helping you reuse instead of rebuild. Generate mode — Describe a plugin in plain English and get a complete project, including the plugin descriptor, Java or HTML/CSS/JavaScript source, and build configuration with the correct Appian SDK dependencies. Question mode — Ask questions about what a plugin does, how an operation works, or which SDK or API to use. Use phrases such as “existing plugin” or “in AppMarket” to search the plugin catalog. Answers are provided inline without making code changes. Modify mode — Open a project containing an appian-plugin.xml and describe the changes you need, such as adding a new operation, input parameter, or unit tests. For substantial changes, Plugin Composer presents a plan for your approval before making changes. Fix mode — Paste a complete stack trace or build output to identify the likely root cause and get a proposed fix. Plugin architect — Determines the appropriate plugin type, components, operations, dependencies, and authentication requirements, and asks clarifying questions before generating code. Plan before code — Review a plan describing what will be built, the files to be created, and key design decisions. Select Generate to apply the result to your local project. All five plugin types — Supports Connected System, Function, Servlet, Smart Service, and UI Component plugins. Curated knowledge base — Grounded in Appian plugin SDKs, official Appian documentation, and AppMarket best practices. Secure communication — Communicates with your Appian site over HTTPS/TLS and sends only the files relevant to your plugin.

For installation and usage instructions, see Plugin Composer documentation[https://docs.appian.com/suite/help/26.9/install-plug-in-composer.html].