Salesforce Third-Party Integration: Set up a Bidirectional Sync between Salesforce and Other Tools 

Salesforce third-party integration

Salesforce is perfect for teams working with customer data. Feature-rich, and easy to use, it lets you control every aspect of the sales process, without advanced technical know-how. 

There are ways to get more from it, however. The data you store can be shared with teams using other tools like Jira, Zendesk, etc. That means your sales department can work with other departments more easily, with data filtered and shared automatically. 

What’s covered in this article?

Why Integrate Salesforce Using a Third-Party Integration Solution 

Though Salesforce includes a broad range of functionality, a third-party integration can take you beyond its default capabilities.

Note: If you want to learn more about the native Salesforce functionality, you can read this Salesforce to Salesforce integration guide.

Specialized applications bring features that can help you connect to other platforms, with little development effort. Here are some examples of how that could work.

Common Use Cases 

Salesforce is typically used by sales teams, but you can use a third-party integration to connect to other platforms. 

If you have sales teams in different locations, you can integrate their data, and exchange tickets. Perhaps they sometimes acquire customers that are best handled by other teams. An integration can help your teams share their details automatically.

Developers using Jira can share progress on new items with the sales team via an integration. The sales team can make developers aware of customer requests for features, and developer feedback can be automatically sent back to the original ticket.

Project managers working in Azure DevOps can share targets with the sales team, and the sales team can have that data automatically synchronized with the other team’s system.

There are many other ways a third-party integration can contribute to your business. All it takes is a little imagination.

Choosing the Right Solution for a Salesforce Third-Party Integration 

The integration solution we have chosen for this article is called Exalate. Exalate is an integration solution that enables two-way syncs between multiple tools like Salesforce, Jira, Zendesk, Servicenow, HP ALM, GitHub, Azure DevOps, and more.

There are a few criteria that you need to take into consideration when choosing an integration solution for your specific use case.  

Decentralized Integration

With a decentralized integration, neither side owns the connection. If different teams manage each platform, they retain their autonomy and have full control over what they share, and how incoming data is mapped to their systems. Exalate gives each team an independent configuration screen, allowing them to choose what is shared. 

Flexibility

Exalate is hugely customizable and suitable for many scenarios. Its scripting engine allows you to filter and map data using advanced logic. Exalate also has a drag-n-drop mode for simpler use cases.

Reliability 

Exalate is designed with reliability in mind. If one side of the connection drops, it can recover gracefully. There’s no need for manual intervention. Once it is running, you can forget about it.

How to Integrate Salesforce with other Tools through a Third-Party Solution 

An advantage of using Exalate as a Salesforce third-party integration solution is that it uses a common interface on each platform.

In this example, we’ll connect it to Jira Cloud, but the process is the same for other platforms. You can integrate any of these with Salesforce, or each other, just as easily.

The process starts with installing Exalate on both platforms, then connecting them. Next are some optional configuration steps for controlling how data is shared, and when data exchange happens. 

Let’s go through each step.

Step 1: Install Exalate on Salesforce

You can do the first two steps in either order, but let’s install Exalate on Salesforce first. Open the AppExchange marketplace. Search for “Exalate”, then click “Get It Now”. 

install exalate on salesforce

Choose either production or sandbox mode depending on your needs, along with who has access to Exalate, and whether to grant access to third-party websites.

Once you’ve made your choices and “Installation Complete” appears, click “Done”. Now you have to request a node. In Salesforce, you can find the newly installed app by typing “Exalate” in the search bar. 

If you click “Request Node”, you’ll get an email with a verify button. Click that to set up your node and complete your installation.

request an exalate node

Step 2: Install Exalate on Jira

Next, switch to Jira and install Exalate there. We’re using Jira Cloud, but you can read about how to set up Jira on-premise here.

install exalate on jira

First, search for “Exalate” in the Atlassian Marketplace. Click “Exalate Jira Issue Sync & more” and install it via the “Try it free” button, followed by the “Start free trial” button. 

After a brief install process, click “Get Started”. 

Now you’re ready to connect your instances.

Step 3: Connect Salesforce and Jira

Now that Exalate is installed on both platforms, let’s create a connection between Salesforce and Jira.

You can start from either side of the connection. This guide uses Salesforce, so find the Exalate screen on your Salesforce installation, then click “Connections”. This screen shows any existing connections but will be empty the first time you use it.

exalate for salesforce integrations

To create your first connection, click the “Initiate connection” button. Next, you’ll see a “Destination instance URL” box. Enter your Jira instance’s address, so that Exalate can verify it is available.

