Marketing tools and webhooks

Updated

Public LMS Pro connects the LMS to other services: it adds students to your email marketing tool, and sends events to any service through signed webhooks.

Marketing tools

Pro adds students to Mailchimp, MailerLite, HubSpot, Brevo or FluentCRM, with tags for enrollments and completions. Set them up on LMS → Settings → Email marketing.

SettingDefaultWhat it does
Only add people who agreed to receive marketing emailsOnRequires consent. People are asked with a box that reads “Email me news about courses. You can unsubscribe at any time.”
Tag for students who enroll ({course} is the course title)Enrolled: {course}The tag given when a student enrolls.
Tag for students who complete a course ({course} is the course title)Completed: {course}The tag given when a student completes a course.

Then fill in the fields of the tool you use:

ToolFields
MailchimpMailchimp API key, Mailchimp audience id and Ask Mailchimp to confirm each new address by email (double opt-in). The API key ends in its data centre, such as -us21.
MailerLiteMailerLite API key and MailerLite group id.
HubSpotHubSpot private app access token.
BrevoBrevo API key and Brevo list id.
FluentCRMAdd students to FluentCRM on this site and FluentCRM list id. FluentCRM must be active on the site.

External services

A marketing tool is contacted only once you set it up. See External services.

Webhooks

A webhook sends events to another service as they happen, signed so the receiver can trust them. Manage them on LMS → Webhooks.

  1. Go to LMS → Webhooks and press New webhook.
  2. Enter a Name and the Send to (HTTPS address): the full HTTPS address the events should go to.
  3. Tick at least one of the Events, and press Create webhook.
  4. Copy the Signing secret to the receiving service. It is shown only now. Then press I have copied it.

The events are:

  • A student is enrolled
  • An enrollment ends
  • A student completes a course
  • A certificate is issued
  • A quiz attempt is graded
  • An assignment is graded
  • An order is paid
  • An order is refunded
  • A subscription starts, renews, fails, is cancelled or ends

Each request carries an X-Publms-Signature header made with the signing secret. The screen explains how the receiver checks it. New signing secret makes a new secret; the receiver must use the new one from then on.

Under Deliveries you see what was sent to a webhook and whether it was Delivered or Failed. Send a test event tries the address, and Send again repeats a delivery.

Zapier

LMS → Webhooks also explains how to connect Zapier: you create an Application Password for a manager on Users → Profile, then use the addresses shown on the screen in Zapier with that user name and password.

Was this page helpful?