View our GitHub

Please visit sails-docs on GitHub to view documentation on your mobile device.

Edit Page


Broadcast a message to all client sockets who have subscribed to the specified record of this model.

By convention, this message indicates that a new child record has been added to the specified collection association of this parent record (and that client-side sockets receiving the message should update their user interface to match). In other words, if a Tutorial model has an associated collection of "comments" (referring to records of the Comment model), then you might call Tutorial.publishAdd() to notify connected clients that a new comment has been added to the tutorial.

Something.publishAdd(id, association, added);


  • Something.publishAdd(id, association, added, socketToOmit);


Argument Type Details
1 id or The id (primary key) of the parent record.
2 association The name of the association that the child record was added to (e.g. "comments")
3 added Either a number or string to represent the id (primary key) of the child record being added, or a dictionary of properties describing it (must contain an id key!). Either way, this information will be bundled in the socket message which is broadcasted.
4 socketToOmit Optional. If provided, the client-side socket indicated by req will not receive the message blasted out to everyone else. Useful when the broadcast-worthy event is triggered by a requesting user who doesn't need to hear about it again.

When your app calls publishAdd(), a socket message is broadcasted to all sockets subscribed to the record's room (i.e. via the subscribe() resourceful pubsub method) and the model identity is used as the event name.

The socket message is an object with the following properties:

  • id - the id attribute of the parent record
  • verb - always provided as the string: "addedTo"
  • attribute - the name of the model attribute (collection association) that was added to
  • addedId - the id of the newly added child record
  • added - Not guaranteed. Will only be present if a dictionary of properties for the newly added child record was provided, rather than just its id.


// Broadcast a message to all client-side sockets subscribed to the tutorial record w/ id=3
// letting them know that a new child record with id=17 has been associated and is now one of the 
// tutorial's "comments".
Tutorial.publishAdd(3, 'comments', 17);
// Broadcast a message to all client-side sockets subscribed to the tutorial record w/ id=3
// letting them know that a new child record with the specified properties has been associated
// and is now one of the tutorial's "comments".
// (Note that we also pass in `req` to prevent the requesting socket from receiving the broadcast.)
Tutorial.publishAdd(3, 'comments', { 
  id: 17,
  message: 'I love this show!'
}, req);


  • If you are using Sails' blueprint API, this resourceful pubsub method is called automatically by built-in code within the blueprints hook in Sails core. The cleanest way to customize this, or any other behavior bundled in a blueprint API, is to override it with a custom action.
  • If you are looking for information about noReverse, see the documentation for publishUpdate. In general, you should not have to set this argument unless you are writing your own implementation of publishAdd for a model.
  • Under the covers, resourceful pubsub methods use sails.sockets.* methods. When/if you encounter a need for customization beyond what is supported out of the box in a resourceful pubsub method, you should use the methods exposed in sails.sockets.* directly.

Is something missing?

If you notice something we've missed or could be improved on, please follow this link and submit a pull request to the sails-docs repo. Once we merge it, the changes will be reflected on the website the next time it is deployed.


We wrote a book!

Get early access to the book
with promotion code: mcneildoc

Get the Book