Skip to content
Log inStart free

Message Basedash directly in Slack

You can now chat with Basedash one-on-one in Slack. Open the Basedash app’s Messages tab, pick a suggested prompt or type your own question, and get the same answers, charts, and analysis you’d get in a channel thread, without @mentioning the bot in front of everyone.

CSV files now come through as real Slack files. When you ask Basedash for a CSV in a Slack thread, the file is attached right in the conversation, ready to open or forward. Workspace admins will see a “Slack update available” prompt in Basedash; approve the new permissions to turn on file uploads. Until then, replies keep their download link.

Automations can deliver CSV files

Scheduled automations can now create downloadable CSV exports, the same way chat can. Ask for a CSV in an automation’s instructions, like “send a CSV of last week’s new signups every Monday”, and each run builds the file from your data.

Every delivery includes the file. Slack messages attach the CSV in the message’s thread, and emails and the automation’s run history include a Download CSV link. If a run builds the CSV but stops before writing its summary, the file is still delivered. Downloads go through Basedash, so recipients still need access to the automation to open them.

Stopping a response keeps what’s already done

Pressing Stop in chat no longer erases the turn. Your question and the partial answer stay in the conversation with a “Stopped” label, so you can read what the assistant found before you redirected it. On your next message, the assistant knows the previous answer was cut short and that any charts or edits it started may be half-finished, so it picks up from there instead of starting over.

Long analyses also end more gracefully. Chat can now take up to 50 steps on a single question, up from 30, and when it gets close to the limit it wraps up on its own: it summarizes what it found and lists what’s still unfinished, instead of ending with a bare “Continue” button.

Insights reads like a newspaper

The Insights feed has a new borderless, editorial layout. The top story leads the page, the rest flow in two columns separated by thin rules, charts sit flush with their captions, and each preview shows as much text as fits beside its chart. When you open the sidebar or chat panel, the feed switches to one column instead of cramping the stories. Insight pages get larger headlines and more readable body text, on desktop and mobile.

Large Insights feeds now load in pages with a Show more button, so the page opens quickly no matter how many insights you have. Scheduled insights also work across all of your data again: organizations with several data sources get findings from every connection the insight’s creator can access, not just one.

Fixes and improvements

  • Clarified chat error messages when a data source is down. Chat now names the data source it couldn’t connect to, instead of showing a generic error or blaming the AI model.
  • Added a Retry button to charts that fail with “Unable to connect to database”, so you can recover without reloading the page.
  • Fixed long chats and automations failing with “Your input exceeds the context window”.
  • Fixed chats failing with “Invalid time value” when a table contained dates far in the future.
  • Fixed insights that could go missing when they were being generated during a Basedash update. They now retry and finish.
  • Applied schema, table, and column access rules to organization admins too, so a “no access” rule now covers everyone. Admins can still see every object in the access settings to change its rules.
  • Improved AI-written SQL for MotherDuck databases connected through the PostgreSQL connector, so queries use DuckDB syntax instead of failing on Postgres-only functions.
  • Made new charts open the dashboard chat with your cursor in the message box, so you can describe the chart right away.
  • Added a “This dashboard has been deleted” state for dashboards shown in chat, instead of a blank preview.
  • Fixed new dashboard headers and blocks that could appear and then disappear until you reloaded.
  • Fixed public dashboards embedded on other websites failing to load charts in Safari.
  • Fixed record dropdown filters on public dashboards showing “No values found”.
  • Polished the mobile experience: the Back button works after redirects, chart menus are reachable on touch screens, and menu items no longer need two taps on iOS.
  • Restyled the sign-in pages for connecting MCP clients to match Basedash, with light and dark mode and translations.
  • Refreshed icons across the app, with clearer symbols, filled radio buttons, and evenly spaced keyboard shortcut keys.