Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Build a Slackbot for sharing Lightdash links in Slack

See original GitHub issue

-Similar to how Metabase does the setup for Slack - Setup your own bot and connect this to your Lightdash instance + your Slack instance. - This means that the Slackbot is part of the app (instead of being a separate slackbot app) - ^If we have references to the Slack Bot in the app, it would be weird to not include it as part of the core app (which is why I think this is a better idea than making a hosted Lightdash Slackbot like Looker

To connect Slack, you’d go to settings, then under organization settings, you’d have slack

This would bring you to a connection page like this:
- Need to think about how we’d guide users through the “building a Slack app” - would we just send them to the docs?

Clicking open slack apps brings you here:

- Select `from an app manifest`

- We give them the manifest to put in here:

Initially, this Slackbot would just allow for Lightdash links to be unfurled in Slack (like GitHub or other apps:)

The unfurls would need to:
- show the entire chart/dashboard. —> reason being: I don’t want to have to login to Lightdash to be able to see what you’ve shared. What if I don’t have a Lightdash account?
- have a link to the chart/dashboard you’re sharing
- If it’s a shared chart/dashboard, then the title of the saved chart/dashboard would be included in the message title
- if it has a description, include the description

Issue Analytics

State:
Created a year ago
Comments:9 (4 by maintainers)

Top GitHub Comments

1reaction

rephuscommented, Oct 7, 2022

@ZeRego let’s unblock this. Should we then start building this without react-dom/server until this blocker is fixed ?. I think it should be easy to migrate.

So we can be using chrome-headless and puppetter as I suggested, we can use html2canvas instead of taking a screenshot of the page, filtering only the div we want to share.

1reaction

ZeRegocommented, Sep 27, 2022

@rephus @owlas Right now there is a blocker when using using react-dom/server to do server side rendering since the lib we use to display echarts [echarts-for-react](https://github.com/hustcc/echarts-for-react) doesn’t seem to support server side rendering.

Opened a ticket: https://github.com/hustcc/echarts-for-react/issues/506

Top Results From Across the Web

Create a bot for your workspace - Slack

Create a bot for your workspace. A bot is a nifty way to run code and automate messages and tasks. In Slack, a...

Enabling interactions with bots - Slack API

Enable conversations between users and apps in Slack by building bots. A conversation between @celeste and @officebot. What are Bots? Getting Started. Creating...

A guide to Slackbot custom responses

A guide to Slackbot custom responses. How to create automated answers for frequently asked workplace questions, gently nudge coworkers, and more.

An introduction to Slackbot | Slack

Sometimes helper, sometimes messenger, always bot — Slackbot is there to help, whether it's through a direct message (DM) or in a channel...

Reference: Deep linking into Slack

Create special links that go directly to apps, app tabs, or conversations within Slack. ... Open a channel; Open a direct message; Open...