Bubble Docs
Search…
Bubble Docs
Introduction
New? Start Here
Help Guides
Structuring an Application
Building a User Interface
Building Workflows
Working With Data
Using Plugins
Using The Bubble API
Testing an Application
Maintaining an Application
Optimizing an Application
Customizing an Application
More about Bubble apps
Core Reference
Bubble's Interface
Elements
Workflows
Events
Actions
Data
Styles
Bubble-made Plugins
Application Settings
API
Account & Marketplace
Account & Billing
Dedicated Plans
Building Plugins
The Plugin Editor
General Settings
Adding API Connections
Building Elements
Building Actions
Loading Data
Publishing & Versioning
Github Integration
Building Templates
Miscellaneous
The Showcase
More features for your to-do app
The Glossary
Powered By GitBook
General Settings
In the first tab of the plugin editor, you'll be able to set general settings for your plugin. You can modify the plugins name, URL, icons, and select the few categories relevant to the plugin. This is important to make your plugin searchable by Bubblers.

Shared technical settings

The second tab lets you define a few technical settings for your plugin.
This plugin uses jQuery 3. If you are building an element that relies on jQuery 3, check this box. The API will give you access to the jQuery plugin.
HTML Header. If you need to insert some HTML in all the pages of an app that use this plugin, you can enter the HTML here. Analytics services, for instance, usually require to add a HTML snippet on all pages. If you need users to be able to enter a key in an HTML snippet (for instance a Google Analytics tracking code), you can add the dynamic key in your snippet between the sequence of characters _*_, such a _*_API KEY_*_. Once a user uses your plugin in their app, this key will be a setting to be filled in the Plugins tab, and the key will be replaced by the actual value in Run-mode.
Note: The only valid header tags are <script>, <meta>, and <link>. Any invalid header code will end up in the body due to automatic repair logic in most modern browsers.
Whenever the HTML for your page is parsed by a browser like Google Chrome, it will detect any invalid HTML tag used in the headers, assume that this was a mistake, that the closing </head> tag was missing, and just add it to the body automatically with an opening tag.
Additional keys. If you need your plugin's users to enter some keys in the Plugins tab, you can enter these key definitions in this tab. These keys will be made accessible in the context object that is sent to all the functions used in your elements and actions (see the following sections for more details). Note that if you are adding API connections to your app, the API call tab will let you pick the different keys that are need for your API to function.
Shared assets and resources. If your plugin implementation requires some assets (images, CSS file, JS files), you can upload them to Bubble's storage and use their URL in your code. All assets are accessible through Bubble's CDN, ensure high speed when accessing the files.
Previous
The Plugin Editor
Next
Adding API Connections
Last modified 5mo ago
Copy link
Contents
Shared technical settings