Bots that work everywhere

#5 Product of the DayNovember 02, 2016

With, it’s easier than ever to take advantage of the conversational workplace revolution. We enable developers to take their existing bot or conversational apps and deploy across multiple enterprise messaging platforms. We obsess over the latest platform requirements and docs, so you or your development team doesn’t have to.

Around the web



You need to become a Contributor to join the discussion - Find out how.
Tom HadfieldMaker@tomhadfield · CEO,
Many thanks, Chris, for hunting us. I'm the CEO of We're launching our "bot translation tool" in private beta today. If you've built a bot natively for Slack, for example, you can deploy it to HipChat or Skype without making any coding changes. Our goal is to help bot developers reach more users. We don't think the concept of a ‘Facebook bot’ or a ‘Slack app’ makes any more sense than a website that was 'optimized for Internet Explorer” or ‘optimized for Netscape’. Messaging clients are just like browsers, with small variations in UI. We currently support translation to/from Slack, HipChat and Skype. We'll be adding more enterprise/consumer messaging platforms over the next few months. Ultimately, we think that all bots should work on all messaging platforms. Please let us know if you have any feedback, comments or questions! Thank you.
Brennan White@brennan_white · CEO, Cortex
@tomhadfield Love the philosophy. Totally agree. Thanks for making this!
Christian Montoya@cm0nt0y4 · Maker
@tomhadfield already set up a slack bot with and it's like magic. Excellent work.
Ramesh Padala@rameshdot0 · Maker of & yogatailor
@tomhadfield congrats on the launch! Looking forward to try out the platform
Dharmesh Shah@dharmesh · Founder and CTO, HubSpot
@tomhadfield @cm0nt0y4 Curious: Which platform did you deploy on (once you got the bot configured in
Tom HadfieldMaker@tomhadfield · CEO,
@dharmesh We helped @cm0nt0y4 launch Emojify on Microsoft Teams - see:
Andy Mauro@andymauro · CEO
Nice job Tom. This is one of the smarter cross-platform messaging/bot plays. There are few enough consumer messaging platforms that matter that translation layers are often not worth using. However, in the enterprise messaging space there are so many platforms, and the market for each is small enough that is not so much solving a technical problem of translation, it's actually expanding the addressable market for enterprise bot devs -- pretty cool.
Tom HadfieldMaker@tomhadfield · CEO,
Thanks @andymauro. This means a lot coming from you. We love what you're doing at Automat.
Jake Bailey@jake_bailey · CEO, Harvest
This is really cool, Tom. Can you explain in some more detail how bot translation works?
Tom HadfieldMaker@tomhadfield · CEO,
Hi @jake_bailey. Let’s say you’ve built a Slack app. You built it to send/receive messages via the Slack API. Now, you can now connect your Slack app to, using an API key we provide, and with one click you can now provision your bot on HipChat. When a HipChat user sends a message to your bot, the message comes to (because we're hosting the endpoint) in HipChat’s format. We translate the message from HipChat’s format to Slack’s format, and then relay it in real-time to your Slack app. Your Slack app responds, just as it normally would, to us. We translate the response from Slack’s format into HipChat’s format and then relay it (in real-time) to the HipChat user. is literally a man-in-the-middle that is translating and relaying messages back-and-forth, thus enabling your Slack app to communicate with HipChat users (for example).
Guillermo Gette@guillegette · Founder of Workast
@tomhadfield congratulations on the launch! Quick question, do you have an example of a HIpChat bot? As far as I know, they do have slash command but not actual bot as you can find on Slack that can message users directly. Cheers
Carlos Herrera@carlosherrera · Software Engineer, Epicor Software
@tomhadfield @jake_bailey I love how simple it seems, although I know it involved a lot of work behind the curtains.
Jesse Vickey@jesse_vickey
Interesting. What other platforms are you planning to support?
Tom HadfieldMaker@tomhadfield · CEO,
Hi @jesse_vickey. We currently support translation to/from Slack, HipChat, Skype and - as of a few minutes ago - Microsoft Teams. We'll be adding other enterprise messaging platforms - such as Salesforce Chatter and Cisco Spark - in the months ahead. Ultimately, we plan to support all enterprise platforms that have open API's, including Glip, Flowdock, Campfire, Ryver, Gitter, Socialcast, Mattermost, Rocket.Chat, Convo, Symphony, Blink, etc. Although we're focused on enterprise messaging platforms for now, consumer platforms (like Messenger, Kik, Telegram, LINE, Viber, WeChat, etc) are also on the longer-term roadmap.
Dharmesh Shah@dharmesh · Founder and CTO, HubSpot
@tomhadfield Congrats on the launch. Now that twitter has some "bot-like" platform features, any thoughts to supporting it too? (Note: I'm not advocating for bots on twitter, as it's my least favorite platform for bots).
Tom HadfieldMaker@tomhadfield · CEO,
@dharmesh We're focused on enterprise messaging platforms for now (eg, Slack, Microsoft Teams, Cisco Spark, HipChat, Google Hangouts Chat, etc) but no doubt we'll be adding consumer platforms including Facebook/Twitter/etc soon!
Matty Mariansky@mmariansky · Product Designer at Meekan
I like the idea, but how do you handle some of the fundemental differences between the augmented features of each platofrm (eg Slack buttons which can create a mini-app inside a message vs HipChat's cards vs Skype's much simpler buttons )?
Tom HadfieldMaker@tomhadfield · CEO,
Hi @mmariansky. On enterprise messaging platforms, the vast majority of UI elements and API methods can be mapped across platforms. There are a small number of UI elements, like Interactive Messages on Slack for example, that don't map to anything similar. In those cases, we aim to maintain the basic user experience - even if it's not identical - by mapping to the available UI elements. It's something we'll continue to refine over time.