App developer platform is in beta. If you have any feedback about this feature, please submit it here.
With apps that require plugin access, you can add content directly into the Kit app UI. Kit needs to authenticate against the third-party to be able to pull the data required to be rendered within Kit .
For example, if a creator is writing an email to promote a Mighty Network community they run, they can select the events from within the email editor while they are in the context of email writing, and send it out to their email list without ever leaving Kit .
For plugins, authentication goes the opposite way to the API, where Kit needs to authenticate against the third-party to be able to pull the data required to be rendered within Kit.
If you have no plugins set up, you will see this page here under Plugins, in your app settings. To create a new one click on New plugin
Configuring Plugin authentication
If you already have plugin authentication set up, you'll move directly to the plugin creation flow.
If you don't have plugin authentication set up, you can:
Continue without authentication. This sets your strategy to "No authorization", or
Configure Authentication taking you to the Authentication tab to set this up
If you disable plugin authentication on the Authentication tab, you'll see a warning when you return to the Plugins tab. This warning indicates that you need to update authentication settings before your plugins can be active. Click the prompt to go directly to the Authentication tab and make the necessary changes.
In the Authentication tab, you can find two authorization methods:
OAuth: If you require linking of third-party accounts or are sharing sensitive information, we currently only support OAuth authentication. This option will likely be the default for most applications, needing to pull data from a third-party account for the creator in a vast number of use cases.
No authorization: If you are working with public APIs, don’t need to pull any confidential information and are happy to have the content endpoints open, you can select “No authorization”.
OAuth Authorization Strategy
If OAuth is selected, all fields will need to be filled out, sharing all of the authentication details needed for Kit to maintain authorization credentials to access the plugin content.
Create a new plugin
Once you selected your authentication method, you'll see a modal asking for a name and plugin type.
After completing this step, you'll land on a dedicated setup page where you can configure your plugin settings.
Details on the JSON required to set plugins up can be found on our plugin documentation.
If you've already set up authorization and plugins, you'll see your complete plugin list with options to:
Activate or deactivate plugins using toggles
Edit plugin settings
Publish a new plugin
Once this setup is complete, you are able to complete all of the work to generate the plugin content and can push their app forward for publishing and installation by users. In order for specific plugins to be made available, they also need to be toggled on.
