As you already know, Appmixer comes with a set of components. Some of those can be used directly, some require user authentication into a third-party system (Slack for instance). This authentication is usually done through the OAuth protocol which requires a pair of secrets stored in Appmixer. There are, nonetheless, more ways you can 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 where you will be provided with clientId and clientSecret. Once you have those, you can save them into Appmixer.
Creating new service configuration
We can now add the clientId and clientSecret.
Adding service configuration key/values
Then add clientId key with your client Id.
Adding clientId key
And then the 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.authobject and in the case of auth.js files directly in the
You can use this configuration even for components that do not require user authentication into third-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. Instead of that, you may want to use your own API key for all your users to make their lives a little bit easier.
Refer to our technical documentation to learn more about "Services": https://docs.appmixer.com/appmixer/appmixer-backoffice/services
You rock! 🔥 You learned all the basics about Backoffice. Now, it's time to get some guidance on how Appmixer gets embedded into your platform, and preview what your end-users interact with.