![]() |
VOOZH | about |
The CData API Server enables you to access Calendly data from cloud-based applications like the Salesforce console and mobile applications like the Salesforce1 Mobile App. In this article, you will use the API Server and Salesforce Connect to access Calendly external objects alongside standard Salesforce objects.
If you have not already done so, download the CData API Server. Once you have installed the API Server, follow the steps below to begin producing secure Calendly OData services:
To work with Calendly data from Salesforce Connect, we start by creating and configuring a Calendly connection. Follow the steps below to configure the API Server to connect to Calendly data:
Start by setting the Profile connection property to the location of the Calendly Profile on disk (e.g. C:\profiles\CalendlyProfile.apip). Next, set the ProfileSettings connection property to the connection string for Calendly (see below).
To authenticate to Calendly, provide an API Key. The Calendly API Key, can be found in your Calendly account, under 'Integrations' > 'API & Webhooks' > 'Generate New Token'. Set the APIKey in the ProfileSettings connection property.
π Connecting to a datasource (SQLite is shown)
Next, create a user to access your Calendly data through the API Server. You can add and configure users on the Users page. Follow the steps below to configure and create a user:
Having created a user, you are ready to create API endpoints for the Calendly tables:
Having configured a connection to Calendly data, created a user, and added resources to the API Server, you now have an easily accessible REST API based on the OData protocol for those resources. From the API page in API Server, you can view and copy the API Endpoints for the API:
π API EndpointsFollow the steps below to connect to the feed produced by the API Server.
URL: Enter the URL to the OData endpoint of the API Server. The format of the OData URL is https://your-server:your-port/api.rsc.
Note that plain-text is suitable for only testing; for production, use TLS.
Select JSON in the Format menu.
After you have created the external data source, follow the steps below to create Calendly external objects that reflect any changes in the data source. You will synchronize the definitions for the Calendly external objects with the definitions for Calendly tables.
After adding Calendly data as an external data source and syncing Calendly tables with Calendly external objects, you can use the external objects just as you would standard Salesforce objects.
Create a new tab with a filter list view:
π A filtered list view shown on a custom tab. (NetSuite Invoices are shown.)Display related lists of Calendly external objects alongside standard Salesforce objects:
π A related list that shows an indirect lookup relationship, which links a child external object to a parent standard object. (Salesforce accounts and associated NetSuite invoices are shown.)You can use the following checklist to avoid typical connection problems:
Ensure that the server you are hosting the API Server on is using TLS 1.1 or above. If you are using the .NET API Server, you can accomplish this by using the .NET API Server's embedded server.
If you are using IIS, TLS 1.1 and 1.2 are supported but not enabled by default. To enable these protocols, refer to the how-to on MSDN and the Microsoft technical reference.
If you are using the Java edition, note that TLS 1.2 is enabled by default in Java 8 but not in Java 6 or 7. If you are using these earlier versions, you can refer to this this Oracle how-to.
Learn more or sign up for a free trial:
CData API Server