You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'd like to create a simple Confluence WebHook for another application. There's an admin page to add WebHooks for JIRA, but I don't see the same for Confluence.
The documentation here says I can add WebHooks. https://developer.atlassian.com/static/connect/docs/modules/jira/webhook.html
Webhooks are not available for Confluence at this time. We do have a feature request open for this: CONFSERVER-52487: Webhooks for Confluence
Feature requests are implemented per our Implementation of New Features Policy, so I would suggest voting on and watch the case, and leave any feedback you may have on the feature request itself. Our developers look to these cases when prioritizing which bugs and feature requests to work on. This participation will help the feature to gain traction and will also be the best way to receive updates on the status of this case.
thanks for having the feature request registered. I voted and watch it.
Now that you guys have dropped HipChat and Stride, Webhooks are even more needed to feed other Group Chat platforms without the need to buy 3rd party plugins.
A really good use case for this would be to provide a webhook everytime a document is created from a template. This would allow for a process to be triggered from the creation of a specific document. For example I ask my teams to keep "change logs" which show us what was deployed to a particular system as well as notes observed after deployment. This is setup as a template in our confluence and if we could webhook that to other systems to notify them with the "meta data properties" from the page than we could build some really great processes where Confluence could remain the single source of information and other systems could simply be aware.
This would seem to fit in with overall product strategy for Confluence quite well. It's a real shame this doesn't exist.