-
Notifications
You must be signed in to change notification settings - Fork 3
justinhunt/moodle-local_trigger
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
Broadcast Moodle events to pre-registered webhooks ------------------------------------------ This has been designed for use with Zapier but could be used in other situations too. Installation -------------- Download,unzip,rename Or git clone the plugin folder "trigger" into the [path/to/moodle]/local folder. Usage -------------- On the settings page for the plugin enter eventname and webhook (url) pairs. e.g trigger: \core\event\user_enrolment_deleted webhook: https://hooks.zapier.com/hooks/catch/1020304/v9plzv/ If the 5 slots are too few, you can add more by increasing the trigger count setting on the same page. After changing any of the settings on the settings page, you will need to: i) visit your site's notifications page to make sure the new setting does not need to be "installed." If so, just let Moodle do that for you. ii) "purge all caches" for any changes to be reflected. Do that at: site admin->debugging->purge all caches Using with Zapier -------------- The trigger plugin is used by the Poodll NET zapier app. This allows you to connect over 5000 different SaaS apps via their APIs to a Poodll NET/Moodle site. https://zapier.com/apps/poodll-net/integrations If you do not use Poodll NET you can still use the Poodll NET Zapier app with your own Moodle site. You will need to create a web services user on your Moodle site, and then generate a web token that can be pasted into Zapier as the Poodll NET API key. Documentation for how to do that is here: https://support.poodll.com/en/support/solutions/articles/19000141629-poodll-trigger-api-key-web-token Justin https://poodll.com
About
Send events that occured to 3rd party services
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published