Drop us a short note with your inquiry by filling out the contact us form.
This "how-to-connect" documentation will explain the initial configuration of an example connection from Nimble to a SharePoint Online List in Office 365. We will be synchronizing data stored in Nimble.
This guide presupposes that you have installed the Layer2 Cloud Connector and that you are familiar with its basic functionality. The Layer2 Cloud Connector User Documentation will provide you with all necessary information.
2. Configuring the Layer2 Cloud Connector
2.2 Configuring the Data Entity 1
2.3 Configuring the Data Entity 2
Connecting to Nimble is very simple. Go to your account settings:
Click on API tokens and Generate New Token
Copy the generated token. That is all.
Create a new connection by using the Create New Connection option in the Actions pane (right-hand side). The new connection will appear at the bottom of the Connection Manager List (left-hand side). Click on your newly created connection to open the connection configuration settings.
Choose a meaningful name for your connection and replace the current "New Connection" Connection Title with it.
Connections to Nimble are read-only connections. Therefore we will choose Left to Right as Synchronization Direction.
We will now set up our Data Entities. Go to the data entity “Data Entity 1” to open the configuration settings.
Choose a Data Entity Title. It is recommended to give your entities meaningful names to maintain an overview when you decide to set up multiple connections.
Select the Data Provider for REST from the data provider list. You can search for REST by typing into the selection box.
For the Connection String, we need the information mentioned in step 1. You can copy the below connection string and adjust it to match your gathered information. Use the Verify Connection String option to evaluate if the provided connection string is valid.
The Select Statement text box is used to define specific data queries. We will be gathering all the contacts data. You can copy the below select statement and adjust it to match your needs. Save your changes by using the right-hand pane option Save Changes.
SELECT * FROM data
To check if all necessary columns are received, you can use the Preview Data option on the right-hand pane which will provide you with a pop-up window showing your sample data from your Nimble entity.
We are going to send the data to a custom SharePoint Online list. It's required that you set up this list prior to the next steps. Your list should contain matching columns according to your source entity.
Use the left-hand pane to switch to the data entity "Data Entity 2". We will be using the Layer2 SharePoint Provider for this setup.
For more information about the SharePoint provider visit:
You can copy the below Connection String which contains the minimum of required properties to connect to your custom SharePoint Online list.
Enter the password that belongs to the user account used in the connection string into the Password field. Save your changes by using the right-hand pane option Save Changes.
In the next step, we will configure our mapping settings. Click on the Mappings option on the left-hand pane. If your fields from SharePoint are named identical to the fields from your source system, the Enable Auto Mapping option will match those columns. Disabling this option allows you to match your columns as needed. We enabled auto-mapping in our setup. Save your changes by using the right-hand pane option Save Changes.
To run your connection switch back to the main connection configuration node and use the Run Now Button located on the bottom of the setup page. The Run Synchronization Toolbox will also display the synchronization process.
Below is a data preview of the information we have accessed in our source entity:
This will be the result in our SharePoint Online list after our initial successful synchronization:
As far as tested, this connection supports uni-directional only.
The data model is based on the endpoint from the Nimble API. You can find the API information here.