It would be convenient if we could create our own labels for integrations the same way we can custom label an API.
Use case: Yesterday, I couldn't get a deployment event to post to a GH commit hash. Cornel passed the issue to Joe who told me it was necessary to create a second GH integration. Since the GH integration is directed at respective repo when you install it and does not contain a self-documenting description in the configuration column, it would be helpful to be able to add one. This way the other automation testers aren't scratching their heads wondering why I added a GH integration when we already had one.
At another company, regarding Slack integration, the QA's look at everything, but devs on different teams only want mabl run reports for their relevant area. They set up multiple Slack channels and configured multiple Slack integration instances. I'm sure they would make use of a custom label system if it were available.