Event Notifications

Overview

The Event Notifications service keeps you informed about critical events occurring on your site, triggering automated actions via webhooks, emails, SMS, and messages. It captures all system changes, including those related to customers, subscriptions, plans, and invoices.

View and Manage Events

The Event Notifications page can be accessed through Settings in your Admin Portal. It is used to hold all the events you have created on your Subsbase site.
This page enables you to manage your events, allowing you to add new ones, make changes to existing ones, and delete them as needed.

Edit Event: To edit any of your existing events, click on the arrow icon located in the respective cell, make the needed changes, and then save.

Delete Event: To delete an event notification, click on the ellipsis (...) located in the respective cell.

Add Event: To add a new event notification to your Subsbase site, click the "Add" button. You will then see a form with the following fields:

Event Name

This is just an internal name that is only shown to the Admin Portal users, which will not be shown to your customers/subscribers. However, we recommend setting up a naming convention within your company to help differentiate between your event notifications.

Trigger when

List of Events: This is a selection of specific events that can be chosen to trigger automated actions.
Configuring event notifications allows for the automation of actions whenever these selected events occur.
So, if you set up a trigger when "Subscription is renewed," an automated action will occur every time a customer renews their subscription.

It is a cause-and-effect relationship between an event and an automated action. When the specified event occurs, a predefined action is triggered, based on configured conditions and/or delays.

For example: When the Subscription is renewed, send an email to the customer.
- Trigger when: Subscription is renewed
- Action: Send an email to the customer
In this scenario, "Send Email" is the automated action that will occur when the event "Subscription is renewed" happens. Specifically, an email will be sent to the customer, with the recipient's email address being populated using the placeholder null from the list of available placeholders.

Delay

When the delay toggle is turned on, you can delay the event notifications to be sent to your customers/subscribers when needed.
This delay toggle is disabled by default.
You have three options to choose from when the delay toggle is enabled:
- After: Select the number of day(s), week(s), month(s), or year(s) to specify the duration after which the notification will be sent.
- Specific Date: Select the calendar day of the month, to specify the notification date.
- Day of week: Select from Sunday to Saturday to specify the notification day.

Conditions

This is an additional option that you can use for filtering, where you can configure complex event notifications that only match events under very specific conditions.
Event Notifications whose attributes match a condition will trigger action(s). Notifications whose attributes do not match a condition will not.

Action(s) taken

An action happens as a result of a trigger; it is a response from a triggered event.
You can select as many actions as you want to be taken when the event is triggered.
There are four available actions: Trigger Webhook, Send Email, Send SMS and Send Message.

Trigger Webhook

Webhooks are automated event-driven messages sent from one system to another.
Every time a specified event takes place, the webhook immediately sends a payload to a specified URL. To be able to receive the payload, you must add an endpoint.
You can customize the approach you want to use from the request method.
You can customize the webhooks payload using placeholders.

Send Email

Applicable when email or SMTP integration is available.

Each email notification configuration is treated as a template to be used to formulate the final email that is going to be sent.
During that process, all placeholders are replaced with the actual values. The available placeholders depend on the kind of event being triggered.
Provided below is a list of events along with the different Available Placeholders.

Placeholders could be used in any of the fields.
Email bodies could be HTML.