Integrate Amazon CloudWatch with Thinkific

Appy Pie Connect allows you to automate multiple workflows between Amazon CloudWatch and Thinkific

  • No code
  • No Credit Card
  • Lightning Fast Setup
20 Million man hours saved

Award Winning App Integration Platform

About Amazon CloudWatch

Amazon CloudWatch is a monitoring service for AWS cloud resources and the applications you run on AWS.

About Thinkific

Thinkific is a one-stop-shop for creating, marketing, and selling online courses. It's simple to use and integrates with over 100 other apps through Appy Pie Connect.

Thinkific Integrations

Best Amazon CloudWatch and Thinkific Integrations

  • Amazon CloudWatch Integration Thinkific Integration

    Amazon CloudWatch + Thinkific

    Create User to Thinkific from New Log in Amazon CloudWatch Read More...
    Close
    When this happens...
    Amazon CloudWatch Integration New Log
     
    Then do this...
    Thinkific Integration Create User
  • Amazon CloudWatch Integration Thinkific Integration

    Amazon CloudWatch + Thinkific

    Enroll User in Thinkific when New Log is created in Amazon CloudWatch Read More...
    Close
    When this happens...
    Amazon CloudWatch Integration New Log
     
    Then do this...
    Thinkific Integration Enroll User
  • Amazon CloudWatch Integration Thinkific Integration

    Amazon CloudWatch + Thinkific

    Unenroll User in Thinkific when New Log is created in Amazon CloudWatch Read More...
    Close
    When this happens...
    Amazon CloudWatch Integration New Log
     
    Then do this...
    Thinkific Integration Unenroll User
  • Amazon CloudWatch Integration Amazon CloudWatch Integration

    Thinkific + Amazon CloudWatch

    Enable Alarm in Amazon CloudWatch when New Enrollment is created in Thinkific Read More...
    Close
    When this happens...
    Amazon CloudWatch Integration New Enrollment
     
    Then do this...
    Amazon CloudWatch Integration Enable Alarm
  • Amazon CloudWatch Integration Amazon CloudWatch Integration

    Thinkific + Amazon CloudWatch

    Enable Alarm in Amazon CloudWatch when New User is created in Thinkific Read More...
    Close
    When this happens...
    Amazon CloudWatch Integration New User
     
    Then do this...
    Amazon CloudWatch Integration Enable Alarm
  • Amazon CloudWatch Integration {{item.actionAppName}} Integration

    Amazon CloudWatch + {{item.actionAppName}}

    {{item.message}} Read More...
    Close
    When this happens...
    {{item.triggerAppName}} Integration {{item.triggerTitle}}
     
    Then do this...
    {{item.actionAppName}} Integration {{item.actionTitle}}
Connect Amazon CloudWatch + Thinkific in easier way

It's easy to connect Amazon CloudWatch + Thinkific without coding knowledge. Start creating your own business flow.

    Triggers
  • New Log

    Triggers when a new log is created.

  • Lesson Complete

    Triggers when user completes a lesson of course.

  • New Collection

    Triggers when a new collection has been made.

  • New Enrollment

    Trigger when a user enrolls in your course.

  • New Free Preview Enrollment

    Triggers when a user enrolls in the free preview of your course.

  • New Order

    Triggers when a new purchase has been made.

  • New Product

    Triggers when a new product has been made.

  • New User

    Triggers when a new user is created.

    Actions
  • Enable Alarm

    Enable Alarm

  • Create Update User

    Create a new user or update an existing user.

  • Create User

    Creates a User

  • Enroll User

    Creates or finds a user in your Thinkific site, and enrolls them in a course or bundle. Available on Pro + Growth plan or higher

  • Unenroll User

    End a student's enrollment in a course or bundle either immediately or at a specified date. Available on Pro + Growth plan or higher

Compliance Certifications and Memberships

Highly rated by thousands of customers all over the world

We’ve been featured on

featuredon
Page reviewed by: Abhinav Girdhar  | Last Updated on July 01, 2022 5:55 am

How Amazon CloudWatch & Thinkific Integrations Work

  1. Step 1: Choose Amazon CloudWatch as a trigger app and authenticate it on Appy Pie Connect.

    (30 seconds)

  2. Step 2: Select "Trigger" from the Triggers List.

    (10 seconds)

  3. Step 3: Pick Thinkific as an action app and authenticate.

    (30 seconds)

  4. Step 4: Select a resulting action from the Action List.

    (10 seconds)

  5. Step 5: Select the data you want to send from Amazon CloudWatch to Thinkific.

    (2 minutes)

  6. Your Connect is ready! It's time to start enjoying the benefits of workflow automation.

Integration of Amazon CloudWatch and Thinkific

Amazon CloudWatch

