Travis Cucore
Software Engineer | Technologist
Have you ever looked at Salesforce Platform Events and thought they seemed like a very locked-down, under-featured, pub/sub pattern. That's because that's exactly what it is. It's great for moving data around Salesforce, but not so much if you need something to integrate with another platform. In this post, we'll dig into a different way of achieving the same functionality for almost, if not nothing at all using the MQTT protocol, AWS Lambda (to bad Salesforce functions are being sunset), AWS IoT Core, NodeJS, and Apex.
Ah, the lowly ContactMe form. A staple for any website. I'm on a mission to prove integrating with Salesforce doesn't have to be hard, and I'm starting with this low-hanging fruit. In this post, I'll briefly describe how I used the Salesforce CRUD API and added a Node API to my website to hide the details of implementation from the end-users browser. Stop using back-door integration strategies like email-to-case for anything but... email-to-case.
I put this test post together when I was still heavily developing the blog page template. It's been unpublished since I "completed" that work, but I thought why not publish it for others to use as a reference. I hope you find it useful.
Have you ever looked at Salesforce Platform Events and thought they seemed like a very locked-down, under-featured, pub/sub pattern. That's because that's exactly what it is. It's great for moving data around Salesforce, but not so much if you need something to integrate with another platform. In this post, we'll dig into a different way of achieving the same functionality for almost, if not nothing at all using the MQTT protocol, AWS Lambda (to bad Salesforce functions are being sunset), AWS IoT Core, NodeJS, and Apex.
Ah, the lowly ContactMe form. A staple for any website. I'm on a mission to prove integrating with Salesforce doesn't have to be hard, and I'm starting with this low-hanging fruit. In this post, I'll briefly describe how I used the Salesforce CRUD API and added a Node API to my website to hide the details of implementation from the end-users browser. Stop using back-door integration strategies like email-to-case for anything but... email-to-case.
I put this test post together when I was still heavily developing the blog page template. It's been unpublished since I "completed" that work, but I thought why not publish it for others to use as a reference. I hope you find it useful.
Interested in knowing more about Travis' professional history? No problem. He's provided a very clean and succinct timeline organized by employer, then by project that clearly describes project goals along with his role and contributions to each project.
When possible, Travis likes to build working versions of things he's done. Here you'll find a library of working widgets, integrations, and other things demonstrating a small portion of Travis' skill-set.