Moodle + Ecwid + Make.com Integration for Automated Course Enrollment

Project: Ecwid → Make.com → Moodle Automated Course Enrollment I have an existing production Moodle website with multiple online courses. Courses are sold through my Ecwid store. Current environment: - Moodle 4.1+ (Build: 20221229) - cPanel hosting - Ecwid online store - Make.com account - Moodle Web Services and REST protocol are already enabled Currently, students receive a shared Moodle enrollment key after purchasing a course. Some users share this key with other people. I want to completely eliminate shared enrollment keys and automate enrollment. Required workflow: Ecwid paid order → Make.com → identify purchased product/course → find Moodle user by email → create user if necessary → enroll that user in the corresponding Moodle course → send secure access/first-login instructions. If the customer already has a Moodle account, the existing account must be used and the newly purchased course simply added to it. There should be no shared enrollment key. Important: secure first login: For newly created Moodle accounts, I do NOT want passwords sent by plaintext email. Please implement a secure password-setting / password-reset / first-login mechanism. Ecwid / Make requirements: - Automation should trigger only for successfully paid orders. - Ecwid Product ID/SKU must map to the appropriate Moodle Course ID. - It should be easy for me to add additional product → course mappings later. - Multiple eligible courses in one Ecwid order should be supported. - The automation must be idempotent: if Ecwid/Make sends the same event twice, it must not create duplicate users/enrollments or send unnecessary duplicate emails. - Unpaid/failed orders must never grant Moodle access. - Appropriate error handling/retry should be configured if Moodle is temporarily unavailable. Moodle REST API: I have already created a custom Moodle External Service called: Ecwid-Make Integration REST protocol is enabled. Functions expected may include: 1) core_user_get_users_by_field 2) core_user_create_users 3) enrol_manual_enrol_users Please use a dedicated service account/token with minimum necessary permissions rather than unrestricted administrator API access. Existing Moodle issue: - There is currently an HTTP 500 error when I go to: External services → Ecwid-Make Integration → Functions → Add functions. - This needs to be diagnosed from - Moodle/PHP/server logs and fixed properly. VERY IMPORTANT — production safety / backup (!) This is an existing production Moodle installation containing real courses, users and student progress. Before making significant changes, please: 1) Check cPanel/server disk space and inode usage. 2) Check PHP/Moodle compatibility and relevant PHP/server errors. 3) Create and verify a complete backup sufficient to restore the Moodle site, including the database, moodledata, Moodle application files and config.php. 4) Tell me where the backup is stored and how it can be restored. Do NOT upgrade Moodle, PHP, database, plugins, reinstall Moodle, delete users, modify student progress, or make unrelated server changes without discussing them with me first (!). After the backup is verified, you may separately advise me whether Moodle/PHP/plugins should be upgraded. Account-sharing protection: The primary objective is to eliminate shareable enrollment keys. Please also configure reasonable Moodle protection against account sharing where appropriate (for example, concurrent-session restrictions), without making normal student access unnecessarily difficult. Testing required Please test at minimum: 1) new customer buying a course; 2) existing Moodle user buying another course; 3) duplicate webhook/order event; 4) unpaid/failed order; 5) two courses purchased in one order; 6) unknown/unmapped product; 7) temporary Moodle/API failure. Deliverables: 1) Verified Moodle backup 2) HTTP 500 issue diagnosed/fixed 3) Secure Moodle REST API configuration 4) Working Ecwid → Make.com → Moodle automation 5) Automatic account creation/reuse 6) Automatic enrollment into the correct course 7) Secure first-login/password-setting process 8) Duplicate-order protection 9) Error handling 10) Automated customer notification 11) Basic account-sharing protection 12) Documentation of the Make scenario and Moodle API configuration 13) Simple instructions showing me how to add another Ecwid Product → Moodle Course mapping myself Required experience: I am looking for someone with real hands-on experience with Moodle, Moodle REST Web Services/API, PHP troubleshooting, Make.com, webhooks/API integrations and preferably Ecwid. This is intended as a fixed-price project with milestones. Please explain briefly how you would approach the project rather than sending a generic proposal.