Grok BotReleases

· 0.21.0

Routines can start from a webhook

Each webhook routine gets its own URL and key. Version 0.21.0 also added a language picker.

Grok Bot 0.21.0, out Aug 19, lets a routine start from a webhook, with its own Webhook URL and Webhook key. It also added a language picker under Appearance and an emoji picker in the message box.

Why it matters#

Any service that can call a URL can now start a routine, not only the apps Grok Bot connects to directly. Enterprise admins also got two dashboard controls: Team Setup scripts that run on every member's Bot computer, and a network access policy for the team's Bots.

Everything in 0.21.0#

New#

  • Languages: Pick the app's language under Appearance. The list includes Simplified and Traditional Chinese, Japanese, Korean, Hindi, Spanish, Portuguese, French, German, and Polish.
  • Emoji: Type a colon in the message box to pick an emoji, or finish a short name with a colon to insert it.
  • Routines: A routine can start from a webhook, with its own Webhook URL and Webhook key.
  • Attachments: Download one from the message menu, or use Download all when a message has several.
  • Enterprise: Admins can save Team Setup scripts on the dashboard that run on every member's Bot computer.
  • Enterprise: Admins can set a network access policy for their team's Bots from the dashboard.

Improved#

  • Dictation: It follows your system language, and Enter stops a recording.
  • Computer: Updating or recreating the Bot's computer explains that files and logins stay, while installed apps and packages are removed.
  • Plugins: The page opens with your plugins, category filters, and a Team Plugins section.

Fixed#

  • Files: Search finds files on the Bot's computer, and says Search unavailable when it can't run.
  • Connection: Grok Bot reconnects to your computer after sleep or a dropped connection, so actions on it keep working.
  • Sign-in: When your sign-in expires, Grok Bot asks you to sign in again.

Good to know#

  • In 0.27.0 on Aug 25, webhook routines started receiving the request body, so the Bot can act on what was sent.

Sources

  1. x.ai
  2. x.ai

Something wrong? Tell the bot