FluxBilling
Plugins

Creating a Plugin

Create a plugin with the New Plugin wizard, from a template or from scratch.

Updated · 2026-05-28

Every plugin starts in the New Plugin wizard — a five-step flow in the admin Plugins area that scaffolds your plugin and drops you into the builder. You can begin from a ready-made template for a common provider shape, or start blank from any plugin type. This article walks through each step, shows how to import an existing plugin instead, and explains the Draft → build → Enable lifecycle.

Opening the wizard

In the admin panel, go to the Plugins area and choose to create a new plugin. The wizard header shows your progress, for example Step 1 of 5 — Start.

The five steps

Step 1 — Start

Pick how you want to begin:

  • From a template. Choose one of the starter templates, each tailored to a common kind of integration:

    • VPS / Cloud Provider
    • Game Server Provider
    • Web Hosting Panel
    • Domain Registrar
    • License Provider
    • Blank Plugin

    A template ships with starter flows already wired for that kind of service, so you spend less time scaffolding and more time filling in the details.

  • From a type (blank). Instead of a template, you can select a plugin type card and build from scratch: Infrastructure Provider, Payment Gateway, Notification, Automation, Authentication, AI Provider, or Custom. (See Introduction to FluxBilling Plugins for what each type is for.)

You must select either a template or a type before continuing.

Step 2 — Basic Info

Give your plugin its identity:

  • Plugin Name — the human-readable name shown in the admin UI.
  • Slug — a short machine identifier, auto-generated from the name as you type. You can edit it, and a Reset option re-derives it from the name. The slug is what you'll reference your plugin by, so keep it lowercase and simple.
  • Description — a short explanation of what the plugin does.
  • Icon — pick from the available icon options to represent your plugin.

Both a name and a slug are required to continue.

Step 3 — API Connection (optional)

Optionally set up the connection to the external API now:

  • Base URL — the root URL of the service's API.
  • Authentication — choose the auth type and fill in its fields (API key, bearer token, basic auth, OAuth2, and more).
  • Test Connection — a button that performs a quick test call so you can confirm your settings work before you finish.

This step is optional — you can skip it and add or edit the connection later from the builder. For the full list of auth types and their fields, see Connections and Authentication.

Step 4 — Capabilities

Select the capabilities your plugin should support. Each capability you select scaffolds a matching starter flow so the platform can find and run it later — for example, choosing "provision" on an Infrastructure Provider creates a starter provisioning flow. The list of available capabilities depends on the type you chose.

This step is skipped automatically when you start from a template, because templates already ship with their flows.

Step 5 — Review & Create

Review a summary of your choices — name, type, slug, description, the connection, and the flows that will be created. When you confirm, the plugin is created as a Draft. Nothing is enabled yet, so you're free to keep building and testing.

Importing an existing plugin instead

If you already have a plugin package file (a shared plugin or one you exported earlier), you don't have to use the wizard. From the Plugins area you can import the package directly. You can preview what's inside a package — its name, type, and how many connections, flows, forms, and webhooks it contains — before committing. Imported plugins arrive as a Draft, just like wizard-created ones, so you can review and test before enabling. See Packaging, Importing, and Updating for the full workflow.

The plugin lifecycle

Every plugin moves through the same stages:

  1. Draft — the plugin is created (by the wizard or by import) but not active. It does nothing in production yet. This is where you do all your work.
  2. Build & test — open the flow builder to design and refine your flows, fill in your configuration schema, and use the connection test to verify your API calls. See Building Flows and Configuration Settings.
  3. Enable — when you're confident, enable the plugin. Only then does the platform start routing real events and actions to it.

Build and test thoroughly while in Draft — enabling a plugin makes it live.

Related: Introduction to FluxBilling Plugins · Connections and Authentication · Building Flows

All topicsSuggest an edit →