Services

Open Appmixer Backoffice and click the Services item in the main menu.

Service configuration.

Appmixer comes with a set of components. Some of those can be used directly, but some require user authentication into a 3rd party system (Slack for instance). This authentication is usually done through the OAuth protocol. That protocol requires pair of secrets stored in Appmixer.

There are more ways how to save those secrets in Appmixer. Using Appmixer Backoffice is the easiest one. Let's say you want to start using Slack components. First, you need to register your Slack application on the Slack website, then you will be provided with clientId and clientSecret. Once you have those, you can save them into Appmixer like this:

Create new service configuration.

As a Service ID you use appmixer:slack. This is the same value that is used in Slack component.json files in the auth section.

Auth section.

This tells Appmixer that the NewChannelMessageRT component uses appmixer:slack authentication module. Appmixer will try to locate authentication file auth.js in appmixer/slack directory.

We can now add the clientId and clientSecret.

Adding service configuration key/values.

Then add clientId (has to be clientId, not clientID or any other combination) key with your client Id.

Adding clientId.

And then the clientSecret.

Adding clientSecret.

After that, you can use the Slack components in Appmixer.

You can add any key/value pair here. All the keys and their values will be available in your component's code at context.auth object and in the case of auth.js files directly in the context object.

You can use this configuration even for components that do not require user authentication into 3rd party applications. DeepAI component is a good example. In this case, you need an API key in order to use the Deep AI API. But you don't want your users to provide that API key. You want to use your own API key for all your users. More about that here.