Notifications for updated content in articles

Webhooks about new/modified articles would be perfect for integration purposes too.

There is existing integration between Crowdin and Zendesk, it uploads articles for translation and delivers translations back. Currently, we have to pull all source articles from Zendesk periodically and compare them with existing files in Crowdin.

* If we detect a new article, it's uploaded

* If we detect a modified article, the existing file in Crowdin is updated

When KB is quite large, it takes time to synchronize everything. Webhooks will dramatically decrease the number of requests Crowdin needs to submit to ZD, it will make the integration > x10 faster.

Webhooks will be extremely useful for different kinds of integrations, so we truly hope Zendesk team will put them on the roadmap for the near future 🙏

I m agree ! Update = notification :)

Hi,

I have posted my feedback in the other thread on this topic (https://support.zendesk.com/hc/en-us/community/posts/4409222573466-Follow-article-feature-to-notify-users-of-article-content-updates?page=4#community_comment_4506595532698).

I would also echo Nikki's comment that it would be optional to send an update to customers on an articles update. As mentioned, if there is a typo, we don't necessarily need to notify everyone, but if there were a major update posted, it would be great.

Best regards,
Stephen

I would also add the request that a notification not go out by default for every update, but some way to opt to notify upon update or not. For example, have the option to "Save Update", or "Save and Notify Followers". Sometimes you might make a minor change, like correct a typo, and you wouldn't want to draw special attention to it with an email blast. 

I also use one single article to update with new release notes. I've decided to enable comments so that I can comment about the update, but make comment moderation required so that we don't get public comments. I could also opt to turn on comments for the article, make my comment, and then turn comments back off. I also saw the suggestion elsewhere that we could delete the comment to reduce clutter. My point is, the workaround isn't TOO tricky but "Save and Notify Followers" seems like a good solution.

identical topics you can upvote

https://support.zendesk.com/hc/en-us/articles/4408820052506?page=1#comment_4426879916442

https://support.zendesk.com/hc/en-us/community/posts/4409222573466-Follow-article-feature-to-notify-users-of-article-content-updates?page=4#community_comment_4426929446938

We need the same functionality. I agree, why else would you follow an article? Our customers assume they will be notified if we update the page and then come back to us upset when they were not notified. 

Agree.
What else is the purpose of following an article?
You should fix this as soon as possible.

Thank you Josef Prandstetter for sharing your company use case. 

Hello Tetiana Gron

For us this is also an import feature - our scenario:

We are a software vendor which is affected by the Log4j vulnerability in several product families.

We have provided Help Center articles on the current state of knowledge to our customers and partners promptly after the vulnerability became known.
In the last few days this status has been constantly changing regarding workaround, mitigation or solution.
We have assumed that customers and partners will be notified of any changes as we make changes in the original post and they follow it.
We do not consider a separate post for each update be overseeable and purposeful.

Is our motivation for this change understandable?

I agree!