Each Pendula customer has their very own environment or tenant, of Pendula. This tenant is unique to your organisation or business, and contains all of your configured flows and templates.

Before you can start building out your flows we need to firstly connect Pendula to your data source-in this case, Salesforce.

Quick links:

How does Pendula integrate with Salesforce?

How to connect Pendula to your Salesforce environment

How does Pendula integrate with Salesforce?

Pendula integrates to Salesforce using a process called OAuth 2.0, which is a commonly used method for securely connecting web platforms together.

OAuth works by authorising access to Salesforce via a specific user within either a Sandbox or Production environment. Once authorised, Pendula then inherits the visibility and permissions associated with that user within Salesforce.

OAuth is quick, secure and easy. Once you know which user you will use to OAuth to Pendula, connecting your tenant to Salesforce can be done in a matter of seconds.

How to connect Pendula to your Salesforce environment

Before you start

You'll firstly need a Pendula tenant before you can integrate it to Salesforce. If you don't already have access to Pendula, please contact the Pendula Support team.

Before proceeding, think about what apps, object permissions and visibility Pendula might require within your Salesforce environment, as this will help determine which User you should use to complete the OAuth process.

Typically OAuth is done with a user with system administrator or equivalent access to ensure full coverage of any use cases. If need be, you can always change this to a different user down the track.

While not essential for this process, you will require the Pendula managed package installed in your Salesforce environment in order to sync any outbound or inbound messages sent, along with make use of the Console for ad-hoc messaging.

See Salesforce deployment checklist for more information.

Important considerations

You'll want to ensure the user you OAuth with will have consistent access to Salesforce and any relevant apps, as deactivating this user will essentially disconnect Pendula as well.

If the user is deactivated, or access revoked and OAuth completed using a different user, this may impact any active flows you have setup within Pendula.

Steps

1. Log in to your Pendula tenant

2. Navigate to the Pendula Settings screen by clicking on the avatar icon in the top-right hand side of the app, and then select Pendula Settings

3. Scroll down to the Salesforce Integration section

4. From the Salesforce instance dropdown, select either Production or Sandbox (depending on the type of environment you'll be connecting Pendula to) and then click on Connect to Salesforce

5. In a new browser window, you'll be prompted to enter the username and password of the Salesforce user you are authorising to connect Pendula to Salesforce.

6. Enter these details and click on Login. Complete the OAuth process by clicking on Allow from the Allow Access? screen

7. Your Pendula tenant is now connected to your Salesforce environment!

You should now see a green confirmation message within your Pendula tenant, and an Authorised connection to... message underneath the Salesforce Integration section.

Tips and tricks

• If needed, you can revoke access to Pendula by clicking on the Revoke access button. This will break the integration between Pendula and Salesforce, so any active flows or experiences will error until the connection is re-authorised using the same OAuth process as before

• You can use OAuth to initially connect your Pendula tenant to a sandbox environment for testing, before revoking access and re-connecting it to your Production environment when you are ready to set your flows live

• Once you OAuth Pendula to Salesforce, you can revoke access and repeat the process quickly and easily with a different user if required

• If you have any active flows within Pendula, you'll want to avoid revoking access and re-connecting Pendula at a time when these flows are expected to trigger. Once you have re-connected Pendula, you'll also want to ensure you re-activate any active flows to ensure Pendula still has access to the data required for these flows to continue to run

You should now be able to:

• Start creating related objects, which point Pendula to the relevant objects within Salesforce you would like to configure communications regarding. See Related objects for more information.

• If needed, you can revoke access and OAuth to a different Salesforce User or environment