Integrate Showpad activities in Salesforce

See how it's done on Salesforce Lightning

• Configure CORS in Salesforce Lightning
• Setup a Salesforce instance in Showpad
• Basic troubleshooting

Do this step by step

1. Configure CORS in Salesforce Lightning

The first step in configuring the Salesforce integration is to allow requests coming from the Showpad domain. Salesforce allows its customers to control which websites are allowed to use the Salesforce API. This helps keep your Salesforce instance secure by only allowing requests from known sites and denying all others.

This setting is called CORS (Cross-Origin Resource Sharing) and configuration is required for Showpad to integrate with Salesforce. The instructions below show how a Salesforce Admin can enable our Showpad domain to make requests to your Salesforce instance. 

This allows:

• Showpad to create a Salesforce Activity whenever a user in the Showpad app or the Web App shares content with a prospect or customer.
• Showpad to create a Salesforce Event whenever a user on any mobile app wants to log a meeting to Salesforce.

1. Go to the Setup page in Salesforce.com as a Salesforce admin.
2. In the left menu, search for CORS. You can also manually select Security Controls > CORS.
3. Add a New Whitelisted Origin.
4. Add https://*.showpad.biz and click Save.

   Note: If the permission Modify All Data is disabled in Salesforce, we will inform you on Showpad's Online Platform that we could not verify the CORS configuration. You will still be able to continue setting up the integration when you see this warning.

2. Setup a Salesforce instance in Showpad

1. To connect Salesforce and Showpad, you need to set up your Salesforce instance(s) in Showpad. You can configure multiple Salesforce instances if your company uses more than one.
   Open the Showpad Online Platform and log in with your Administrator credentials.
2. In Settings, select CRM under the Integrations section, then select Configure a Salesforce Instance.
3. Enter a Description for your Salesforce Instance. If you're planning to set up multiple Salesforce instances, be sure to choose appropriate names for each instance to make it easier to identify them.
   • If you're using a custom domain to access Salesforce, like https://companyxyz.my.salesforce.com, enable Use a Custom Domain and enter companyxyz.
   • Showpad user accounts can be automatically created when users log in for the first time with their Salesforce credentials. Learn more about the Auto-Provisioning option.
4. Click Next and Connect to Salesforce.
5. You'll need to enter your Salesforce credentials now. This login will be used as an Integration user to connect with Salesforce.
   If the user that is used to configure this integration is not a full admin, the following permissions are needed:
   System settings
   • API Enabled
   • Edit Tasks
   • Edit Events
   • View Roles and Role Hierarchy
   • View Setup and Configuration
   
   Object settings
   • Read/Create/Edit for Leads, Contacts, Opportunities, Accounts objects.
   • Read/Create/Edit/Delete for Showpad Activities, Showpad Activities Items, Showpad Content & Showpad Content Views objects.
   The integration works with a server to server communication. The outcome of this is that the originating IP address will not be the company's IP range or IP address, but a Showpad IP address. If you use IP restrictions, we advise reading our OAuth app recommendations.
   After logging in, the Showpad Online Platform will reopen. Your users will see a form when creating a new lead in Salesforce. You can configure the form in this screen. Repeat the steps for the Contacts form.
   • Three fields are required. By default, Email, Last Name, and First Name are selected.
   • Select the Fields you want to include.
   • Rearrange the fields by clicking, holding and dragging a field to a different position in the list.
   
6. You can now enable Content Recommendations for your sales colleagues. Refer to this page if you want more information. To use this feature, you will need to install the Showpad for Salesforce app via Salesforce's AppExchange. Click Save.
7. The last tab you will see is for enabling advanced logging to custom objects. Account and Opportunity will be selected by default, and you can indicate other relevant objects by checking their boxes for the “Related To” field. This allows your users to relate shares to objects other than accounts or opportunities when logging tasks.
8. In Salesforce, when editing or creating the custom object it needs to have the Allow Activities box checked in the Optional Features section.
9. Select the custom objects you want to log activity against then click Save. The list you see has the same objects that are available in the connected SFDC’s instance in the Related To field of a Task. Users are not able to log meetings to a custom object.  
10. It is possible to control which user groups can use the Salesforce integration. Click the Groups with Access tab and select All Users or Selected groups.
11. When a Share is logged, you'll see the email body and a link to view the Share as the recipient in the comments of the Task Information. Depending on how your settings are configured, it will look similar to this for your users.

3. Basic Troubleshooting

OAuth authentication error

The Showpad and Salesforce integration works with a server to server communication. A consequence of this is that the originating user IP address will be changed with Showpad's address during the login process.

In cases where Login IP ranges are used, or when users experience OAuth sign-in errors, we recommend changing the settings in the OAuth app from Enforce IP restrictions to Relax IP restrictions.

The Relax IP restrictions setting allows users to run the connected Showpad app without IP restrictions. You can find these settings in the Salesforce Administer section.

1. In Setup, search Connected Apps. Open the Connected Apps OAuth Usage options in the Manage Apps tab.
   
2. Find the Showpad Salesforce Integration app and click Install.
3. From the Connect Apps OAuth Usage list, click Manage App Policies.
4. Click Edit Policies. Click the IP Relaxation drop down menu, then change Enforce IP restrictions to Relax IP restrictions.
   
5. Click Save.

Salesforce connection is not working on the Web app

Make sure you are working on a browser that fully supports HTML, for a full overview of our browser requirements, click here.
For Internet Explorer users, please make sure you're working on IE11 or higher. Please make sure that in the Security settings, you have the miscellaneous option set to enable for both internet and intranet. If this is not the case, Internet Explorer will not allow the Showpad page to connect to the Salesforce domain and get the contacts and leads data.

1. Go to Settings, Internet Options, Security.
2. You should see an Internet icon, make sure it is selected. If they are using Local intranet, make sure to apply the same change there as well.
3. Choose Custom.
4. Scroll until you find the below, make sure Access data sources across domains is enabled
5. Apply and save.
6. Make sure to apply the same settings for their Local intranet as well.
7. You will also have to make sure you have your CORS set-up in your Salesforce instance.

XMLHttpRequest cannot load, the Response has status code 401

To make Salesforce API calls we need a valid access token. The access token is obtained on the Showpad servers and not in the user's browser. If the Salesforce setting "locks the session to the IP address" is activated, it means that we can only send api calls from the Showpad servers, because we requested the Salesforce token on our servers. Using that access token on a different IP address (your browser), it will not work due to this Salesforce setting. If you switch off this setting, the access token can be used in the browser as well and you'll be able to make Salesforce requests in the Web app.
Note that the mobile apps don't use our servers to request a new access token, so they don't have this issue.

Navigate to Session Settings and ensure the box for Lock sessions to the IP address from which they originated is unchecked.