Good day,

I’m using Invision Community Cloud Creator Pro (5.0.20) for my courses and WordPress with WooCommerce and FunnelKit for checkout. My integration is 99% complete but I'm having an issue with course enrollments emails.

After WooCommerce confirms payment, my WordPress plugin finds or creates the Invision member using their checkout email and calls POST /courses/courses/{id}/enroll/{member} once for each purchased course.

In a live PayPal test, the new member received the WooCommerce order email and the Invision password setup email. I set the password, logged in as the member, and confirmed that both purchased courses were accessible. AdminCP also showed both enrollments. However, neither course generated a native “You have been enrolled” email with the Begin Course button.

I then manually enrolled the same member in a different course through AdminCP. The native enrollment email arrived, and its Begin Course button opened the course. Since I used a different course for the manual test, I’d like to know whether course settings could explain the difference.

1. Is the REST enrollment endpoint expected to send the native course_enrolled email, just as manual enrollment through AdminCP does? It assume it should replicate what ACP does.

2. If it is, could a course setting, member notification preference, or mail queue issue explain what I saw? I've been waiting for 30 minutes before composing this message and I can confirm that I didn't get an email.

3. If the REST endpoint intentionally skips the email, is there a supported setting or API action on Cloud to trigger it after a successful REST enrollment? The API reference lists no parameters for the endpoint. REST enrollment endpoint

4. If this is a known bug, is there a fix available or planned for Cloud?

I’m holding off on adding a course access email from WordPress until I know what Invision is supposed to send. If a fix restores the native emails, I want to avoid customers receiving enrollment confirmations from both systems for the same purchase.

Thanks a lot.

I wouldnt say so. APIs will tend to be explicit in what they are doing, and really built for external use to the core system. So if you wanted to send an email, it would be expected to be something you would actively do yourself. Think of it in terms of someone external to the system. I might want to push 10 users who already purchased a course on my own personal site, and set that course are purchased. I dont want to send another email, as they already know they purchased it