Skip to content
Developers and bots

Build what yourhub needs next.

Make an application and you get a bot account. Your code talks to Hubs over a plain HTTP API, and hears about new messages over a WebSocket gateway. Roles and tickets are already built in, so your bot can do the part only your hub needs.

You'll need to sign in to use the portal, but not to read the developer docs.

Example bot, shown for illustration.
The platform

What you get as a developer.

Everything a bot needs to work in Hubs, from its own account to live events.

  • Bot accountsEach application gets its own bot account with a name and a picture. It always shows a Bot badge, and a bot can't hide it.
  • Slash commandsAdd commands for every hub or just one. People pick them from the message box.
  • Buttons, menus and formsPost a card with buttons or a menu, ask for details in a form, or reply only to the person who asked.
  • Live eventsConnect to the WebSocket gateway and your bot hears about messages as they arrive. It supports heartbeats, resume and shards.
  • Hub API keys and webhooksHub owners can make a key for chosen channels and send signed events to their own servers.
  • TeamsWork on an application with other people. Give each person the access they need, down to read only.
Permissions

Hub admins stay in charge.

A bot can do only what a hub's admins approved, and they can see what it did.

  • Plain-words installBefore an admin adds a bot, the install screen lists what it can do and what it can't.
  • Scopes and permissionsA bot gets only what the hub approved. It follows the same channel rules as a person with its role.
  • Token safetyWe show a token once and store only a hash of it. If someone posts a token in chat by mistake, we revoke it right away.

Hub owners can see each bot, the permissions it was approved for and a log of what it did. You can remove a bot at any time.

See you in Hubs.

Start in your browser, or get the app for Mac or Windows. You sign in with the same account either way.