Overview
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. |
Associated Username | Yes | The username associated with the Salesforce Connected App |
Consumer Key | Yes | The Consumer Key from the Salesforce Connected App |
Private Key | Yes | The key generated during the creation of the Salesforce Connected App |
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
Install the Hyperscience package in the desired Salesforce org.
Go to the Salesforce AppExchange’s Hyperscience Platform listing.
Click the Get It Now button.
Enter your details and click the Contact Me button.
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.
Add Hyperscience Permission Set to users that should have access to the Hyperscience application.
Go to the Setup page.
Search for “Permission Sets” and click the Permission Sets link.
Go to Hyperscience Permission Set.
Click Manage Assignments.
Click Add Assignments.
Select the users you want to give permissions to Hyperscience application by checking the checkbox for each user.
Click Assign and then Done.
Make sure that Hyperscience__Supervision_Task__c is added to Change Data Capture Events.
Go to the Setup page.
Search for “Change Data Capture” and click the Change Data Capture link.
Search for “Hyperscience__Supervision_Task__c” on the Available Entities window.
Select Hyperscience__Supervision_Task__c and click the arrow pointing to the right. Ensure that Hyperscience__Supervision_Task__c is added to the Selected Entities window.
Enable the Query All Files permission.
Go to the Setup page.
Search for “Permission Sets” and click the Permission Sets link.
Click the Hyperscience Permission Set link.
Click App Permissions.
Enable Query All Files.
Add the Hyperscience URL
Search your apps for “Hyperscience”. Click on the Hyperscience app.
Click on the Core Setup tab.
To edit the Hyperscience URL, click Edit.
Enter the full URL for your Hyperscience app.
Click Save.
Configure Authentication
Generate private key
Create the private key (salesforce.key) and certificate (salesforce.crt) by running the following command:
openssl req -x509 -sha256 -nodes -days 36500 -newkey rsa:2048 -keyout salesforce.key -out salesforce.crt
Copy the private key to your clipboard.
cat [private.key file] | sed 's/$/\\n/' | tr -d '\n' | pbcopy
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.
Create your JWT Connected App
Log in to Salesforce and go to Setup.
In the side nav, go to Apps > App Manager and click New Connected App.
Enter the information in the Basic Information section.
In API (Enable OAuth Settings), complete the following steps:
Disable the Enable OAuth Settings option.
In Callback URL, enter http://localhost.
Disable the Use digital signatures option and upload the salesforce.crt file that was generated when you created your private key.
In Selected OAuth Scopes, add the following permissions:
Manage user data via APIs (api)
Perform requests at any time (refresh_token, offline_access)
Click Save. The page should look similar to the following screenshot:
On the resulting page, click Manage.
Click Edit Policies.
In the OAuth policies section, change Permitted Users to Admin approved users are pre-authorized.
Click Save.
On the app page, in the Profiles section, click Manage Profiles.
On the Application Profile Assignment page, assign the user profiles that will access this app. This is the service account user, which will be configured in the Salesforce Listener and Notifier Blocks, and its details will be logged for any object updates.
Retrieve your consumer_key from the Connected App
Within Salesforce, click App Manager in the Apps navigation sidebar.
Find the connected app created in the previous section.
On the app’s row, click on the drop-down menu and select View.
Copy the Consumer Key from the API (Enable OAuth Settings) section. You’ll need the Consumer Key when configuring the Salesforce Listener Block.
Configure the Salesforce Notifier Block
Log in to your Hyperscience instance.
Go to Flows, and click on the name of the flow you want to add the Salesforce Notifier Block to.
Scroll to the end of the flow and click Outputs.
Click Add and select Salesforce Notifier Output Block.
Within the Notifier, configure the following parameters:
email_address: The email address of the service account to associate with the Block.
private_key: The key created during the process of connected app creation.
sandbox_environment: This boolean determines if the Salesforce instance is a sandbox or not.
consumer_key: The key generated by the jwt connected app.