“I’m kind of a weirdo. I love tinkering, always have.”


Rashed Talukder is a Developer Evangelist at Jive. The opening slide said he’s been with Jive for “0.685 years.” Yes, I had to use my Droid’s calculator to find out that means about eight months and change. So he’s a newbie. But if he hadn’t said that, I never would’ve guessed.


The long and the short of it is this: Simple stream integrations (SSIs) allow you to harness salient information from the outside world and introduce it into Jive without the need for a middleware service. Jive-n now runs developer code on the Jive servers thanks to the availability of webhooks and a secured signed public URL.




Rashed whipped through the technical context pretty quickly, perhaps too quickly. A few of the slides I didn’t manage to capture include one showing the required components to be the transform function (translator for params to fit required params), and the need to sample incoming JSON to verify the transform.


Then he showed the SSI add-on file structure, followed by the below slide.




Rashed made it all make sense with a use case I could relate to. Let’s say your sales org wants to know what leads are coming in without Salesforce or Marketo acting as the middleware. You could use Marketo’s webhook and then add in all the profile fields you want for a smart campaign. This creates an SSI that lets you capture all your leads in Jive.


He showed a quick video demo showing how you can enrich SSI activity with Built.io Flow. The graphical UI was very user friendly, allowing you to drag and drop icons representing such variables as Get Lead Activities and an HTTP request with the Node.js request between them.


How about beefing up that simple stream to bring you even more helpful info? Maybe you’d like to get more context about your sales leads and bring Jive yet another step closer to being a true hub of knowledge.






In the above scenario, Rashed added the lead’s Twitter feed to capture more context in Jive, such as contact info and interests, complimented by the ability to contact that lead from within Jive courtesy of handy “Call” and “Email” buttons.


He showed us what a cinch it was to use the Jive node SDK to unpack and add the app to the SSI.


SSI considerations:


•    Only for cloud

•    Transform function has 1000ms execution time

•    Data displayed is limited to external service’s payload (e.g. Marketo example, awesome though it is, is still missing info and context a seller might want before contacting a lead)

•    Unable to take direct action on the external service from generated activity because it’s a one-way push into Jive without any external calls


Finally, he went over shared auth for requests using Jive Connects. This provides a secure way for secure auth for app requests. The end user is blind to your credentials. To do this, go to admin panel→App Services. The most important field is the Service URL which is the base URL for all requests.


Rashed brought it home saying what makes the simple stream integration so simple: it takes very little time. He emphasized that he can create powerful integrations like the Marketo example in about a half-hour. “There’s not a whole lot out there that can do that,” he said.


Why SSI rocks:


•    Low investment, high ROI

•    Patternizable

•    High velocity

•    Middleware-less

•    Secure

•    Allows for quick and contextually meaningful collaboration (e.g. searchable, allows for commenting, liking, sharing, marking for action, marking as success, etc.).


Given how easy and powerful SSIs are, Rashed was a bit bummed out that hardly anyone in the audience raised their hands when he asked who out there had already given SSIs a whirl.


“SSIs are just a quick and easy way to get more meaningful info about leads all within Jive.”