SYSTEMS AND METHODS FOR COORDINATING PROCESSING OF NOTIFICATIONS FROM DIFFERENT SOURCES AND IMPLEMENTING OF WORKFLOWS

1 . A multi-tenant system, comprising:

one or more hardware processors; and

memory storing computer instructions, the computer instructions when executed by the one or more hardware processors configured to perform:

storing product information in one or more databases, the product information defining subscription products available to subscribers of a tenant of the multi-tenant system and sources where subscriptions to the subscription products are available;

storing subscription information in the one or more databases, the subscription information including subscriber identifiers, a tenant identifier, and subscription statuses of the subscription products;

ingesting, from the sources, event notifications of subscription updates to the subscription information, the event notifications indicating update types of the subscription updates;

filtering the event notifications based on the update types;

validating respective sources of the event notifications;

reformatting the event notifications to a standardized format;

generating messages corresponding to each of the reformatted, filtered and validated event notifications;

storing the messages within a data structure;

mapping the messages to respective workflows based on the update types; and

implementing the workflows.

2 . The multi-tenant system of claim 1 , wherein at least a subset of the workflows comprise transmitting a webhook to an external system.

3 . The multi-tenant system of claim 1 , wherein the computer instructions when executed by the one or more hardware processors are further configured to perform:

generating and transmitting, to the tenant, a synchronized view of the subscription statuses of the subscription products across the sources; and wherein:

the workflows comprise updating fields within the synchronized view corresponding to the event notifications.

4 . The multi-tenant system of claim 3 , wherein the computer instructions when executed by the one or more hardware processors are further configured to perform:

monitoring workflow statuses, wherein the workflow statuses indicate whether a workflow is pending, processing, completed, or has failed.

5 . The multi-tenant system of claim 4 , wherein the computer instructions when executed by the one or more hardware processors are further configured to perform:

in addition to storing the messages within the data structure, storing, within the one or more databases, the messages;

in response to a workflow status indicating that a first workflow corresponding to a first subscription product has failed, transmitting, to the tenant, an indication of the failed first workflow;

receiving, from the tenant, an indication of an update to the product information;

updating the product information according to the indication;

implementing the first workflow according to the first message and the updated product information.

6 . The multi-tenant system of claim 1 , wherein the filtering comprises filtering out any event notifications in which the corresponding update types are unmapped to any workflows.

7 . The multi-tenant system of claim 1 , wherein:

the event notifications comprise first event notifications from a first source and second event notifications from a second source; and

the first event notifications comprise a first format and the second event notifications comprise a second format; and

the reformatting comprises converting, into the standardized format, the first event notifications and the second event notifications.

8 . The multi-tenant system of claim 7 , wherein:

the ingesting of the event notifications comprises ingesting the first event notifications into a first gateway and ingesting the second event notifications into a second gateway.

9 . The multi-tenant system of claim 1 , wherein the data structure comprises a queue.

10 . The multi-tenant system of claim 1 , wherein the event notifications comprise changes in the subscription statuses; and the messages indicate the tenant identifier and the update types.

11 . A method implemented by a multi-tenant system, the method comprising:

storing product information in one or more databases, the product information defining subscription products available to subscribers of a tenant of the multi-tenant system and sources where subscriptions to the subscription products are available;

storing subscription information in the one or more databases, the subscription information including subscriber identifiers, a tenant identifier, and subscription statuses of the subscription products;

ingesting, from the sources, event notifications of subscription updates to the subscription information, the event notifications indicating update types of the subscription updates;

filtering the event notifications based on the update types;

validating respective sources of the event notifications;

reformatting the event notifications to a standardized format;

generating messages corresponding to each of the reformatted, filtered and validated event notifications;

storing the messages within a data structure;

mapping the messages to respective workflows based on the update types; and

implementing the workflows.

12 . The method of claim 11 , wherein at least a subset of the workflows comprise transmitting a webhook to an external system.

13 . The method of claim 11 , further comprising:

generating and transmitting, to the tenant, a synchronized view of the subscription statuses of the subscription products across the sources; and wherein:

the workflows comprise updating fields within the synchronized view corresponding to the event notifications.

14 . The method of claim 13 , further comprising:

monitoring workflow statuses, wherein the workflow statuses indicate whether a workflow is pending, processing, completed, or has failed.

15 . The method of claim 14 , further comprising:

in addition to storing the messages within the data structure, storing, within the one or more databases, the messages;

in response to a workflow status indicating that a first workflow corresponding to a first subscription product has failed, transmitting, to the tenant, an indication of the failed first workflow;

receiving, from the tenant, an indication of an update to the product information;

updating the product information according to the indication;

implementing the first workflow according to the first message and the updated product information.

16 . The method of claim 11 , wherein the filtering comprises filtering out any event notifications in which the corresponding update types are unmapped to any workflows.

17 . The method of claim 11 , wherein:

the event notifications comprise first event notifications from a first source and second event notifications from a second source; and

the first event notifications comprise a first format and the second event notifications comprise a second format; and

the reformatting comprises converting, into the standardized format, the first event notifications and the second event notifications.

18 . The method of claim 17 , wherein:

the ingesting of the event notifications comprises ingesting the first event notifications into a first gateway and ingesting the second event notifications into a second gateway.

19 . The method of claim 11 , wherein the data structure comprises a queue.

20 . The method of claim 11 , wherein the event notifications comprise changes in the subscription statuses; and the messages indicate the tenant identifier and the update types.