Abstract: A particular option selection may be provided by an online service platform (OSP) to a client regarding one or more predefined services that the OSP can be configured to perform. These may include automatic activities option selection(s) that may trigger the OSP to automatically start one or more activities upon one or more thresholds being crossed. The OSP may apply digital rules to the dataset(s) of the client to determine whether or not to automatically start or stop activities, including producing respective resources, upon a threshold being crossed, to determine a requested resource and then push, send, or otherwise cause to be transmitted a notification regarding the produced resource or other activities.

Abstract: Techniques for restricting plug-in application recipes (“PIARs”) are disclosed. A PIAR management application receives a PIAR restriction via an authenticated user of the PIAR management application. The PIAR restriction is applicable to certain users of the PIAR management application. The PIAR restriction identifies functionality of the PIAR management application that would otherwise be available to a user of the PIAR management application if the user had an active account for a particular plug-in application that, once linked to that user in the PIAR management application and associated with a particular PIAR, would be capable of supplying at least part of the functionality. The PIAR management application stores the PIAR restriction, including information to block the restricted functionality. Based on the PIAR restriction, the PIAR management application blocks the restricted functionality. Many different types of functionality may be restricted, in various ways.

Abstract: A particular option selection may be provided by an online service platform (OSP) to a client regarding one or more predefined services that the OSP can be configured to perform. These may include automatic activities option selection(s) that may trigger the OSP to automatically start one or more activities upon one or more thresholds being crossed. The OSP may apply digital rules to the dataset(s) of the client to determine whether or not to automatically start or stop activities, including producing respective resources, upon a threshold being crossed, to determine a requested resource and then push, send, or otherwise cause to be transmitted a notification regarding the produced resource or other activities.

Abstract: Techniques for restricting plug-in application recipes (“PIARs”) are disclosed. A PIAR management application receives a PIAR restriction via an authenticated user of the PIAR management application. The PIAR restriction is applicable to certain users of the PIAR management application. The PIAR restriction identifies functionality of the PIAR management application that would otherwise be available to a user of the PIAR management application if the user had an active account for a particular plug-in application that, once linked to that user in the PIAR management application and associated with a particular PIAR, would be capable of supplying at least part of the functionality. The PIAR management application stores the PIAR restriction, including information to block the restricted functionality. Based on the PIAR restriction, the PIAR management application blocks the restricted functionality. Many different types of functionality may be restricted, in various ways.

Abstract: Techniques for restricting plug-in application recipes (“PIARs”) are disclosed. A PIAR management application receives a PIAR restriction via an authenticated user of the PIAR management application. The PIAR restriction is applicable to certain users of the PIAR management application. The PIAR restriction identifies functionality of the PIAR management application that would otherwise be available to a user of the PIAR management application if the user had an active account for a particular plug-in application that, once linked to that user in the PIAR management application and associated with a particular PIAR, would be capable of supplying at least part of the functionality. The PIAR management application stores the PIAR restriction, including information to block the restricted functionality. Based on the PIAR restriction, the PIAR management application blocks the restricted functionality. Many different types of functionality may be restricted, in various ways.

Abstract: Techniques for restricting plug-in application recipes (“PIARs”) are disclosed. A PIAR management application receives a PIAR restriction via an authenticated user of the PIAR management application. The PIAR restriction is applicable to certain users of the PIAR management application. The PIAR restriction identifies functionality of the PIAR management application that would otherwise be available to a user of the PIAR management application if the user had an active account for a particular plug-in application that, once linked to that user in the PIAR management application and associated with a particular PIAR, would be capable of supplying at least part of the functionality. The PIAR management application stores the PIAR restriction, including information to block the restricted functionality. Based on the PIAR restriction, the PIAR management application blocks the restricted functionality. Many different types of functionality may be restricted, in various ways.

Abstract: Techniques for transforming plug-in application recipe (PIAR) variables are disclosed. A PIAR definition identifies a trigger and an action. Trigger variable values, exposed by a first plug-in application, are necessary to evaluate the trigger. Evaluating the trigger involves determining whether a condition is satisfied, based on values of trigger variables. A second plug-in application exposes an interface for carrying out an action. Evaluating the action involves carrying out the action based on input variable values. A user selects, via a graphical user interface of a PIAR management application, a variable for a trigger or action operation and a transformation operation to be applied to the variable. The PIAR management application generates a PIAR definition object defining the trigger, the action, and the transformation operation, and stores the PIAR definition object for evaluation on an ongoing basis.

Abstract: Techniques for restricting plug-in application recipes (“PIARs”) are disclosed. A PIAR management application receives a PIAR restriction via an authenticated user of the PIAR management application. The PIAR restriction is applicable to certain users of the PIAR management application. The PIAR restriction identifies functionality of the PIAR management application that would otherwise be available to a user of the PIAR management application if the user had an active account for a particular plug-in application that, once linked to that user in the PIAR management application and associated with a particular PIAR, would be capable of supplying at least part of the functionality. The PIAR management application stores the PIAR restriction, including information to block the restricted functionality. Based on the PIAR restriction, the PIAR management application blocks the restricted functionality. Many different types of functionality may be restricted, in various ways.

