# Salesforce Notifier

- Updated on Nov 6, 2025
- Published on Mar 18, 2025

- 6 minute(s) read

> **Accessing this feature**  
> Your access to the feature described in this article depends on your license package and pricing plan.  
> To learn which features are available to your organization and how to add more, contact your Hyperscience representative.

With the Salesforce Notifier Block, you can configure your flow to send extracted information to Salesforce.

The Salesforce Notifier Block can use extracted information to look up, and then update any number of fields on a Salesforce object.

The Salesforce Notifier Block is available in both SaaS and on-premise versions of the Hyperscience application.

## Sample use cases

- Storing extracted information from other sources on a Salesforce object.
- After using the Salesforce Listener Block to extract information from a file stored on a Salesforce object, update the field data of this object in Salesforce.
- Update customer data in Salesforce based on forms from the customer.

## Block settings table

| **Name** | **Required?** | **Description** |
|-----------|----------------|-----------------|
| Routing Filter | No | To learn more about this setting, see [Universal Integration Block Settings](https://help.hyperscience.ai/v42/docs/universal-integration-block-settings). |
| Associated Username | Yes | The username associated with the Salesforce Connected App or External Client App |
| Consumer Key | Yes | The Consumer Key from the Salesforce Connected App or External Client App |
| Private Key | Yes | The key generated during the authentication-configuration process |
| Sandbox Environment | Yes | Indicates whether the connected Salesforce instance is a sandbox environment |
| Object API Name | Yes | API name of the object in Salesforce to look up and update |
| Create New Record on Lookup Failure | Yes | If enabled, Hyperscience creates a new record if the lookup fails to find a record with the given lookup parameters. If disabled, the lookup fails if it doesn’t find a record with the given lookup parameters. |
| Lookup Field Mapping | Yes | A set of key-value pairs indicating which Salesforce fields should be queried in the lookup and the extracted data that should be queried in those fields (e.g., `“DOCUMENT_FIELD_NAME”: “OBJECT_FIELD_API_NAME”`) |
| Document Field Mappings | Yes | A set of key-value pairs indicating the Salesforce fields Hyperscience should update and the extracted data they should be updated with (e.g., `“DOCUMENT_FIELD_NAME”: “OBJECT_FIELD_API_NAME”`) |
| Overwrite Existing Field Data? | Yes | If enabled and the selected field contains data, Hyperscience overwrites that data. If disabled and the selected field contains data, Hyperscience does not overwrite the existing data, and the operation fails. |

## Setting up Salesforce Notifier

### Setup within Salesforce

#### Install and set up Hyperscience Package

1. Install the Hyperscience package in the desired Salesforce org.
   - Go to the Salesforce AppExchange’s [Hyperscience Platform (opens in new tab)](https://appexchange.salesforce.com/listingDetail?listingId=a0N4V00000G6fiBUAR&preview=%222022-09-29T15%3A51%3A35.000Z%22&_ga=2.84305497.1160715746.1664388746-1251261210.1661438262&tab=e) listing.
   - Click the **Get It Now** button.
   - Enter your details and click the **Contact Me** button.  
       1. A Hyperscience representative will contact you and provide you with the Hyperscience package.
   - Once you have the Hyperscience package, install it in the desired Salesforce org.
2. Add **Hyperscience Permission Set** to users that should have access to the Hyperscience application.
3. Make sure that **Hyperscience__Supervision_Task__c** is added to **Change Data Capture Events**.
4. Enable the **Query All Files** permission.

#### Add the Hyperscience URL

1. Search your apps for “Hyperscience”. Click on the **Hyperscience** app.
2. Click on the **Core Setup** tab.
3. To edit the Hyperscience URL, click **Edit**.
4. Enter the full URL for your Hyperscience app.
5. Click **Save**.

#### Configure authentication

**Salesforce Connected App**  
1. Create the private key (`salesforce.key`) and certificate (`salesforce.crt`) by running the following command:
   
   ```bash
   openssl req -x509 -sha256 -nodes -days 36500 -newkey rsa:2048 -keyout salesforce.key -out salesforce.crt
   ```
   
2. Copy the private key to your clipboard.
   
   ```bash
   cat [private.key file] | sed 's/$/\n/' | tr -d '\n' | pbcopy
   ```

3. Paste the private key into a text file and save it. Later, you will need to paste it into your Salesforce Notifier Block within Hyperscience.
4. Create your JWT Connected App.  
5. Retrieve your _consumer_key_ from the Connected App.

### Configure the Salesforce Notifier Block

1. Log in to your Hyperscience instance.
2. Go to **Flows**, and click on the name of the flow you want to add the Salesforce Notifier Block to.
3. Click **Edit Flows**.
4. In Flow Studio, click **Outputs**.
5. Click **Add**, and select **Salesforce Notifier Output Block**.
6. Configure the settings described in the [Block settings table](https://help.hyperscience.ai/v42/docs/salesforce-notifier#block-settings-table) in this article.