Skip to content

[Tool] Create a Slack channel shared by two organizations

Notifications You must be signed in to change notification settings

Empia/slackline

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

9 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Share channels between Slack accounts!

We are big fans of Slack and have been using it for a while now. Our friends at Vizzuality started using it recently and we missed not being able to speak with them, so I just created a quick service to link two channels from two Slack organizations.

How can I set it up?

Dead simple, follow this steps from each organization's account.

  1. Create a channel you want to share with another organization.
  2. Create an Incoming WebHook itntegration and select the channel you created.
  3. Copy the Incoming WebHook token (you can find it in the left column from the integration page).
  4. Create a URL with the following format: http://slackline.herokuapp.com/bridge/?token=[TOKEN]&domain=[YOUR_SLACK_DOMAIN] send it to the person setting up the other organization.
  5. The person setting up the other organization will send you a similar URL with their domain and token, create an Outgoing WebHook with that URL and the channel you created in step 1.

Once you have done this in both organizations, you will have a chat-room shared by both organizations.

Here you have an example of a Outgoing WebHook URL:

http://slackline.herokuapp.com/bridge/?token=bcaa5867b1d42142b74eDVA4&domain=avengers.slack.com

How does it work?

We are just bridging hooks, we don't store any messages going through the bridge.

ToDo

We don't support custom avatars right now.

If somebody from Slack is reading this, it would be great to be able to set the icon_url for the message to be something like http://[DOMAIN]/avatar/[USER_ID] to set the USER_ID based on the information from the Outgoing WebHook with no extra requests or state.

DISCLAIMER

This project is not officially supported by Slack and they are not responsible for the use you make of this and won't give you any support related to this integration.

Now that we are talking disclaimers... I'm not responsible either for any use of the software. Use at your own risk and to be safe it might be good if you deploy this yourself rather than using my Heroku deployment ;)

MIT LICENSE

Copyright (C) <2014> Ernesto Jimenez [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

About

[Tool] Create a Slack channel shared by two organizations

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published