How to model and manage non-user entities (teams/projects) with Objects.
type
, grouping similar objects together. Objects are uniquely identified by an {id, object_type}
pair in all API calls. Follow these conventions when defining object types and IDs:
Creating objects in a separate API call before trigger
Adding objects inline in workflow trigger
customer
object with associated team
objects subscriber to customer
object and team members
are subscribed to their respective team
objects. Now, when you trigger workflow on the customer object as recipient, it will propagate through this hierarchy and all teams and their team members will be notified.recipient.subscription
namespace.
:object_type/:id
instead of :distinct_id
.
Refer all object APIs