Open hikalkan opened 4 years ago
Sorry, but "urgent" is not a word we like, especially for feature requests. If that's a requirement of your solution please implement it yourself. "normal" is a good priority level for this issue. We have more fundamental features/enhancements with higher priority. Thanks for your comment.
Still in the roadmap :)
Hi @hikalkan
Any plans to release this feature yet? I'm hopeful
@Mattia is working on this module porting it from ABP Bolierplate I am hopeful that he is able to share what he is doing, so that I can help or use what he has already done :)
Hi @albutta & @mattia, I'm quite curious to learn more about what you've been working on and how I might be able to assist or leverage what you've done so far.
I have not implemented webhooks into my application as yet. I add webhook posts when requested. As a workaround, I have a data table with a few fields, EntityName, EventName, BackgroundJobName and subscriber address. and API key. When a entity is created or updated, a check is done for a subscriber for the entity and event, and then creates a background that posts the entity details to the subscriber. If a 200 is returned, the background job is closed, else a retry is done as per background priority.
This works for now, as I don't have that many.
Any update?
Hi @hikalkan this is urgent. For web based services this is a feature all of us need. We can prioritize?