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

WebHook System #4223

Open
hikalkan opened this issue Jun 4, 2020 · 8 comments
Open

WebHook System #4223

hikalkan opened this issue Jun 4, 2020 · 8 comments

Comments

@hikalkan
Copy link
Member

hikalkan commented Jun 4, 2020

No description provided.

@dicksonkimeu
Copy link

Hi @hikalkan this is urgent. For web based services this is a feature all of us need. We can prioritize?

@hikalkan
Copy link
Member Author

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.

@xewn
Copy link

xewn commented Apr 6, 2022

Asp.net core WebHooks

@albutta
Copy link

albutta commented Nov 22, 2022

Still in the roadmap :)

@rei-okawara-portx
Copy link

Hi @hikalkan
Any plans to release this feature yet? I'm hopeful

@albutta
Copy link

albutta commented Aug 16, 2023

@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 :)

@AhmadAlMunajjed
Copy link
Contributor

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.

@albutta
Copy link

albutta commented Apr 11, 2024

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.

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

No branches or pull requests

6 participants