You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A starting point for developers to integrate openedx-events into their projects, allowing seamless event-driven workflows.
A testing tool for contributors of openedx-events, providing a straightforward way of validating their contributions. Contributors can integrate their event changes here to verify that the event is being sent and received as expected.
The name change reflects more of a generic testing tool for events integration, moving from Zapier to support other webhook implementations. For instance, events can be tested with tools like webhook.site or by checking the logs in relevant services without necessarily configuring Zapier.
This change does not mean dropping support for Zapier but extends compatibility to any webhook provider, making it more accessible for contributors.
The text was updated successfully, but these errors were encountered:
I'm fine with the change. This is a repo to be filled with examples. If the examples contain something more than zappier, lets change the name. If it will only contain the zapier example, but we are using the goal of being more general in the future as the excuse I don't see the necessity.
If you still want to move forward with the change, go ahead.
Proposal
This repository serves as:
The name change reflects more of a generic testing tool for events integration, moving from Zapier to support other webhook implementations. For instance, events can be tested with tools like webhook.site or by checking the logs in relevant services without necessarily configuring Zapier.
This change does not mean dropping support for Zapier but extends compatibility to any webhook provider, making it more accessible for contributors.
The text was updated successfully, but these errors were encountered: