11–20 of 81 posts
But Twists API to create either thread/comment in an integration will be more complicated to do than Slack and their attachments are not very powerful (yet?), migrating our existing Slack related code might proof difficult.
We have been using Slack as a UI for our backend services, for example, and it is a great way to present reports and alerts, and offer basic controls to the relevant person. For me, whether or not I actually adopt Twist will depend on how easily I can interact with it from my own software.
I would suggest making the integrations page easier to find - I had to troll through the Zendesk archive to find it, even though it is a core feature. Also, a link to the API docs on the help page would be nice. (Edit: Didn't realize until now that integrations are at the channel level, not the top level.)
Is there an API? One of the main values as a Dev is all the integrations we use and build.
it looks a bit more complicated than the Slack one, because of the thread/comment difference, but the "Automatic URL Report" and "Loop in" email based input looks very powerful as well.
Eh, looks like a proprietary email system to me.
Hmm. It seems that these chat applications are more and more becoming like a polished webmail system. Now they've introduced threads, it's searchable forever, you can mail erm. I mean send messages to individuals or even groups. This new technology is amazing. Seriously there is nothing wrong with using e-mail (apart from the dated protocol) and for knowledge sharing your team is better of with some kind of wiki with…
Email is great and we are fans of it, but not for internal team communication.
Eh, looks like a proprietary email system to me.
And we also have a very powerful API: https://api.twistapp.com/
And we are working on a lot more integrations.