Abstract: Techniques for transforming plug-in application recipe (PIAR) variables are disclosed. A PIAR definition identifies a trigger and an action. Trigger variable values, exposed by a first plug-in application, are necessary to evaluate the trigger. Evaluating the trigger involves determining whether a condition is satisfied, based on values of trigger variables. A second plug-in application exposes an interface for carrying out an action. Evaluating the action involves carrying out the action based on input variable values. A user selects, via a graphical user interface of a PIAR management application, a variable for a trigger or action operation and a transformation operation to be applied to the variable. The PIAR management application generates a PIAR definition object defining the trigger, the action, and the transformation operation, and stores the PIAR definition object for evaluation on an ongoing basis.

Abstract: Techniques for transforming plug-in application recipe (PIAR) variables are disclosed. A PIAR definition identifies a trigger and an action. Trigger variable values, exposed by a first plug-in application, are necessary to evaluate the trigger. Evaluating the trigger involves determining whether a condition is satisfied, based on values of trigger variables. A second plug-in application exposes an interface for carrying out an action. Evaluating the action involves carrying out the action based on input variable values. A user selects, via a graphical user interface of a PIAR management application, a variable for a trigger or action operation and a transformation operation to be applied to the variable. The PIAR management application generates a PIAR definition object defining the trigger, the action, and the transformation operation, and stores the PIAR definition object for evaluation on an ongoing basis.

Abstract: Techniques for governing access to third-party application programming interfaces (API's) are disclosed. A proxy service exposes an API configured to receive requests, from user-facing services, to perform functions of backend services. The proxy service stores a usage policy that defines a criterion that is (a) different from any authorization criterion and (b) associated with using a function of a backend service. The proxy service receives a request to perform the function of the first backend service for a user-facing service and determines that the request does not satisfy the usage policy. Based on determining that the request does not satisfy the usage policy, the proxy service refrains from accessing the backend service to perform the function responsive to the request, and transmits an alert to the user-facing service indicating that the request does not satisfy the usage policy.

Abstract: Techniques for managing a plug-in application recipe (“PIAR”) are disclosed. A mapping between (a) a user-selected field, selected via a PIAR creation interface, and (b) a third-party application field, exposed by an application programming interface (“API”) of a third-party application, is stored. The third-party application field is associated with a trigger or action of a PIAR. Managing the PIAR in an active state involves periodically receiving and checking data from the third-party application field against a PIAR condition. During or after managing the PIAR in the active state, information is stored to update the mapping to a different mapping. The different mapping maps the user-selected field to a different third-party application field. Without modifying the PIAR, managing the PIAR in the active state then involves periodically receiving and checking data from the different third-party application field against the PIAR condition.

Abstract: Techniques for transforming plug-in application recipe (PIAR) variables are disclosed. A PIAR definition identifies a trigger and an action. Trigger variable values, exposed by a first plug-in application, are necessary to evaluate the trigger. Evaluating the trigger involves determining whether a condition is satisfied, based on values of trigger variables. A second plug-in application exposes an interface for carrying out an action. Evaluating the action involves carrying out the action based on input variable values. A user selects, via a graphical user interface of a PIAR management application, a variable for a trigger or action operation and a transformation operation to be applied to the variable. The PIAR management application generates a PIAR definition object defining the trigger, the action, and the transformation operation, and stores the PIAR definition object for evaluation on an ongoing basis.

Abstract: Techniques for restricting plug-in application recipes (“PIARs”) are disclosed. A PIAR management application receives a PIAR restriction via an authenticated user of the PIAR management application. The PIAR restriction is applicable to certain users of the PIAR management application. The PIAR restriction identifies functionality of the PIAR management application that would otherwise be available to a user of the PIAR management application if the user had an active account for a particular plug-in application that, once linked to that user in the PIAR management application and associated with a particular PIAR, would be capable of supplying at least part of the functionality. The PIAR management application stores the PIAR restriction, including information to block the restricted functionality. Based on the PIAR restriction, the PIAR management application blocks the restricted functionality. Many different types of functionality may be restricted, in various ways.

Abstract: Techniques for managing a plug-in application recipe (“PIAR”) are disclosed. A mapping between (a) a user-selected field, selected via a PIAR creation interface, and (b) a third-party application field, exposed by an application programming interface (“API”) of a third-party application, is stored. The third-party application field is associated with a trigger or action of a PIAR. Managing the PIAR in an active state involves periodically receiving and checking data from the third-party application field against a PIAR condition. During or after managing the PIAR in the active state, information is stored to update the mapping to a different mapping. The different mapping maps the user-selected field to a different third-party application field. Without modifying the PIAR, managing the PIAR in the active state then involves periodically receiving and checking data from the different third-party application field against the PIAR condition.