Next, you should select the Basic mode or the Script mode. 

The Basic mode uses automatic configuration, with simple visual tools. The Scripting mode uses programming logic to set complex rules that control how your data is shared.

exalate configurarion modes

Let’s cover them in turn.

Continue with the Basic Mode

The Basic mode takes you through a few simple dialogue screens. You can head straight to the other side of your connection by clicking a button.

Once there, choose a project and click “Confirm”. Your connection is now ready and you can test it by picking a test issue to synchronize.

If you don’t have admin access to the other side of the connection, use the Script Mode guide to complete the process.

Continue with the Script Mode

In the Script mode, you need to choose a name for your connection, and can optionally add a description, both of which can help you make sense of things later on, especially if you have multiple connections.

After adding these details, click “Initiate”. You’ll see a “Copy invitation code” button. Click that, and then click the “Go to remote” button to visit the other side of your connection.

copy jira salesforce sync invitation

On the Jira connection screen, click the “Accept invitation” button and paste the code into the space provided. The code should be on your clipboard. If not, go back and copy it again.

accept salesforce integration invitation

Click next, and Exalate will ask you a few questions, as in the Basic mode. When you’re done, the connection is created and you can move on to the next steps.

Step 4: Configure the Connection Rules

Step 4 lets you control what is shared, and how fields from each side of the connection are mapped onto each other.

To begin, find the newly created connection on the Exalate connections screen. Then click the “edit connection” button.

There are multiple tabs on the screen that appears, and “rules” should be visible by default. Select it if not.

salesforce third-party sync rules

Here, you can see two sets of rules, one for incoming items and one for outgoing. These describe how each item is mapped to its equivalent on the other platform.

When you sync tickets, the data is copied between these fields, from the existing ticket to the new one.

By default, the mappings use identical, or similar fields. In the above screenshot, you can see that replica.description maps to entity.Description in the outgoing rules. 

You can change, remove or adjust any of these lines. 

If you want to remove a line, delete it or comment it out. You could also add specific text. For example, you could change the description line to read: replica.description = “Synced from Salesforce”. That way all items in Jira that come from Salesforce will have that description.

You could match items to others if that suits you better. Perhaps you want to make the summary on one platform list the status on the other. In that case, you could change the summary line to replica.summary = entity.Status

You can go further and use code to make decisions based on the values being exchanged. That’s beyond the scope of this article, but if you have any coding skills you can probably think of a few ideas yourself.

Step 5: Set Up Triggers to Automate Data Exchange

In the previous step, you used sync rules to decide what maps to what. In this step, you’ll create a trigger that decides when items are exchanged. You can have as many triggers as you like, setting different conditions for sharing.

Perhaps you want to share high-priority items or items assigned to a particular person. You can create separate triggers for both of those things. 

To get started, click the “Triggers” tab on the edit connection screen you accessed in the previous step. Then click the “Create trigger” button.

salesforce integration triggers

On the add trigger screen, there are several controls. Firstly, you can choose the type of entity the trigger synchronizes. There’s a notes section to describe the trigger, and a switch, labeled “Active?”, to switch the trigger on and off.

There’s also a “Use search query” switch that gives you a choice of how to do things. If you don’t use a query, you can specify values for fields that will activate the trigger if met.

For more advanced decision-making, you can use a search query. That uses code for more advanced control. In Salesforce, you use SOQL (Salesforce Object Query Language), and JQL (Jira Query Language) in Jira.

As an example, you could use Name = ‘demo opportunity’ to select items with the specified name. You can use programming constructs like AND and OR to combine conditions.

For more on using  SOQL with Exalate, read this. For JQL triggers, check this guide.

When you’re done, click the “Add” button to create the trigger.

Step 6: Start Synchronizing Salesforce and Jira

Now the platforms are connected, you can start adding more triggers that match the data you want to share. The integration will automatically share this data between Salesforce and Jira. It’s a good idea to monitor what happens at first to make sure it matches your requirements.

Now that it’s working, you can make it do even more for you by creating advanced filters and sharing rules. Experimenting with the triggers and sync rules can give you new ideas on how you can use it, so try a few things out.

Conclusion 

When you want to share data between platforms your choice of solution is key. Get it right and your teams will benefit. 

Exalate, as a Salesforce third-party integration solution, is designed to deliver reliability and flexibility in a decentralized integration. It lets you integrate multiple platforms easily without leaving the tool(s) you are familiar with.

You can choose exactly how and when data is shared. Once set up, your integration does the hard work for you, leaving your teams free to get on with what they do best. 

Recommended Reads:

Comments are closed.