RocketChat / RocketChat/Rocket.Chat
Integration with Incoming Webhooks from Slack for Confluence
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Hi!
We're using Confluence Server and RocketChat and would like to notify RC channels about changes in Confluence. Since Confluence Server doesn't support webhooks, we use a plugin called Slack for Confluence (https://marketplace.atlassian.com/apps/1215055/slack-for-confluence?hosting=cloud&tab=overview). We've managed to make the webhooks work basically, but they're displayed empty in RocketChat, although they work in Slack and Mattermost (We've checked with the exact same hooks).
The logs in RocketChat show no errors, but the message doesn't appear to be parsed correctly. Comparing it with Messages created by Microsoft TFS Webhooks, it appears that Slack for Confluence does not limit itself to sending the "attachments", but also sets attributes like the channel which are direct message attributes and not attachments.
Is there something we can do here or do we need an extra Rocket Chat feature? I don't know if a script could do the job, but so far I've failed to understand how exactly this could be accomplished.
I've attached a log file:
sample_log.txt
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached sample_log.txt and compare its Slack for Confluence payload with messages created by Microsoft TFS Webhooks. Trace the incoming-webhook parsing path to determine why the content is empty, then verify that a matching webhook message is rendered in a Rocket.Chat channel.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100