Automations

With Automations you can react to specific events happening in COACHY and either set a tag in your Autoresponder or send out a Webhook to your custom URL.

Here,we will introduce you to all the events and explain some points you should look out for.

Feature ist available for Coachy DELUXE and ENTERPRISE and currently in beta phase.

  • Access granted
    • ​​​​​​​Applies to all types of access, including manual, CSV imports and access via Quentn.
    • Contacts are only tagged in the connected autoresponder, not created. To create new contacts, use the settings in accesses or a webhook here in the automations and transfer contacts to the autoresponder via Make/Zapier.

    • Coachy transfers the type and name of the access in the webhook so that you can work with this information in your automations, for example to only transfer members that have been imported. Or only those that have been created manually.

    • When importing, please bear in mind that many providers have limitations and can only process a certain number of API calls per minute/hour. This is especially true if you have an automation that sends an email via SMTP for each new access imported.

  • Access expired
    • The event is triggered shortly after midnight on the day on which an access expires.
    • The event applies to every access, so it can be received many times. This means that the event is also triggered if an access expires but there is still another active access for the same training/product.
  • Access will expire in x days

    Example: If an access expires on 08.12.2025 and the event ‘Access expires in 2 days’ is set, the event will fire shortly after midnight on 06.12.2025, as the member will then have two full days left.

  • Member has completed x %
    • The percentage always refers to the entire course. Please keep this in mind, if you are working with timing and/or only selling parts of a course.
    • The event is only triggered again if members/coach reset the progress.
    • The event is not triggered again if the training has been increased and the member exceeds x % again.
    • The event is also not triggered again if you change the percentage in the event but a member has already received the event.
  • Member has completed a lesson
    • The event is only triggered again if member/coach reset the progress and complete a lesson a second time.
    • The event is not triggered again if content is deleted/extended in a lesson and members complete this lesson a second time.
  • Member has completed a module
    • The event is only triggered again if members/coaches reset their progress and complete a chapter again.
    • If you add lessons to a chapter at a later date, the chapter will shown as incomplete for the member. However, the event will not be triggered again once the new lessons have been completed.
  • Member has completed a test

    Important: The event is triggered with every test attempt. If your members have multiple attempts and/or can reset the test, multiple events per member are also possible. Keep this in mind for your automations.

    • Tags are only assigned to connected autoresponders if a test has been passed.
    • Coachy sends to a webhook info about the test status as the parameter test_status ‘NOT PASSED’ and ‘PASSED’.
  • Member has completed all tests
    • Event is triggered if a member has passed all tests.
    • Event is triggered again, if progress was resetted.

     

  • Member has downloaded a file

    Event is only triggered again, if progress was resetted.

  • Member got access to new chapter
    • The event is only triggered once for member. So if you change timing, it will not trigger again.
    • If your members do your training a second time and should receive the events again, please work with a timing and new events accordingly.
  • Member got access to new lesson
    • The event is only triggered once for member. So if you change timing, it will not trigger again.
    • If your members do your training a second time and should receive the events again, please work with a timing and new events accordingly.
    • The event is also triggered if the lesson is in a chapter that has been unlocked via timing. The lesson therefore does not have to have its ‘own’ timing.
  • Member did not logged in for x days

    Important: x days are 24 hours.

    Example: Last login on 12.02.2025 at 15:13 and the event is set to apply to members who have not logged in for one day: Event is triggered on 13.02.2025 at 15:13.

    Important: The event only looks into the future!

    Example:

    You create the event ‘has not logged in for 10 days’ on 01.03.2025.

    • Member A has not logged in since 27.02.2025.
    • Member B last logged in on 02.03.2025.
    • Member C was added to your member area on 05.03.2025 and has never logged in since.

    Consequence:

    • The event for member A is triggered for the first time 10 days after his next login.
    • The event for member B will be triggered on 12.03.2025.
    • The event for member C is triggered on 15.03.2025.

    The event therefore applies to all members who have logged in since the event was activated or who were created for the first time.