If the last thing you knew about EmmaBot was "she answers Domo questions in Slack," that's still true — but it's not the whole story anymore. She's picked up a handful of other things worth knowing about, and most of them aren't obvious unless someone tells you they exist. This is that list.
Nothing here requires an install or a login. Everything below works in a DUG channel or a DM with her.
The thing she's always done: Domo Q&A
Tag her, or use /ask-domo <question>, and she searches a hybrid-RAG
knowledge base built from Domo's official documentation — an indexed Domo
fileset plus mdrag's domo-official-docs collection — before answering. You
get a doc link, an API call, or a code block — not a guess.
/ask-domo what's the rate limit on the Dataset Export API?
@EmmaBot why would a Beast Mode work in a card but fail in App Studio?
She remembers your conversation, too — built on Letta, so corrections and context from last week still apply this week instead of evaporating when the thread closes.
Research briefings: /storm
If you need more than a Q&A answer — an actual research pass on a topic, with
multiple perspectives — /storm triggers a STORM-style briefing.
/storm Domo governance models for multi-instance orgs
Want to steer which angles it covers, use /storm custom <lenses> <topic>.
It runs in the background; check on it with /storm status <run-id>.
Turn a thread into a tracked issue: /paperclip
Slack threads are where good ideas go to get lost. /paperclip on a thread
files it as a tracked issue instead.
/paperclip
/paperclip list— see what's open/paperclip status <id>— check on a specific one/paperclip spec— write a spec from the thread first, then file it
Turn a conversation into a spec: /spec
Once a thread has actually converged on a decision — not just a debate, an
actual "here's what we're doing" — /spec converts it into a structured spec
document instead of leaving it to be reconstructed from scrollback later.
Diagrams, on request
Ask, and she'll draw a Mermaid diagram inline — a dataflow, a process, an architecture sketch. No slash command, just ask in plain language.
can you diagram how a Domo dataflow moves data from a connector through a
transform to a dataset?
Save something for the group: shared knowledge base
If you hit a good article, forum thread, or write-up worth keeping, hand her
the URL (or paste the text) and ask her to save it. It goes into a shared
knowledge base the community can draw on later — separate from the Domo
documentation /ask-domo searches — so a good find doesn't get lost in
scrollback.
Coming soon: a Home tab, and a way to chip in
A Home tab is rolling out to EmmaBot's app in Slack that will list everything above in one place, so you won't have to keep this post bookmarked. It'll also have an option to chip in toward what it costs to keep her running — entirely optional, not a paywall on anything she does.
What she won't do
She's not going to connect your Google account, delegate work to other bots, or manage agent config — that's admin tooling, not something community members reach for. And she's deliberately not omniscient about when to speak up: tag her, or DM her, and she'll respond; she's not trying to be the loudest voice in every channel.
Full details and background on how she's built: EmmaBot project page. She lives in the Domo User Group Slack — free, independent, join here.
