Skip to main content

Concord Data Source

The Concord connector enables you to ingest contract lifecycle management data from the ConcordNow REST API, including agreements, organizations, folders, reports, tags, members, and attachments. This connector is particularly useful for syncing contract metadata into a data warehouse, monitoring agreement status and renewals, and building reporting on your organization's agreement portfolio. Follow the instructions below to create a new data flow that ingests data from a Concord source in Nexla.
concord_api.png

Concord

Create a New Data Flow​

  1. 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.

  2. Select the Concord connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Concord instance, and click Next; or, create a new Concord credential for use in this flow.

  3. In Nexla, Concord data sources can be created using pre-built endpoint templates, which expedite source setup for common Concord endpoints. Each template is designed specifically for the corresponding Concord endpoint, making source configuration easy and efficient.
    • To configure this source using a template, follow the instructions in Configure Using a Template.

    Concord sources can also be configured manually, allowing you to ingest data from Concord 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 Concord endpoints. Each template is designed specifically for the corresponding Concord endpoint, making data source setup easy and efficient.

Most Concord endpoints are scoped to an organization, so they require an Organization ID. You can obtain your organization IDs using the List User Organizations endpoint, which returns every organization the authenticated user belongs to.

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.

    List User Organizations

    This endpoint returns the list of organizations that the authenticated user is a member of. Use it first to discover the Organization IDs required by most other Concord endpoints.

    • This endpoint requires no additional parameters. Select the template and the source is ready to test.
    • Nexla reads each organization from the organizations array in the response, producing one record per organization.

    The Organization ID values returned by this endpoint are used to configure organization-scoped endpoints such as List Agreements, List Folders, and List Reports.

    Get Organization

    This endpoint returns the details of a single organization. Use it when you need configuration or metadata for one specific organization.

    • Enter the ID of the organization to retrieve in the Organization ID field. You can obtain this value from the List User Organizations endpoint.

    List Agreements

    This endpoint returns the agreements that belong to an organization. Use it to sync your contract portfolio—including status, parties, and metadata—into Nexla for reporting or downstream processing.

    • Enter the ID of the organization whose agreements you want to ingest in the Organization ID field.
    • This endpoint is paginated. Nexla automatically advances through pages using the start and limit parameters and stops when no further records are returned, so you do not need to configure pagination manually.

    Each element of the returned array is treated as a separate record. To retrieve the full details of an individual agreement, use the Get Agreement endpoint with the corresponding agreement ID.

    Get Agreement

    This endpoint returns the full details of a single agreement by ID. Use it to retrieve complete agreement metadata, fields, and status for a specific contract.

    • Enter the ID of the organization the agreement belongs to in the Organization ID field.
    • Enter the ID of the agreement to retrieve in the Agreement ID field. Agreement IDs can be obtained from the List Agreements endpoint.

    List Agreement Attachments

    This endpoint returns the list of attachments associated with a specific agreement, such as exhibits, schedules, and supporting documents.

    • Enter the ID of the organization the agreement belongs to in the Organization ID field.
    • Enter the ID of the agreement whose attachments you want to list in the Agreement ID field.

    This endpoint returns attachment metadata. To retrieve the binary content of an individual attachment, use the Download Agreement Attachment endpoint.

    Download Agreement Attachment

    This endpoint retrieves the content of a single agreement attachment by ID. Use it to ingest the actual document associated with an agreement.

    • Enter the ID of the organization the agreement belongs to in the Organization ID field.
    • Enter the ID of the agreement the attachment belongs to in the Agreement ID field.
    • Enter the ID of the attachment to download in the Attachment ID field. Attachment IDs can be obtained from the List Agreement Attachments endpoint.

    List Folders

    This endpoint returns the list of folders in an organization. Use it to map the folder structure your agreements are organized into.

    • Enter the ID of the organization whose folders you want to retrieve in the Organization ID field.

    List Organization Members

    This endpoint returns the list of members in an organization, including their roles. Use it to sync user and access data for governance or reporting.

    • Enter the ID of the organization whose members you want to retrieve in the Organization ID field.
    • This endpoint is paginated. Nexla automatically advances through results using the start offset and limit parameters and stops when no further records are returned.

    List Reports

    This endpoint returns the reports configured for an organization. Use it to discover available reports and their identifiers.

    • Enter the ID of the organization whose reports you want to retrieve in the Organization ID field.
    • This endpoint is paginated. Nexla automatically advances through pages using the page and numberOfItemsByPage parameters and stops when no further records are returned.

    Records are read from the reports array in the response. To retrieve a single report's full details, use the Get Report endpoint with the corresponding report ID.

    Get Report

    This endpoint returns the details of a single report by ID for an organization.

    • Enter the ID of the organization the report belongs to in the Organization ID field.
    • Enter the ID of the report to retrieve in the Report ID field. Report IDs can be obtained from the List Reports endpoint.

    List Tags

    This endpoint returns the list of tags available in the system. Tags are used to categorize and organize agreements within Concord.

    • This endpoint requires no additional parameters. Select the template and the source is ready to test.
    • Records are read from the tags array in the response.

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​

Concord data sources can be manually configured to ingest data from any valid ConcordNow API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Concord sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom request parameters.

API Method​

  1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Concord API from the Method pulldown menu. Concord read operations use:

    • GET: For retrieving agreements, organizations, folders, reports, tags, members, and attachments

API Endpoint URL​

  1. Enter the URL of the Concord 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 any required path parameters. ConcordNow endpoints follow the pattern https://{subdomain}.concordnow.com/api/rest/1/...—for example, https://mycompany.concordnow.com/api/rest/1/organizations/{organization_id}/agreements.

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.

Path to Data​

Optional

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. This is particularly useful when API responses wrap records inside a named property.

For example, the Concord List Agreements endpoint returns a top-level array, while the List Reports endpoint nests records under a reports property and List Tags nests records under a tags property. By entering the path to the relevant data, you can configure Nexla to treat each element of the returned array as a record.

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—for example, $.reports[*] to access the array of reports, or $[*] to treat each element of a top-level array as a record.
    Path to Data Example:

    For the Concord List Reports endpoint, records are contained in a top-level array named reports, so the path to the relevant data would be entered as $.reports[*].

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.

    PathSuggestions.png

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, a paginated Concord response may include total counts or pagination details alongside the array of records. If you have specified the path to the relevant data but metadata of interest is located in a different part of the response, you can specify a path to this metadata to include it with each record in the generated Nexset(s).

Metadata paths are particularly useful for preserving API response context like total counts or pagination summaries 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.

Request Headers​

Optional

  • 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). Additional headers are often required for content type specifications or custom request requirements.

    You do not need to include any headers already present in the credentials. The X-API-KEY authentication header is handled automatically 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​

  1. 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 Concord 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.