You can use this node to dynamically remove recipient or actor from object subscription based on an event or action. If you have event-based data coming from third-party systems, you don’t need to write custom object subscription APIs in your codebase. Simply send events to SuprSend, and let the workflow handle object subscriptions. For example, when someone unsubscribes from a topic (like a tournament), you can automatically remove their subscription from the corresponding object. This ensures they receive all relevant notifications about topic-related activities without manual intervention.

​
Compute objects at runtime

You can either remove users from a pre-defined object or compute object on the fly using workflow input data. While defining object, both ID and type are mandatory. Type defines the group that object belong to (example, teams, departments). Dynamic object are defined in handlebars format as {{...}}. One common use case of creating object dynamically is when you need to compute objects based on user topic subscription. For example, there are multiple player tournaments happening and there are separate objects for each tournament. Object ID in such case can be {{tournament_id}} and type tournaments.
Object subscription will only be removed if the computed object exists, else this action will fail.

​
Subscription properties

Subscription properties are the set of variables defining relationship between a subscriber and an object. During a workflow execution, these properties can be accessed under the recipient.subscription namespace as recipient.subscription.property_key. Subscription properties are added in JSONNET format. You can read more about object subscription here.