Node.js Demo with Streaming API &

Apex Callouts and Outbound Messaging are great ways to get your data outside of for integration with external system. However, there are times when you are going to bump into Callout Limits or would like to use Outbound Messaging with non-SOAP endpoints. Never fear, for these types of situations the Streaming API comes to your rescue!

The Streaming API lets you expose a near real-time stream of data from the platform in a secure and scalable way to external applications. From the docs,

The Streaming API uses a publish/subscribe model where administrators create one or more named topics, each of which is associated with a SOQL query. Applications may subscribe to one or more topics, using the Bayeux protocol. As relevant data is updated, the platform re-evaluates the query and, when a change occurs that alters the results of the query, the platform publishes a notification to subscribed applications.

I've put together a video and demo application (see below) that walks you through the entire process. Feel free to clone the github repo and use the code for your own project. All of the instructions to setup and run the application are on the repo.

Here's an overview of the application. I setup a PushTopic in that streams newly created Account records to a Node application running on heroku using faye (a publish-subscribe messaging system based on the Bayeux protocol) to listen for new records. When a new record is received, it is written to the browser using without a page refresh (I know.... magic!!). You could use this same paradigm to send the records to an external HR system, account system or possibly email server. The sky's the limit.

Run the Demo Application

Feel free to watch the entire video at Youtube or embedded below, but here's how to run the demo yourself:

  1. Open this page in another browser window. This is a simple Node app that allows you to create a new Account record in my DE org.
  2. Open the demo app in another browser window. This page will initially be blank but as you (or anyone else) adds new Account records in the first app, they will appear on this page.

Here's a video of the entire process but you can watch it on Youtube if that's more convenient.

Like code? If so, here's the main app.js from the repo:

 * Module dependencies.
var config = require('./config.js');
var express = require('express')
 , faye  = require('faye')
 , nforce = require('nforce')
 , util = require('util')
 , routes = require('./routes');

var app = module.exports = express.createServer();

// attach and listen 
var io = require('').listen(app);
// get a reference to the socket once a client connects
var socket = io.sockets.on('connection', function (socket) { }); 

// Bayeux server - mounted at /cometd
var fayeServer = new faye.NodeAdapter({mount: '/cometd', timeout: 60 });

var sfdc = nforce.createConnection({
 clientId: config.CLIENT_ID,
 clientSecret: config.CLIENT_SECRET,
 redirectUri: config.CALLBACK_URL + '/oauth/_callback',
 apiVersion: 'v24.0', // optional, defaults to v24.0
 environment: config.ENVIRONMENT // optional, sandbox or production, production default

// Configuration
 app.set('views', __dirname + '/views');
 app.set('view engine', 'jade');
 app.use(express.static(__dirname + '/public')); 

app.configure('development', function(){
 app.use(express.errorHandler({ dumpExceptions: true, showStack: true }));

app.configure('production', function(){

// Routes
app.get('/', routes.index);

app.listen(config.PORT, function(){
 console.log("Express server listening on port %d in %s mode", app.address().port, app.settings.env);

// authenticates and returns OAuth -- used by faye
function getOAuthToken(callback) {

 if(config.DEBUG) console.log("Authenticating to get access token...");

 sfdc.authenticate({ username: config.USERNAME, password: config.PASSWORD }, function(err, resp){
  if(err) {
 console.log('Error authenticating to org: ' + err.message);
  } else {
 if(config.DEBUG) console.log('OAauth dance response: ' + util.inspect(resp));


// get the access token from to start the entire polling process
getOAuthToken(function(oauth) { 

 // cometd endpoint
 var salesforce_endpoint = oauth.instance_url +'/cometd/24.0';
 if(config.DEBUG) console.log("Creating a client for "+ salesforce_endpoint);

 // add the client listening to
 var client = new faye.Client(salesforce_endpoint);

 // set header with OAuth token
 client.setHeader('Authorization', 'OAuth '+ oauth.access_token);

 // monitor connection down and reset the header
 client.bind('transport:down', function(client) {
  // get an OAuth token again
  getOAuthToken(function(oauth) {
 // set header again
 upstreamClient.setHeader('Authorization', 'OAuth '+ oauth.access_token);

 // subscribe to push topic
 if(config.DEBUG) console.log('Subscribing to '+ config.PUSH_TOPIC);
 var upstreamSub = client.subscribe(config.PUSH_TOPIC, function(message) {
  // new inserted/updated record receeived -- do something with it
  if(config.DEBUG) console.log("Received message: " + JSON.stringify(message)); 
  socket.emit('record-processed', JSON.stringify(message));

 // log that upstream subscription is active
 client.callback(function() {
  if(config.DEBUG) console.log('Upstream subscription is now active');  

 // log that upstream subscription encounters error
 client.errback(function(error) {
  if(config.DEBUG) console.error("ERROR ON Upstream subscription Attempt: " + error.message);

 // just for debugging I/O, an extension to client -- comment out if too chatty
  outgoing: function(message, callback) {  
 if(config.DEBUG) console.log('OUT >>> '+ JSON.stringify(message));
  incoming: function(message, callback) {  
 if(config.DEBUG) console.log('IN >>>> '+ JSON.stringify(message));