Grok BotWorkflows

· Beginner

Illustration: a countertop call bell with a round dome and a plunger button on top, in black and white.
Illustration

Reported, not yet confirmed.

A custom Slack emoji that hands any thread to Grok Bot

Roger reacts with a homemade :grok: emoji and their Grok Bot files the thread as an agenda item, a ticket or a draft reply.

You can turn one Slack emoji into a "send this to my Bot" button. Roger, whose X bio says "15 years getting developer tools in front of the people who ship," made a custom :grok: emoji. "Now when I react to any thread with it, my Grok Bot reads it within 30 minutes and handles it: adds it to an agenda, logs a ticket or drafts my reply." The result is self-reported. We have not run it.

What it replaces#

The usual way to hand a Slack thread to an assistant is to copy it out, paste it into a chat and explain what you want. Roger's version skips all of that: "No integration to build. Just an emoji and a routine." The reaction is the whole request, and the Bot decides which of three outcomes fits.

How it works#

Roger did not publish the routine, so this is the setup Cursor's help page describes:

  1. Make the emoji. Add a custom emoji in Slack. Any name works, as long as you don't use it for anything else.
  2. Connect Slack to the Bot's account. Cursor's help says to "Connect Slack on the Cursor account that owns the Bot before you rely on it."
  3. Ask for a reaction trigger. Per the help page, a routine "can start when the Bot is mentioned, when a word or phrase is mentioned, when you react to a message, or on any message. It can watch one channel or all of Slack."
  4. Check When to run on the routine to confirm the trigger reads the way you meant.

Prompt (ours; Roger's was not published):

Prompt
Set up a routine: when I react with :grok: to a Slack message in any
channel, read the whole thread and do one thing:
- if it is a topic for a meeting, add it to my agenda doc,
- if it is a bug or a request, log a ticket,
- otherwise draft my reply and show it to me.
Never post in Slack yourself. Tell me which one you picked and why.

Good to know#

  • "Within 30 minutes" is Roger's timing. Roger doesn't say whether it runs on a reaction trigger or on a schedule that checks for reactions.
  • Keep it narrow. Cursor warns "a Slack trigger on a busy channel can use a week of usage in a day." A reaction only you add stays cheap.
  • Drafting a reply is the safe default. Let it log tickets on its own only once you trust its sorting.
  • A trigger only sees new activity. "Messages from before the trigger existed don't start a run."

Sources#

Sources

  1. x.com
  2. cursor.com

Something wrong? Tell the bot