Amazon CloudWatch is a monitoring system as a service (SaaS. offered by Amazon Web Services (AWS. It provides a set of health and performance metrics for cloud computing services such as AWS Elastic Compute Cloud (EC2), AWS Lambda, and Amazon EBS. It also offers integrated dashboards, alerts, and actions on those metrics.

At the time of writing this article, Amazon CloudWatch has been in use for almost 4 years. The last time it was updated was on June 30, 2016. The latest version is 1.0.x.

Thinkific

Thinkific is an online learning platform that allows you to create courses and enrpl students for a fee. You can create any type of course including business, personal development, software, fitness and more. Thinkific charges a monthly fee based on the number of students you have enrpled and the features you need. The cost per student ranges from $7 to $11 per month and the average class has 5 to 10 students.

Thinkific offers different plans depending on your needs. The free plan includes unlimited students, classes, and up to 100MBs of media storage. A premium plan costs $16 per month and includes unlimited videos and courses, unlimited audio recordings, coupons to give away to students, and up to 100MBs of media storage.

At the time of writing this article, Thinkific has been in use for almost 3 years. The last time it was updated was on July 22, 2018. The latest version is 3.0.6.

Integration of Amazon CloudWatch and Thinkific

How does this integration work

Thinkific does not offer an API exposed to developers so the integration is done via Amazon SNS. SNS allows for publishing messages to topics. In this case, events are published from Thinkific to a topic that Amazon CloudWatch subscribes to and triggers an alarm event every time a new student subscribes or drops out from a class. Amazon CloudWatch also publishes events every time a new course is created or updated in Thinkific.

The first thing that Amazon CloudWatch does is check whether any alarms exist that match the event type. If no alarms exist, nothing happens; if alarms do exist, they are evaluated against the newest event data.

In our case, we are interested in whether a new student has subscribed to a class or canceled his/her subscription. These are the events that will trigger an alarm event in thinkific_student_subscribed and thinkific_student_canceled . The first event will trigger an alarm when a new student subscribe to a class and the second one will trigger an alarm when a student cancels his subscription to a class. Our workflow looks like this:

If the event matches one of our alarms then we want it to be processed further by our fault detector (Amazon CloudWatch. So we send any information about our alarm to our fault detector as part of the payload of the event we triggered earlier. This way, our fault detector can read any information we want it to read like which class did the student subscribe to and how long ago did she subscribe to it (data retention period. We can get this information by querying our database through Amazon Redshift Spectrum which is connected to our fault detector through Kinesis Streams. We have chosen this architecture because we have some data that is too big to be stored in our database and therefore we need to store these data in S3 first before reading them through Redshift Spectrum which offers better performance than reading directly from S3. We retrieve any information about the event that interests us from our database using Redshift Spectrum and include them as part of the payload of our event triggered earlier. Now we send our payload with all the information about our alarm together with the event that triggered it to our fault detector which will check if everything looks good (if it does not then it will take action. We also include our account name ([email protected]. in the payload of the event triggered earlier so that our fault detector can send us an email notification every time an alarm fires in our account. We can configure how many emails we want to receive every time an alarm fires per day or no more than once per day via Amazon SNS topic's configuration page or through AWS CLI or AWS SDK. We can also configure who should receive these emails through Amazon SNS topic's configuration page or through AWS CLI or AWS SDK. For example, if we want all employees at our company to receive emails every time an alarm fires then we will configure all their email addresses for "To" parameter in Amazon SNS topic's configuration page or through AWS CLI or AWS SDK as shown below. Our fault detector sends us an email every time an alarm fires in our account with information about which alarm fired and what kind of problem did it detect. We can configure how many emails we want to receive from our fault detector every time an alarm fires in our account via Amazon SNS topic's configuration page or through AWS CLI or AWS SDK but usually it is one email per day maximum (because most problems are intermittent issues that come back after a while. Now we send emails with information about which alarm fired in our account with information about which alarm fired to people who signed up to receive them via Amazon Simple Notification Service (SNS. topic's configuration page or through AWS CLI or AWS SDK. This way everyone at our company will know when something goes wrong in any of our services. Note. We can configure how many emails we want to receive from Amazon SNS topic's configuration page or through AWS CLI or AWS SDK but usually it is one email per day maximum (because most problems are intermittent issues that come back after a while. Now we send emails with information about which alarm fired in our account with information about which alarm fired to people who signed up to receive them via Amazon Simple Notification Service (SNS. topic's configuration page or through AWS CLI or AWS SDK. This way everyone at our company will know when something goes wrong in any of our services. Note. We can configure how many emails we want to receive from Amazon SNS topic's configuration page or through AWS CLI or AWS SDK but usually it is one email per day maximum (because most problems are intermittent issues that come back after a while. Now we send emails with information about which alarm fired in our account with information about which alarm fired to people who signed up to receive them via Amazon Simple Notification Service (SNS. topic's configuration page or through AWS CLI or AWS SDK. This way everyone at our company will know when something goes wrong in any of our services. Note. We can configure how many emails we want to receive from Amazon SNS topic's configuration page or through AWS CLI or AWS SDK but usually it is one email per day maximum (because most problems are intermittent issues that come back after a while. Now we send emails with information about which alarm fired in our account with information about which alarm fired to people who signed up to receive them via Amazon Simple Notification Service (SNS. topic's configuration page or through AWS CLI or AWS SDK. This way everyone at our company will know when something goes wrong in any of our services. Note. We can configure how many emails we want to receive from Amazon SNS topic's configuration page or through AWS CLI or AWS SDK but usually it is one email per day maximum (because most problems are intermittent issues that come back after a while. Now we send emails with information about which alarm fired in our account with information about which alarm fired to people who signed up to receive them via Amazon Simple Notification Service (SNS. topic's configuration page or through AWS CLI or AWS SDK. This way everyone at our company will know when something goes wrong in any of our services. Note. We can configure how many emails we want to receive from Amazon SNS topic's configuration page or through AWS CLI or AWS SDK but usually it is one email per day maximum (because most problems are intermittent issues that come back after a while. Now we send emails with information about which alarm fired in our account with information about which alarm fired to people who signed up to receive them via Amazon Simple Notification Service (SNS. topic's configuration page or through AWS CLI or AWS SDK. This way everyone at our company will know when something goes wrong in any of our services. Note. We can configure how many emails we want to receive from Amazon SNS topic's configuration page or through AWS CLI or AWS SDK but usually it is one email per day maximum (because most problems are intermittent issues that come back after a while. Now we send emails with information about which alarm fired in our account with information about which alarm fired to people who signed up to receive them via Amazon Simple Notification Service (S

The process to integrate Amazon CloudWatch and Thinkific may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.