Salesforce connection add on for Heroku

[vivekvj01]

Required Terms

• I agree to follow this project's Code of Conduct
• I have read and accept the Salesforce Program Agreement

What service(s) is this request for?

Add ons

Tell us about what you're trying to solve. What challenges are you facing?

The Salesforce add-on aims to provide customers with an effortless and reliable connection to Salesforce CRM, based on industry standards. This quick add-on solution addresses the recurring need for a simple and durable integration between Salesforce and Heroku. It focuses on implementing industry-leading security practices, ensuring a secure and efficient connection between the two platforms.

[afawcett]

In the EOL announcement of Salesforce Functions we have referenced this roadmap item, which is presently in active researching and solution prototyping phase.

As head of product for Heroku I wanted to share a little more background to this roadmap item and motivation. That being that much of what has been created and developed for Salesforce Functions and is powered internally by Heroku, will shift into this upcoming Heroku experience. This includes the Kubernetes runtime resurfacing through a Heroku Dyno experience with scale to zero compute as an option. And also the much valued ability to have the platform manage authentication for your code and of course the SDK experience will also be carried forward.

So in due course as we progress this Heroku Add-on and deliver it within the Heroku DX, it will eventually allow customers to experience the full power of Heroku while still enabling them to extend Salesforce workloads as they have done so far with Salesforce Functions.

Please share your thoughts here as to what you want to see from a Heroku Add-on that extends the same flexibility of Heroku Connect into the world of compute and borrows much of what we learnt and customers valued from Salesforce Functions.

[kev4ev]

I would love to see the new Functions experience support the full npm registry (I don't believe the sunset product did). Security concerns, obviously, but perhaps they could be mitigated by something like respect for Remote Site Settings in the authorized org, etc.

Looking forward to hearing more, thanks!