Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slack bridge not two way #7978

Closed
cloudwheels opened this issue Jan 1, 2019 · 3 comments
Closed

Slack bridge not two way #7978

cloudwheels opened this issue Jan 1, 2019 · 3 comments

Comments

@cloudwheels
Copy link

Description

Slack bridge not two way

Steps to reproduce

Set up slack bridge to room. Messages (including simple text message) only go one way, from Matrix to Slack

Log: sent/not sent? N/A

Version information

  • Platform: web (in-browser) or desktop?
    WEB
    For the web app:

  • Browser: Chrome, Safari, Firefox? which version? CHROME

Google Chrome 71.0.3578.94 (Official Build) beta (64-bit)
Revision 6da2ba233559398092dabd8dc7bc8e78cd758307-refs/branch-heads/3578@{#890}
Platform 11151.59.0 (Official Build) beta-channel cyan
Firmware Version Google_Cyan.7287.57.180
ARC 5167872
JavaScript V8 7.1.302.31
  • OS: Windows, macOS, Ubuntu, Arch Linux, etc?
    chromebook
  • URL: riot.im/develop / riot.im/app / somewhere else? If a private server, what version of riot-web?
    riot.im/app
@t3chguy
Copy link
Member

t3chguy commented Jan 1, 2019

Did you set up the outgoing webhook on the slack side?

@cloudwheels
Copy link
Author

@t3chguy
I've not located much in the way of documentation so if you have any pointers please?
I'm using the Event bridge as this is recommended. Should I be using Webhook bridge instead?
Will try with Webhook but the Event option looks preferable.
Also, there's a small UI bug with my setup above that the webhook setup doesn't scroll properly.

@cloudwheels
Copy link
Author

@t3chguy OK got it!
I had to just invite the bot to the channel - seems to work now, so will close this.
Docs seem to be lacking round here, not sure the instruction on the integration screen was clear enough first time round.
I won't add an issue for the above ui 'glitch' as the method is essentially deprecated and functionality not blocked (if you navigate by tabbing). I don't think anyone needs anymore work to do round here!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants