Fusebot: Ultimate developer bot for Slack and Discord. Write custom commands in Node.js. Automate, integrate, and do anything on Slack or Discord. No server required. If you can code it, Fusebot can run it. ✨
@colin_lee1 Hey Colin. Great question. Do you mean how are they handled within each command at the user level or at the server/infrastructure perspective?
@colin_lee1@colin_lee1 Ok, so at the user level, the code and credentials is stored directly within the custom command itself. For example, if you run "/fusebot edit foobar" an edit link would appear. If you clicked the edit link, it would bring you to a Web IDE that has everything in it that you wrote for the command. If this includes tokens or credentials, then it would be there too.
We had another community member ask the same question recently during our first round of testing. We have it in our plans to provide the ability to secure a command down to the user level so only the user that created it, can view the source code.
Report
Smooth!
This is great for quickly building out commands for internal use within our teams. We're going to try and use it to let our marketing folks get direct campaign analytics within slack so that they don't have to jump back and forth while in a conversation.
It's probably not mature enough to be a core service we can rely on 100% of the time + its purely slash commands so seems like notifications/triggers are not possible just yet?
@msakbar Thanks, Shehzad! Yeah, this is Fusebot v1.0 and with feedback from users, we make Fusebot vX.X even better. Also, it is open source, so you could contribute. ;-)
Hi everyone! 👋
First, special thanks to Hiten Shah @hishah for hunting us! 🙏
Tomasz here, alongside @cmorefusebit, and we are excited to introduce Fusebot: the simplest way for developers to create Slack and Discord slash commands using Node.js and npm.
Fusebot lets you realize all your creative ideas and custom automation needs for Slack and Discord without friction.
What are some tasks developers have automated with Fusebot?
☑️ Check the status of your systems
☑️ Launch a build or deployment
☑️ Get the latest sales numbers
☑️ Run custom query in your data warehouse
☑️ Get lead status from your CRM
☑️ Report system usage
☑️ Show a meme or a gif
☑️ Message the on-call person
Basically, if you can code it in Node.js, Fusebot can run it. 🏃♀️
We’ve made Fusebot with developers in mind. In three easy steps, you can:
1. Open a web development environment right from within Slack or Discord.
2. Implement your command with all the flexibility of Node.js and npm.
3. Immediately run it from within Slack or Discord.
Fusebot takes care of the hosting, scaling, and securing your slash commands so that you can focus on what you love and do best: coding. All you need to do is bring your imagination. 🔥
I am super curious what you are planning to build, and how you can think of putting Fusebot to work in your Slack or Discord environment. Please share your ideas, feedback, or questions! ✨
Now let’s create a slash command already! 🚀
Cheers,
Tomasz
Report
Loved how quick it was to get started with adding additional functionality to our Discord server.
Discord doesn't have nearly the ecosystem for plugins that Slack does and this felt like it could be the missing-link needed to make teams more productive from one place.
Just getting started with it, but we used it to provide some basic team management types of features such as assigning github pull requests in a way that more aligned with how we operate than the built in github PR assignments work.
Just being able to run "/fusebot assign PR_URL" without figuring out authentication of bots, or finding somewhere to run the service was a big plus in getting this functionality out fast.
Looking forward to what the team is able to add in the future!
@mmwasser Thank you, glad you are finding Fusebot useful! If there is one thing we could do to make it better, what would it be?
Report
@tjanczuk I think there's a bunch of stuff top of mind, but the one thing I think would make it more usable for me is that I appear to have no way to include secrets without everyone on my discord server also having access to those secrets. A bigger one, but a close second (and perhaps a solution to thing one as well) would be a way to "spin out" bots so for example, I could say "/assign PR_URL" instead to shorten it + perhaps have help responses that are specific to my command instead of fusebot itself
@tjanczuk@mmwasser +1 on the user-level security of command-level code for metadata like secrets. We have heard that from others and have an open GitHub issue on it currently.
@mmwasser Yes we scoped out authorization from first release to force this discussion and understand better how people think about permissions within a slack workspace. One idea we had was role-based access control, but were not sure how far to take it. It is clear there needs to be a "developer" role than can edit commands and access secrets. Do you think calling of the commands can be open do everyone or should this also require authorization?
As for creating "shortcut" slash commands, we'll need to look into this. I believe Discord has a model that allows such commands to be created programmatically. Not sure about Slack, but I suppose it does not matter to you.
@patrickt010 totally! I am a bit of a weather nerd (among other things) and I am thinking about how I can wire this up to IFTTT and my IoT weather station outside.
Meetup
Fusebot
Meetup
Fusebot
Fusebot
Fusebit
Fusebot
Fusebit
Fusebit
Fusebot
Fusebot
Fusebit
Clarify
Fusebot
Fusebit
Fusebot
Fusebot
Fusebit