We will explain the basic principles of building automation and which processes can be automated on Kwiga. For examples of automating popular processes, see other articles.
To automate a process, you need to define the starting event that will trigger the automation. This event can be a user registration, a course payment, or other events. The full list of events is provided in the article below.
Please note that a configured automation will only start triggering after the event occurs. If you configured automations, but the event occurred BEFORE it was configured, then the automation will not start. Example: You want a new email to be sent to all clients who register on the platform. Contacts who are already registered will not receive this email; only those clients who register after you configure the automation will receive it. To perform actions with contacts for whom the event has already occurred, use other tools: campaigns, bulk actions, depending on the expected action and the event itself.
In automation, you can configure a scenario. A scenario consists of one or more triggers.
A trigger is a simple process: event - possible delay or condition - action. Example: A student does not log in to the course for 5 days - they receive a reminder email. To create such a trigger, you need to decide:
-
What will serve as the starting point, which event
-
Whether you need to additionally check any condition after the event occurs or not. Whether an additional delay is needed before checking the condition.
-
What needs to be done, which action. Optionally, you can set a delay before performing the action.
A scenario is a chain of several triggers, meaning each subsequent trigger starts after the action in the previous trigger is completed. If there is no action in the previous trigger, the next trigger will not start either. Example: A student does not log in to the course for 5 days - receives an email (trigger 1), then we wait a couple of days and check whether they clicked the link from the email to the course, and if they did not, we send another email. Any scenario consists of several sequential triggers, so if you are not sure what exactly you need (a trigger or a scenario), start with a trigger.
Please note! It is impossible to build automation based on events that have not occurred. For example, you want to send an email to all students 5 days before the course ends. Choosing course completion as the event would be incorrect, since you want to perform the action BEFORE the event itself occurs (completion). In this case, you should specify Course access opened as the event and set a delay in days for when you want to send the notification (for example, access to the course is provided for 1 month, and the notification should be sent 25 days after access is opened). If you are not sure which event to choose to automate your process, contact platform support.
List of events
CRM
Contacts
Added - a contact was added to your project: registered independently or was added via import or manual addition.
Blocked - the contact is blocked. Blocking a contact means that this client will not be able to view any of your courses, even if they previously paid for access to a course or bootcamp.
Unblocked - the contact was unblocked.
Deleted - deletion of a contact from your CRM. A contact can be deleted by the owner or any team member with the appropriate access.
Resubscribed to campaigns - in development; currently, the contact cannot resubscribe to campaigns on their own.
Unsubscribed from campaigns - The contact unsubscribed from campaigns; a client can do this by clicking the Unsubscribe button in emails they receive from the platform and other campaigns.
Field value entered - in development (currently unavailable for selection)
Field value changed - select which field should be tracked (for example, phone number). Then you can choose whether it can be any value - in that case, the event will trigger any time the client changes this field or fills it in for the first time. Or it can be a specific value, for example, if you are conducting a survey during registration, this will allow you to segment the audience right away.
Field deleted - in development (currently unavailable for selection)
Field added - in development (currently unavailable for selection)
Tag removed from contact - removal of any tag from the contact or of a specific tag. You can select 1 or more tags; in that case, the event will occur if one of the selected tags is removed from the contact (Tag1 or Tag2 or Tag3, etc.).
Tag added to contact - adding any tag to the contact or a specific tag. You can select 1 or more tags; in that case, the event will occur when any of the selected tags is added to the contact (Tag1 or Tag2 or Tag3, etc.).
Communication channel status changed - in development; currently there is only 1 communication channel – email address. It cannot be changed yet.
Duplicate - the event triggers if a contact is created in the account with a phone number that was previously specified for another contact in the same account. The check happens at the moment the contact is created! If the client changes their phone number in the profile after registration or adds it later, the event will not trigger.
Contact list
Added to list - You can specify a particular list whose contact additions should be tracked. You can add a contact to a list using another trigger and the “Add to list” action in it, or by specifying a segmented list. It is not possible to edit a static list, so please keep this in mind when using this event.
Sales
General
Subscription closed - A subscription is considered closed if it was canceled by the client in their account, a scheduled payment failed, or the subscription ended, i.e. all scheduled payments under it were completed (for example, 12 subscription payments were scheduled and all were paid). Please note that canceling a subscription in the payment system by the client or in your payment system account is not transmitted to Kwiga and will not trigger this event.
Subscription renewed - the event triggers when the client makes a scheduled subscription payment, meaning it is renewed (most often for 1 month).
Subscription canceled by participant - the client canceled the subscription in their account. Please note that canceling a subscription in the payment system by the client or in your payment system account is not transmitted to Kwiga and will not trigger this event.
Offers
Successful offer payment - the offer was marked as paid. This can be either a successful payment by the client for the offer through the payment system, or manually adding a participant to a course or another product where you select “Mark as paid” and choose the offer.
Unsuccessful offer payment - the client attempted to pay for the offer, but the charge was unsuccessful, or the participant was added a product and the offer was marked as “unpaid”. You can see why the charge was unsuccessful in the transaction report, where the reason provided by the payment system is shown next to the transaction status, or in your payment system account. If the client did not pay for the offer (that is, did not enter their card details and did not click the pay button), then this event will not be triggered.
Offer payment refund - A refund was made for the offer; you can initiate a refund in the payment system in your account, or the client made a chargeback themselves.
Free offer accepted - the client accepted a free offer (registered for a free product).
Order
Unpaid order (request) - When a client opens the offer page, an order is created for them. This order will always remain unpaid immediately after creation, since going to the payment system and entering the card number takes time. Therefore, a delay is required for such an event - this is the time during which you expect the client to make a payment (for example, 15 minutes). In the list, you can choose which offer's order payment should be tracked, or specify any. If you want to track clients, who register, follow the link, but do not pay (that is, they do not enter card details and do not click the pay button), then use the order for this.
Products
General
Product access opened - You need to select the required product for which access opening should be tracked. As a rule, the product opening is set in the offer (content access date) and may either coincide with the payment date or be delayed until a future date. Also, if you add a product and select full access, then the moment the product is added will be the moment access is opened.
Product access closed - You need to select the required product for which access closing should be tracked. Access may be closed if access to the course (bootcamp or another product) has expired; as a rule, this date is configured in the offer (product access closing date), after which the student will not be able to open the course lessons. This event also tracks product removal from a contact, since this action makes the product unavailable to the client.
Course
Lesson access opened - You need to select the course and lesson for which access opening should be tracked. Access to a lesson opens when access to the course is granted, or when a time delay elapses, or when the student passes checkpoints restricting access to a specific lesson.
Started watching the lesson - The beginning of lesson viewing is considered to be opening the lesson page. This event will be triggered immediately when the lesson page loads, regardless of whether the student started watching the video, listening to the audio, etc.
Lesson viewed - The student watched all videos to at least 80% and listened to all audio to at least 80% that were added to the lesson. If the lesson does not contain video or audio materials, then for the lesson to be counted as viewed, the student needs to open the lesson and remain on the page for at least 4 seconds. Completing quizzes and assignments in the lesson does not affect whether this event is triggered.
All practice in the lesson completed - All quizzes added to the lesson have moved to the Completed status. You need to select the lesson for which practice completion should be tracked.
Course completed - a course is considered completed when all lessons have been viewed and all practices have been completed. Please note: if not all lessons in the course are available to the student, but only some of them, then this event will never occur.
Access frozen - the student's access to the course was frozen; this can be done in the course participants tab or in the contact card.
Access extended - the student's access was extended by adding additional access time or by changing the course end date.
Last course activity - You can specify the number of days that have passed since the student's last activity in the course in the value field, i.e. if you want to track students and send reminders to those who have not visited the course for 5 days, then enter 5 in the value field. Please note, the last activity check runs once a day at 3 AM Kyiv time, take this time into account when creating an action and checking conditions. Therefore, this event is triggered once a day and the check is performed at 3 AM Kyiv time.
Bootcamp
Stage access opened - You need to select the bootcamp and stage for which access opening should be tracked. Access to a stage opens when access to the bootcamp is granted, or when a time delay elapses, or when the student passes checkpoints restricting access to a specific stage.
Stage completed - the student watched all videos to at least 80% and listened to all audio to at least 80% that were added to the stage. If the stage does not contain video or audio materials, then for the stage to be counted as viewed, the student needs to open the stage and remain on the page for at least 4 seconds. Completing quizzes and assignments in the stage does not affect whether this event is triggered.
Bootcamp completed - a bootcamp is considered completed when all stages are completed and all practices are done. Please note: if not all lessons in the bootcamp are available to the student, but only some of them, then this event will never occur.
Bootcamp not completed - the student did not complete the bootcamp, i.e. was excluded due to not completing assignments.
Access frozen - the student's access to the bootcamp was frozen; this can be done in the bootcamp participants tab or in the contact card.
Access extended - the student's access was extended by adding additional access time or by changing the bootcamp end date.
Webinar
Registered for the webinar - the client registered for the webinar by filling out the registration form or by paying for participation in the webinar.
Started watching the webinar - the client joined the webinar when the broadcast was live.
Watched the webinar - the client watched the webinar, i.e. watched 85% of the total webinar duration.
Automated webinar
Registered for the automated webinar - the client registered for the automated webinar by filling out the registration form or by paying for participation in the automated webinar.
Started watching the automated webinar - the client joined the automated webinar when the broadcast was live.
Watched the automated webinar - attended the automated webinar and stayed for 85% of the time.
Consultation
Consultation start time - in development (not yet available for selection)
Consultation end time - in development (not yet available for selection)
Quiz
Quiz moved to status - lets you track the quiz status across different products. You can select a course (bootcamp), lesson, and specify the required practice whose status should be tracked. You can choose one or several quizzes; in that case, the transition to the specified status of any of the selected quizzes will be tracked. If you specify several statuses, one of them will be tracked.
Marketing
Email newsletter service
Email sent - specify any email or a specific email by selecting the required template. As soon as the selected template is sent, the event will trigger.
Link clicked in email - lets you select a template and the link whose click should be tracked. Please note
Email opened - the client received and opened the email, lets you select a specific email or any email.
System
Email received - in development (not yet available for selection)
Website
General
Visited page - lets you specify a product and track whether the student visited the product presentation page. The address of this page can be found in the course settings. If you specify more than one product, the event will trigger if the client opens one of them.
CTA
General
Clicked banner - in development (not yet available for selection)
Gamification
General
Points added - track the event of points being added across the entire project (i.e. without linking to a product) or for a specific course or bootcamp.
Points deducted - track the event of points being deducted across the entire project (i.e. without linking to a product) or for a specific course or bootcamp.
Payment with points - you can track the moment when a client pays with points for any product or a specific offer.
Conditions and delays before checking the condition
You can add additional conditions, which will start being checked after the event is triggered. Possible options:
-
Wait for some time and check the condition
-
Wait until a specific date or a specific day of the week, and then check the condition
-
Wait for another event to occur (the list includes the same events described in the Event list above)
-
Without delay, check whether the conditions are met immediately after the event occurs.
You can create any conditions using the logical operators AND and OR.
Condition list
CRM
Contacts
Status - lets you select one of the contact statuses: Active, Blocked, or Deleted. If you need to select 2 statuses, use the OR operator
Field value - lets you specify any field on the contact, including a custom field, as well as set an exact match or a phrase to check for a match.
Subscribed to newsletter - lets you check whether the contact is subscribed to the newsletter or has unsubscribed from mailings.
Tag - lets you check whether a contact has a specific tag or not. You can also specify a partial match.
Communication channel - for now, it only lets you select email and specify a possible status (Pending verification, unconfirmed; Valid, unconfirmed; Invalid; Confirmed; Spam; Complaint).
Contact added date - lets you check the date the contact was added to the account. Available options: Doesn't matter, Before date, After date, Exact date. When specifying a date, you can also specify the time and time zone.
Last activity - lets you check the date of the contact's last activity in the account. Available options: Doesn't matter, Before date, After date, Exact date. When specifying a date, you can also specify the time and time zone.
Last purchase - lets you check the date of the contact's last purchase in the account. Available options: Doesn't matter, Before date, After date, Exact date. When specifying a date, you can also specify the time and time zone. Any payment is considered a purchase.
Contact list
Is in list - lets you check whether the contact is in the list or not.
Sales
General
Subscription closed - lets you check whether a contact's subscription is closed. A subscription is considered closed if it was canceled by the client in their account, if a scheduled payment failed, or if the subscription ended, i.e. all scheduled payments for it were completed (for example, 12 subscription payments were scheduled and all were paid). Please note that canceling a subscription in the payment system by the client or in your payment system account is not transmitted to Kwiga, which means this condition may work incorrectly in such situations.
Last subscription renewal - lets you select an offer and specify the subscription renewal period.
Subscription closed - A subscription is considered closed if it was canceled by the client in their account, if a scheduled payment failed, or if the subscription ended, i.e. all scheduled payments for it were completed (for example, 12 subscription payments were scheduled and all were paid). Please note that canceling a subscription in the payment system by the client or in your payment system account is not transmitted to Kwiga and will not trigger this event.
Subscription renewed - the condition checks whether a renewal took place, i.e. whether the client made a scheduled subscription payment. You can select the period when the renewal should have occurred.
Offers
Paid for offer - checks whether there was a payment (or not) for a specific offer. Possible options:
- Yes - the user paid for the selected offer.
- No - did not visit the purchase page - the user did not visit either the offer page or the order page, and did not try to sign in or pay. If you want to select only users from your contact database who showed no interest at all in purchasing this offer, use this option.
- No - without payment attempt (order created) - the user started placing an order but did not proceed to the payment system to pay.
- No - with payment attempt - the user proceeded to the payment system to pay, but did not complete the payment or the payment was unsuccessful.
Accepted a free offer - checks whether the client accepted a free offer.
Refund for an offer - checks whether a refund was made for the offer. You can initiate a refund in the payment system in your account, or the client may have made a chargeback themselves.
Products
General
Product access - lets you check whether there is access to the product and what kind exactly (Open, Closed, Pre-registration, or None). Open means that at the moment the condition is checked, the student will have access to the product; Closed means that access to the product has ended, but it existed previously. Pre-registration means the client did not have access to the product but was on the pre-registration list, and None means the client had no access at all to the product. Additionally, you can specify a time frame for the event time in the condition, i.e. the date when access to the product was opened or closed, or when the client was added to the pre-registration list.
Quiz
Practice completed - lets you check the status of a specific practice. Additionally, you can specify a time frame for the event time in the condition, i.e. when the practice status was changed. If you select several practices, the corresponding status will be checked with OR, which means that if at least one selected practice has the selected status, the condition will be counted as met.
Course
Lesson access open - checks whether access to the lesson is open or closed. If several lessons are selected, it is enough that access is available to one of them (or that access to one of them was closed).
Started watching the lesson - checks whether the student started watching the lesson or not. If several lessons are selected, it is enough that the student started watching one of them.
Watched the lesson - checks whether the lesson was watched by the student or not. A lesson is considered watched if the student watched all videos to at least 80% and listened to all audio files added to the lesson to at least 80%. If the lesson does not contain video or audio materials, then for the lesson to be considered watched, the student must open the lesson and stay on the page for at least 4 seconds. Completing quizzes and assignments in the lesson does not affect this condition.
If several lessons are selected, it is enough that the student watched one of them (or that at least one of them was unwatched).
All practice in the lesson completed - checks whether all assignments (quizzes) in the lesson have been completed or not. If several lessons are selected, it is enough that the student completed all practices in at least one of them (or that in at least one of them they were not completed, if the condition is set to “No”).
Course completed - checks whether the student completed the course or not. A course is considered completed when all lessons have been watched and all practices have been completed. Please note that if not all lessons in the course are available to the student, but only some of them, this condition will never be met (if the “Yes” condition is selected).
Access frozen - checks whether the student's access to the course is frozen or not.
Access extended - checks whether access to the course was extended or not.
Freeze ends - lets you check whether the freeze for the course will end or not. You can specify the condition date in the event, i.e. when the freeze will end (before date, after date, exact date, or not important).
Days left on the product - lets you check whether the student still has a certain number of days of access to the product left. You can specify a range of days or an exact number (enter the same number in the from and to fields).
Progress of completion - lets you specify the % of course completion. You can set an interval (from 50% to 70%) by adding two conditions (more than 50% AND less than 70%).
Bootcamp
Stage access open - checks whether access to the stage is open or closed. If several stages are selected, it is enough that access is available to one of them (or that access to one of them was closed).
Stage completed - checks whether the stage was viewed by the student or not. A stage is considered completed if the student watched all videos to at least 80% and listened to all audio files added to the stage to at least 80%. If the stage does not contain video or audio materials, then for the stage to be considered viewed, the student must open the stage and stay on the page for at least 4 seconds. Completing quizzes and assignments in the stage does not affect this condition.
Bootcamp completed - similar to the same condition in a course.
Access frozen - similar to the same condition in a course.
Access extended - similar to the same condition in a course.
Freeze ends - similar to the same condition in a course.
Webinar
Registered for the webinar - checks whether the user is registered for the webinar or not.
Started watching the webinar - allows you to check whether the user has started watching the webinar. Make sure the condition is checked after the webinar starts.
Watched the webinar - allows you to check whether the participant attended the webinar and was present for at least 85% of the webinar. Make sure you check the condition after the webinar ends.
Automated webinar
Registered for an automated webinar - checks whether the user is registered for the automated webinar or not.
Started watching the automated webinar - allows you to check whether the user has started watching the automated webinar. Make sure the condition is checked after the automated webinar starts. In the case of a recurring automated webinar, the delay must match or exceed the recurrence period.
Watched the automated webinar - allows you to check whether the participant attended the automated webinar and was present for at least 85% of the automated webinar.
Marketing
Email service
Email sent - checks whether an email was sent to the participant (specify the required template).
Email viewed - allows you to check whether the participant opened the email. Opening (viewing) an email does not mean that the email was read, it only means that the participant loaded the email.
Clicked a link in the email - allows you to check whether the participant clicked a link in the email or not. If the email contains several links, you will be able to choose which one exactly. Please note that correct click tracking is only possible for links to KWIGA.
Website
General
Visited the page - allows you to track whether the student visited the product presentation page. The address of this page can be found in the course settings. If you specify more than one product, visiting the page of any one of the products will be enough (OR).
CTA
General
Clicked the banner - makes it possible to check whether the banner was clicked or the form was filled out.
Gamification
General
Points earned - allows you to check whether the student has earned the required number of points or not. Available options: =, <, >, >=, <=, as well as checking the number of points for a specific product or for the project.
Actions and delays before an action
The purpose of automation is to perform actions for you. It is in the Actions section that you can specify exactly what needs to be done. You can specify either one action or several. Additionally, you can specify a delay before the action is performed.
Please note! The delay before an action is calculated from the moment the condition is checked (executed). That is, if you specified a delay before the condition of 2 days, and additionally a delay before the event of 3 days, then the action will be performed 5 days after the event occurs).
A delay before an action is optional, you can choose:
-
Wait X days Y hours Z minutes
-
Continue on a specific day of the week
-
Continue at a specific time
-
Wait for the event to occur
Action list
CRM
Contacts
Block - blocks the contact. Blocking a contact means that this client will not be able to view any of your courses, even if they previously paid for access to a course or bootcamp.
Unblock - соответственно removes the block from the contact.
Temporarily delete contact - not available for selection, in development.
Restore contact - not available for selection, in development.
Unsubscribe contact from mailing list
Change field values - allows you to select a field on the contact and update its value.
Delete field - not available for selection, in development.
Add field - not available for selection, in development.
Add tag - adds a tag to the contact. You can choose from existing tags or create a new one.
Delete tag – deletes the tag on the contact.
Add contact to pipeline – lets you select a pipeline and a stage in the pipeline. A new order is created in the pipeline for the contact, i.e. an existing one is not used; a new one is created instead. If you do not want duplicate orders, then use the action Sales - Orders - Add to pipeline instead.
Contact list
Add to list – lets you select a list and add the contact to it. In this list, you can choose either a static list or a segment.
Remove from list – removes the contact from the specified list.
Sales
Orders
Add to pipeline – moves the order to the specified pipeline.
General
Cancel subscription – lets you stop subscription charges if the subscription is implemented through KWIGA. If the charge is processed in the payment system, you will not be able to stop money withdrawals through this action.
Products
General
Grant access to product – full access or offer-based access to the product is opened. Full access means access will be granted to all lessons at once, is not limited in time, and checkpoints are not applied.
Close access to product – access to the product is terminated; the student will no longer be able to open the course, view lessons , etc.
Course
Open access to lesson – opens access to the selected lessons.
Started watching lesson – simulates the start of a student's lesson viewing; the lesson is marked as in progress.
Lesson viewed – the specified lesson is marked as completed, regardless of the student's actual progress.
Course completed – marks the course as completed, regardless of the student's actual progress.
Freeze access to course – freezes access to the course for the specified number of days and months.
Extend access to course – extends access to the course for the specified number of days and months.
Issue certificate – a certificate is issued for completing the course or simply on its own. The certificate is issued regardless of the course settings.
Bootcamp
Actions in the bootcamp are similar to the corresponding actions in the course.
Open access to bootcamp stage –
Bootcamp stage completed
Bootcamp completed
Bootcamp not completed
Freeze access to bootcamp
Extend access to bootcamp
Issue certificate
Webinar
Registered for webinar – registers the student for the selected webinar.
Started watching webinar – marks that the client started watching the webinar (simulates a real event).
Watched webinar – marks the webinar as viewed.
Automated webinar
Actions in the automated webinar are similar to the corresponding actions in the webinar.
Register for automated webinar
Started watching automated webinar
Watched automated webinar
Marketing
Email marketing service
Send email - sends the selected template.
Services
Get Response
Transfer contact - transfers contact data to the Get Response service
Smart Sender
Transfer contact - transfers contact data to the Smart Sender service
SendPulse
Transfer contact - transfers contact data to the SendPulse service
Gamification
General
Award points - lets you award the specified number of points for a course or project.
Deduct points - lets you deduct the specified number of points for a course or project.
System
Notifications
Send to contact - sends a bell notification to the contact who entered the automation.
Sent to user - lets you select a user from your project team and add a notification for him/her. The notification will be available to the user in the bell.
Email sent to user - lets you select a user from your project team and send an email message.
Webhook
Send data - lets you create a webhook and send a request to the specified address.
Automation examples:
Follow-up email sequences (unpaid orders and applications)
Awarding points for completing lessons
Setting up reminders if a student does not visit the platform
Didn't find the answer? Contact the support service via online chat or Telegram