I built a slack app today and it was a lot harder than it should have been. Event payloads are really inconsistent (one even is a JSON object encoded in a form

I built a slack app today and it was a lot harder than it should have been. Event payloads are really inconsistent (one even is a JSON object encoded in a form data field), data about users is inconveniently hidden, and building a functional home tab with navigation is just annoying. This looks like it might solve some of that. The deployment side of things looks awesome, and the typescript types will really help with the inconsistent event structures. However I’m not sure if they are not cutting out a huge part of their target audience with their approach to hosting. How would I connect to an internal service or database with this? I can’t, which makes it super inconvenient for “quick company specific workflows”, which seems to be exactly what they are targeting. That being said, I love the idea of Slack becoming a GUI for an event bus connecting various things together. URL should also be changed to https://api.slack.com/future https://api.slack.com/future