What should I do to extend my workspace’s functionality? Submit a pull request, use integrations, or build a Rocket.Chat app?
Each of these options has its strengths if you want to extend the functionality of your workspace. You can use any one or a combination of options to meet your needs.
Rocket.Chat Marketplace: Rocket.Chat provides a suite of apps developed in-house and by third-party developers. The apps allow you to interact with the UI and execute custom routines.
Build your own app: The Apps-Engine framework allows developers to create and use custom Rocket.Chat apps.
Integrations: You can also use integrations with simple scripts that will be executed when a message is sent or received in a channel. They’re quick to learn and write, but their scope is limited.
Contribute to Rocket.Chat: This option is ideal for developers interested in contributing to the Rocket.Chat project. Changing the source code is the most powerful way of extending Rocket.Chat, but not the simplest. You need to learn the code base, understand the code pattern and rules, submit a PR, and follow up on any changes requested to get it merged.
Do I need to host my app somewhere to make it available to Rocket.Chat?
Not at all! Rocket.Chat apps are packaged and deployed to a workspace, and the system will take care of hooking the app up. Apps can be installed manually or via the marketplace.
Can I build and use an app even if it’s not published in the marketplace?
Absolutely! It’s recommended you use our Apps-Engine CLI tool to develop your apps, making it super easy to deploy your apps to your own Rocket.Chat workspace.
Does Rocket.Chat have a plugin framework?
No, we don't have a plugin framework.
What language should I use to write apps?
Rocket.Chat uses TypeScript only.
Is there a limit to the number of apps I can install?
For premium workspaces, there is no limit on the number of apps that you can install and use.
Community workspaces can enable up to 5 marketplace apps. Private apps can only be enabled in premium plans. You can refer to the Usage limits for details.