Babelforce Data Source
Babelforce
Create a New Data Flow
-
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.
-
Select the Babelforce connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Babelforce instance, and click Next; or, create a new Babelforce credential for use in this flow.
-
In Nexla, Babelforce data sources can be created using pre-built endpoint templates, which expedite source setup for common Babelforce endpoints. Each template is designed specifically for the corresponding Babelforce endpoint, making source configuration easy and efficient.
• To configure this source using a template, follow the instructions in Configure Using a Template.Babelforce sources can also be configured manually, allowing you to ingest data from Babelforce endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
• To configure this source manually, follow the instructions in Configure Manually.
Configure Using a Template
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Babelforce endpoints. Each template is designed specifically for the corresponding Babelforce endpoint, making data source setup easy and efficient.
Endpoint Settings
-
Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.
Endpoint Testing
Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.
-
To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.
-
If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.
Configure Manually
Babelforce data sources can be manually configured to ingest data from any valid Babelforce API endpoint — for example, endpoints that are not yet covered by the pre-built templates, or endpoints that require custom query parameters, request headers, or chained requests.
With manual configuration, you can also build more complex Babelforce sources, such as sources that combine multiple Babelforce endpoints (for example, calling /api/v2/outbound/lists and then iterating over each list with /api/v2/outbound/lists/{'{id}'}/leads).
API Method
-
To manually configure this source, select the Advanced tab at the top of the configuration screen.
-
Select the API method that will be used for calls to the Babelforce API from the Method pulldown menu. Most Babelforce read endpoints use:
- GET: For retrieving data from the API (the typical choice for a data source)
- POST: For endpoints that accept a request body, such as search-style endpoints
API Endpoint URL
- Enter the URL of the Babelforce API endpoint from which this source will fetch data in the Set API URL field. This should be the complete URL including the protocol (https://) and the full API path — for example,
https://services.babelforce.com/api/v2/calls.
Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. The Babelforce base URL stored on the credential is not automatically substituted in manually configured API URLs, so the full URL must be entered here.
Date/Time Macros (API URL)
Optionally, the API URL can be customized using macros — all macros added to the API URL will be converted into values when Nexla executes the API call. Macros are dynamic placeholders that allow you to create flexible API endpoints that can adapt to different time periods or data requirements. This is particularly useful for Babelforce time-window endpoints such as /api/v2/calls?startDate=...&endDate=... or /api/v2/metrics/calls.total?startDate=...&endDate=....
Macros are especially helpful for Babelforce metric and call-listing endpoints, where the startDate and endDate query parameters typically advance with each ingestion run.
-
To add a macro, type
{at the appropriate position in the API URL (within the Set API URL field), and select the desired macro from the dropdown list.-
{now}– The current datetime -
{now-1}– The datetime one time unit before the current datetime -
{now+1}– The datetime one time unit after the current datetime -
custom– Datetime macros can reference any number of time units before or after the current datetime — for example, enter(now-4)to indicate the datetime four time units before the current datetime
-
-
Select the format that will be applied to datetime macros from the Date Format for Date/Time Macro pulldown menu. Babelforce expects ISO 8601 datetime values, so the format applied here should produce that shape (for example,
yyyy-MM-dd'T'HH:mm:ss'Z'). -
Select the datetime unit that will be used to perform mathematical operations in the included macro(s) from the Time Unit for Operations pulldown menu — for example, for the macro
{now-1}, whenDayis selected,{now-1}will be converted to the datetime one day before the current datetime.
Lookup-Based Macros (API URL)
Column values from existing lookups can also be included as macros in the API URL. Lookup-based macros allow you to reference data from previously configured data sources or lookups, enabling dynamic API endpoints that can adapt based on existing data. This pattern is useful for Babelforce endpoints that require an identifier in the path — for example, iterating over outbound list IDs to fetch leads with /api/v2/outbound/lists/{'{list_id}'}/leads.
-
To include a lookup column value macro, select the relevant lookup from the Add Lookups to Supported Macros pulldown menu.
-
Type
{at the appropriate position in the API URL, and select the lookup column-based macro from the dropdown list. Lookup-based macros are automatically populated into the macro list when a lookup is selected in the Add Lookups to Supported Macros pulldown menu.
Path to Data
Babelforce list endpoints typically wrap result arrays inside a named property — for example, calls, agents, applications, leads, or data. If only a subset of the data returned by the API endpoint is needed, you can designate the part(s) of the response that should be included in the Nexset(s) produced from this source by specifying the path to the relevant data within the response.
For example, the response from /api/v2/calls returns the call records inside a top-level calls array, so the path to data would be $.calls[*]. Similarly, /api/v2/agents returns records inside an agents array, and /api/v2/business-hours returns records inside a data array.
Path to Data is essential when API responses have nested structures. Without specifying the correct path, Nexla might not be able to properly parse and organize your data into usable records.
-
To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.
-
For responses in JSON format enter the JSON path that points to the object or array that should be treated as relevant data. JSON paths use dot notation (e.g.,
$.calls[*]to access an array of calls within a response object). -
For responses in XML format, enter the XPath that points to the object/array containing relevant data. XPath uses slash notation (e.g.,
/response/data/itemto access item elements within a data element).
Path to Data Example:For the Babelforce
/api/v2/callsendpoint, which returns records inside a top-level array namedcalls, the path to the response would be entered as$.calls[*]. -
Autogenerate Path Suggestions
Nexla can also autogenerate data path suggestions based on the response from the API endpoint. These suggested paths can be used as-is or modified to exactly suit your needs.
-
To use this feature, click the Test button next to the Set API URL field to fetch a sample response from the API endpoint. Suggested data paths generated based on the content & format of the response will be displayed in the Suggestions box below the Set Path to Data in Response field.
-
Click on a suggestion to automatically populate the Set Path to Data in Response field with the corresponding path. The populated path can be modified directly within the field if further customization is needed.
Metadata
If metadata is included in the response but is located outside of the defined path to relevant data, you can configure Nexla to include this data as common metadata in each record. This is useful when you want to preserve important contextual information that applies to all records but isn't part of the main data array — for example, total counts, pagination cursors, or summary statistics returned alongside Babelforce list responses.
Metadata paths are particularly useful for preserving API response context like total counts or pagination information that apply to all records in the response.
-
To specify the location of metadata that should be included with each record, enter the path to the relevant metadata in the Path to Metadata in Response field.
- For responses in JSON format, enter the JSON path to the object or array that contains the metadata, and for responses in XML format, enter the XPath.
Request Headers
-
If Nexla should include any additional request headers in API calls to this source, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g.,
header1:value1,header2:value2). For Babelforce, additional headers are rarely required because authentication and content negotiation are handled through the credential.You do not need to include the
X-Auth-Access-IdorX-Auth-Access-Tokenheaders here. These are automatically attached by Nexla based on your credential configuration.
Endpoint Testing
After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.
-
To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.
-
If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.
Save & Activate the Source
- Once all of the relevant steps in the above sections have been completed, click the Create button in the upper right corner of the screen to save and create the new Babelforce data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.