Added demo code for AppLink

Author: afawcett

.env

@@ -0,0 +1,19 @@
+{
+  "env": {
+    "node": true,
+    "es2022": true
+  },
+  "extends": [
+    "standard-with-typescript"
+  ],
+  "parserOptions": {
+    "ecmaVersion": "latest",
+    "sourceType": "module",
+    "project": "./tsconfig.json"
+  },
+  "rules": {
+    "@typescript-eslint/semi": ["error", "always"],
+    "@typescript-eslint/strict-boolean-expressions": "off",
+    "@typescript-eslint/no-non-null-assertion": "off"
+  }
+} 

.eslintrc.json

@@ -0,0 +1,8 @@
+{
+  "semi": true,
+  "singleQuote": true,
+  "printWidth": 100,
+  "trailingComma": "es5",
+  "tabWidth": 2,
+  "useTabs": false
+} 

.prettierrc

@@ -1,66 +1,110 @@
-# node-js-getting-started
+# Heroku Integration - Salesforce API Access (Node.js)
 
-A barebones Node.js app using [Express](https://expressjs.com/).
+> **Important**: For use with the Heroku Integration and Heroku Eventing pilots only
 
-This application supports the tutorials for both the [Cedar and Fir generations](https://devcenter.heroku.com/articles/generations) of the Heroku platform. You can check them out here:
+## Architecture Overview
 
-* [Getting Started on Heroku with Node.js](https://devcenter.heroku.com/articles/getting-started-with-nodejs)
-* [Getting Started on Heroku Fir with Node.js](https://devcenter.heroku.com/articles/getting-started-with-nodejs-fir)
+This sample application showcases how to extend a Heroku web application by integrating it with Salesforce APIs, enabling seamless data exchange and automation across multiple connected Salesforce orgs. It also includes a demonstration of the Salesforce Bulk API, which is optimized for handling large data volumes efficiently.
 
-## Running Locally
+<img src="images/index.png" width="50%" alt="Index">
 
-Make sure you have [Node.js](http://nodejs.org/) and the [Heroku CLI](https://cli.heroku.com/) installed.
+## Requirements
 
-```sh
-$ git clone https://github.com/heroku/node-js-getting-started.git # or clone your own fork
-$ cd node-js-getting-started
-$ npm install
-$ npm start
+* Heroku login
+* Heroku AppLink Pilot enabled
+* Heroku CLI installed
+* Heroku AppLink Pilot CLI plugin is installed
+* Salesforce CLI installed
+* Login information for one or more Scratch, Development or Sandbox orgs
+- Watch the [Introduction to the Heroku AppLink Pilot for Developers](https://www.youtube.com/watch?v=T5kOGNuTCLE) video 
+
+## Local Development and Testing
+
+You do not need to deploy your application but you do need to configure it with Heroku.
+
+```bash
+heroku create
+heroku addons:create heroku-integration
+heroku salesforce:connect my-org --store-as-run-as-user
+heroku config:set CONNECTION_NAMES=my-org
+heroku config --shell > .env
+npm install
+npm start
 ```
 
-Your app should now be running on [localhost:5006](http://localhost:5006/).
+Navigate to `http://localhost:5006` to observe a list of accounts from the connected org.
 
-## Deploying to Heroku
+### Multiple Org Connections
 
-Using resources for this example app counts towards your usage. [Delete your app](https://devcenter.heroku.com/articles/heroku-cli-commands#heroku-apps-destroy) and [database](https://devcenter.heroku.com/articles/heroku-postgresql#removing-the-add-on) as soon as you are done experimenting to control costs.
+To access multiple Salesforce orgs, repeat the `salesforce:connect` command above with different org logins and connection names, then update the `CONNECTION_NAMES` environment variable within the `.env` file with a comma delimiated list of connection names (example shown below). The sample code will automatically query for `Account` in each org and display the results.
 
-### Deploy on [Cedar][cedar]
+```
+CONNECTION_NAMES=my-org,my-org-sales-a
+```
 
-By default, apps use Eco dynos on [Cedar][cedar] if you are subscribed to Eco. Otherwise, it defaults to Basic dynos. The 
-Eco dynos plan is shared across all Eco dynos in your account and is recommended if you plan on deploying many small apps 
-to Heroku. Learn more about our low-cost plans [here](https://blog.heroku.com/new-low-cost-plans).
+### Bulk API Demo
 
-Eligible students can apply for platform credits through our new [Heroku for GitHub Students program](https://blog.heroku.com/github-student-developer-program).
+This sample includes a demonstration of using the Salesforce Bulk API using connections formed with the Heroku Integration add-on. To see this in action obtain an org that is empty or that you are using for testing purposes only. Repeat the `salesforce:connect` command above using the connection name `empty-org` and then update the `CONNECTION_NAMES` environment variable within `.env` with a comma delimiated list of connection names (example shown above).
+
+When you visit the `/bulk-demo` endpoint, the application will check for existing bulk-loaded records. If none are found, it will start an asynchronous bulk load process. You will see output in the console similar to this:
 
 ```
-$ heroku create
-$ git push heroku main
-$ heroku open
+Starting Bulk API process for 'empty-org'
+Bulk job status: {
+  id: '750xx00000GtITrXXX',
+  state: 'Queued',
+  numberRecordsProcessed: 0,
+  numberRecordsFailed: 0
+}
+Bulk job status: {
+  id: '750xx00000GtITrXXX',
+  state: 'InProgress',
+  numberRecordsProcessed: 500,
+  numberRecordsFailed: 0
+}
+Bulk job status: {
+  id: '750xx00000GtITrXXX',
+  state: 'JobComplete',
+  numberRecordsProcessed: 1000,
+  numberRecordsFailed: 0
+}
+Job completed successfully. Processed 1000 records
 ```
 
-### Deploy on [Fir][fir]
+Once the processing has completed, refresh the home page to observe the records that have been bulk loaded. Note that to avoid duplicate inserts, the sample code checks if prior bulk inserts have been run before starting a new job.
 
-By default, apps on [Fir][fir] use 1X-Classic dynos. To create an app on [Fir][fir] you'll need to 
-[create a private space](https://devcenter.heroku.com/articles/working-with-private-spaces#create-a-private-space)
-first.
+To reset the Bulk API demo and remove the test records, run the following command using the Salesforce CLI (assuming `empty-org` is also a known `sf` CLI authorized org alias):
 
+```bash
+echo "delete [SELECT Id FROM Account WHERE Name LIKE 'Bulk Account%'];" | sf apex run -o empty-org
 ```
-$ heroku spaces:create <space-name> --team <team-name> --generation fir
-$ heroku create --space <space-name>
-$ git push heroku main
-$ heroku open
+
+## Deploy to Heroku
+
+```bash
+heroku create
+heroku addons:create heroku-integration
+heroku salesforce:connect my-org --store-as-run-as-user
+heroku config:set CONNECTION_NAMES=my-org
+git push heroku main
+heroku open
 ```
 
-## Documentation
+To access multiple Salesforce orgs, repeat the `salesforce:connect` command above with different org logins and connection names, then update the `CONNECTION_NAMES` with a comma delimiated list of connection names. The sample code will automatically query for `Account` in each org and display the results.
+
+## Technical Information
 
-For more information about using Node.js on Heroku, see these Dev Center articles:
+* Salesforce APIs are always accessed in the context of the authenticated user defined at the time of connection through the `--store-as-run-as-user` CLI parameter. This means that only the objects and fields the user has access to can be accessed by the code.
+* This is a Node.js Express application, using EJS to render browser content. Other client libraries and frameworks can be used of course.
+* The application uses the `@heroku/salesforce-sdk-nodejs` package to handle Salesforce connections, authentication, and API interactions including SOQL queries and Bulk API operations.
+* The sample uses a custom environment variable `CONNECTION_NAMES` to enumerate the org connections to be used by the application. However this could easily be hardcoded in your own library code, or obtained from a configuration service or other preferred means of your choice.
+* The Bulk API demo intentionally showcases real-world duplicate handling scenarios. Some records may fail to insert due to Salesforce duplicate detection rules, which demonstrates proper error handling in bulk operations. Users can either accept this as a learning opportunity about integration resilience or temporarily disable duplicate rules in their Salesforce org for testing purposes. Successfully inserted records will still be visible on the main page, regardless of any duplicate-related failures.
 
-- [Getting Started on Heroku with Node.js](https://devcenter.heroku.com/articles/getting-started-with-nodejs)
-- [Getting Started on Heroku Fir with Node.js](https://devcenter.heroku.com/articles/getting-started-with-nodejs-fir)
-- [Heroku Node.js Support](https://devcenter.heroku.com/articles/nodejs-support)
-- [Node.js on Heroku](https://devcenter.heroku.com/categories/nodejs)
-- [Best Practices for Node.js Development](https://devcenter.heroku.com/articles/node-best-practices)
-- [Using WebSockets on Heroku with Node.js](https://devcenter.heroku.com/articles/node-websockets)
+## Other Samples
 
-[cedar]: https://devcenter.heroku.com/articles/generations#cedar
-[fir]: https://devcenter.heroku.com/articles/generations#fir
+| Sample | What it covers? |
+|--------|----------------|
+| [Salesforce API Access - Node.js](https://github.com/heroku-examples/heroku-integration-pattern-api-access-nodejs) | This sample application showcases how to extend a Heroku web application by integrating it with Salesforce APIs, enabling seamless data exchange and automation across multiple connected Salesforce orgs. It also includes a demonstration of the Salesforce Bulk API, which is optimized for handling large data volumes efficiently. |
+| [Extending Apex, Flow and Agentforce - Node.js](https://github.com/heroku-examples/heroku-integration-pattern-org-action-nodejs) | This sample demonstrates importing a Heroku application into an org to enable Apex, Flow, and Agentforce to call out to Heroku. For Apex, both synchronous and asynchronous invocation are demonstrated, along with securely elevating Salesforce permissions for processing that requires additional object or field access. |
+| [Scaling Batch Jobs with Heroku - Node.js](https://github.com/heroku-examples/heroku-integration-pattern-org-job-nodejs) | This sample seamlessly delegates the processing of large amounts of data with significant compute requirements to Heroku Worker processes. |
+| [Using Eventing to drive Automation and Communication](https://github.com/heroku-examples/heroku-integration-pattern-eventing-nodejs) | This sample extends the batch job sample by adding the ability to use eventing to start the work and notify users once it completes using Custom Notifications. These notifications are sent to the user's desktop or mobile device running Salesforce Mobile. Flow is used in this sample to demonstrate how processing can be handed off to low-code tools such as Flow. |

README.md

@@ -1,7 +1,31 @@
 {
-  "name": "Start on Heroku: Node.js",
-  "description": "A barebones Node.js app using Express 4",
-  "repository": "https://github.com/heroku/node-js-getting-started",
-  "keywords": ["node", "express", "heroku"],
-  "image": "heroku/nodejs"
+  "name": "Heroku Integration - Salesforce API Access (Node.js)",
+  "description": "A sample Node.js app demonstrating Salesforce API integration using Heroku Integration Pilot",
+  "repository": "https://github.com/heroku-examples/heroku-integration-pattern-api-access-nodejs",
+  "logo": "https://cdn.rawgit.com/heroku/node-js-getting-started/main/public/node.svg",
+  "keywords": ["node", "express", "heroku", "salesforce", "integration", "api", "bulk-api"],
+  "image": "heroku/nodejs",
+  "env": {
+    "CONNECTION_NAMES": {
+      "description": "Comma-separated list of Salesforce connection names",
+      "required": true
+    }
+  },
+  "addons": [
+    {
+      "plan": "heroku-integration"
+    }
+  ],
+  "buildpacks": [
+    {
+      "url": "heroku/nodejs"
+    }
+  ],
+  "environments": {
+    "test": {
+      "scripts": {
+        "test": "npm test"
+      }
+    }
+  }
 }