Skip to main content

Slack

The Timbr chat bot lets your team ask questions about your data in plain English from Slack. Every answer is computed by your own Timbr instance, under the asking user's own permissions — the same engine behind Ask Timbr, surfaced in the tool your team already has open.

How it works​

The chat bot is not a separate service. It runs inside the Timbr API service as a blueprint mounted at /timbr/api/chatbot/* and executes each query in-process.

  1. Slack delivers the message over an HTTPS webhook — a direct message, an @AskTimbr mention, a slash command or a button click. There is no Socket Mode, no polling and no outbound connection to maintain.
  2. The Timbr API service verifies the request signature, resolves the asking user's verified email address, generates semantic SQL for the question and runs it.
  3. Your data is queried through your ontology, impersonating the asker via the platform credential the API service already holds.

Because there is no shared identity and no service-account token, you get per-user permissions and per-user audit trails — nobody can see through the bot anything they could not see in the platform.

What your team gets​

WhereWhat to typeNotes
Slack direct message<question>No mention or command needed in a DM.
Slack channel@AskTimbr <question>The bot must be in the channel. Replies in a thread.
Slack, anywhere/asktimbr <question>Works without inviting the bot to the channel.
Anywherehelp? works too. Lists every surface and override.

Quick commands are answered immediately, without calling the LLM: list ontologies, list agents, list concepts, list views and list cubes.

Override the default source by prefixing any question. This works on every surface:

ontology:sales_data  How many leads?
agent:my_agent What is total revenue?

Every answer carries follow-up buttons — Show SQL, Show Result Set and Export CSV — so an analyst can verify the query that produced the number. In a channel those follow-ups are ephemeral: only the person who asked sees them.

Requirements​

The bot is configured on your existing Timbr API service instance, not on a new server:

RequirementDetails
Turned onENABLE_CHAT_BOT=true, plus one of CHAT_BOT_DEFAULT_ONTOLOGY or CHAT_BOT_DEFAULT_AGENT
A public HTTPS endpointWebhooks are delivered to it by Slack, so it must be reachable from the internet and present a valid certificate
LLM configurationTIMBR_LLM_TYPE, TIMBR_LLM_MODEL, TIMBR_LLM_APIKEY — the natural language to SQL call is made by the API service itself
RedisBacks result state, the identity cache, event de-duplication and the in-flight guard. Required for correctness whenever more than one worker is running

Setup​

Slack installation is driven by a pre-built app manifest, so there is nothing to fill in by hand in the Slack UI.

The interactive walkthrough for Slack is still being finalised. Until it is published, contact Timbr support for the Slack app manifest and the installation steps.