Dropin is a minimalist Slack slash command integration with one purpose: bridging the gap between Slack and existing shell scripts and programs.
\nDropin runs specific commands and sends their output back to Slack. This allows you to add your existing scripts to Slack without having to build a specific integration around them—for most kinds of use-cases, Dropin will Just Work™ out of the box.
\nDropin supports basic authorization in the form of whitelisted channels and user IDs.
\nStart by creating a new Slack slash command here. Fill out these fields:
\nDropin is released as a static binary. You can download the latest release from the releases page on GitHub. Once you've done so, place the binary wherever you want: /usr/local/bin, /opt/dropin, etc. Set proper permissions by running:
sudo chown root:root /path/to/dropin\nsudo chmod 755 /path/to/dropin\nDropin uses a config file to store the Slack connection info and other settings as well as the chatops commands. Start by setting the global settings:
\nteam = "Slack Team ID"\ntoken = "Slack Token"\nlistenaddress = "127.0.0.1:4000"\ntimeout = "3m"\ntimeout is the global timeout value for chatops commands. Commands that exceed the timeout limit will be canceled. This default value can be overriden per individual command.
Set up authorization:
\n[[users]]\n name = "user name"\n id = "user ID"\n\n[[channels]]\n name = "channel name"\n id = "channel ID"\nHelpful links:
\n\nTo add a command, add a section like this to the config file:
\n[[commands]]\n name = "test"\n description = "This is a test command"\n executable = "/bin/echo"\n chdir = "/tmp"\n args = ["test"]\nWith this command, running /chatops test will return test—the output of running /bin/echo test.
Available options are:
\nname name, passed to the slash command. No spaces alloweddescription descriptionexecutable = "/bin/sleep"chdir the working directory to run the command inargs an array of arguments passed to the commandtakesArguments boolean. if true, any arguments passed to the slash command will be appended to the original commandtimeout an optional override of the global timeout limitAnother example command:
\n[[commands]]\n name = "sleep"\n description = "This command should fail"\n executable = "/bin/sleep"\n chdir = "/tmp"\n args = ["5"]\n takesArguments = false\n timeout = "2s"\nIt's always recommended for web services to communicate over HTTPS instead of plain HTTP. While Slack allows you to run slash commands over HTTP, Dropin can easily be put behind an HTTPS proxy. We'll use Caddy but you can use whichever web server you like (Nginx, traefik, etc.).
\nFirst, set Dropin to listen locally, e.g. localhost:4000. You can use any port you like as long as it's not used by another process and is over 1024.
Add the following to your Caddyfile and Caddy will take care of the rest.
yourdomain.com {\n tls your-email-address-here\n proxy / http://localhost:4000\n}\nSet Slack to use https://yourdomain.com/ as the slash command URL and you'll be all set.
You can use the following Systemd service unit file to run Dropin as a service. All chatops commands will be run as the same user that is running Dropin so pick one that works for you. If your commands don't need any special privileges, you can always use nouser as the user and nogroup as the group.
[Unit]\nDescription=dropin-chatops for Slack\nAfter=network-online.target\n\n[Service]\nRestart=on-failure\n\nUser=dropin\nGroup=dropin\n\nExecStart=/opt/dropin/dropin -config /opt/dropin/dropin.toml\n\n[Install]\nWantedBy=multi-user.target\nReplace /opt/dropin/dropin with the path to the Dropin binary, and /opt/dropin/dropin.toml with the path to config file.
Save the file in /etc/systemd/system/dropin.service and enable it:
sudo systemctl daemon-reload\nsudo systemctl start dropin\nsudo systemctl enable dropin\n