Skip to main content

Concord Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a Concord location.
concord_api.png

Concord

Create a Concord Destination​

  1. Click the + icon on the Nexset that will be sent to the Concord destination, and select the Send to Destination option from the menu.

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

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

    Concord destinations can also be configured manually, allowing you to send data to Concord endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Concord endpoints. Each template is designed specifically for the corresponding Concord endpoint, making destination setup easy and efficient.

Each destination template sends the Nexset record as a JSON request body to the corresponding ConcordNow API endpoint. Organization-scoped templates require an Organization ID, which you can obtain using the List User Organizations source endpoint. For templates that act on an existing agreement, member, or tag, the relevant ID field defaults to the {{id}} field from the incoming record—map your data so this field holds the correct identifier, or override it with an explicit value.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Create Agreement

    This endpoint creates a new agreement within an organization. Each Nexset record is sent as the JSON agreement payload using an HTTP POST request.

    • Enter the ID of the organization to create the agreement under in the Organization ID field.
    • Ensure each Nexset record contains the agreement fields expected by the ConcordNow API, such as the title and template or document content.

    For the complete agreement payload schema, refer to the Concord API reference.

    Update Agreement

    This endpoint updates an existing agreement—including its metadata, status, and fields—using an HTTP PUT request. Send the partial or full agreement payload as JSON.

    • Enter the ID of the organization the agreement belongs to in the Organization ID field.
    • Enter the ID of the agreement to update in the Agreement ID field. This field defaults to the {{id}} value from the incoming record.

    Delete Agreement

    This endpoint deletes (voids) an existing agreement using an HTTP DELETE request.

    • Enter the ID of the organization the agreement belongs to in the Organization ID field.
    • Enter the ID of the agreement to delete in the Agreement ID field. This field defaults to the {{id}} value from the incoming record.

    Deleting an agreement is irreversible. Verify that the agreement IDs in your Nexset are correct before activating this destination.

    Send Agreement for Signature

    This endpoint sends an existing agreement for e-signature by creating a signature request. Send the signer details and signing options as the JSON payload.

    • Enter the ID of the organization the agreement belongs to in the Organization ID field.
    • Enter the ID of the agreement to send for e-signature in the Agreement ID field. This field defaults to the {{id}} value from the incoming record.
    • Ensure each record contains the signer details and signing options expected by the ConcordNow signature-requests endpoint.

    Apply Tag to Agreement

    This endpoint applies one or more tags to an existing agreement using an HTTP POST request. Send the tag payload as JSON.

    • Enter the ID of the organization the agreement belongs to in the Organization ID field.
    • Enter the ID of the agreement to apply the tag to in the Agreement ID field. This field defaults to the {{id}} value from the incoming record.

    Tag IDs can be obtained using the List Tags source endpoint, or created using the Create Tag destination endpoint.

    Remove Tag from Agreement

    This endpoint removes a previously applied tag from an agreement using an HTTP DELETE request.

    • Enter the ID of the organization the agreement belongs to in the Organization ID field.
    • Enter the ID of the agreement the tag is applied to in the Agreement ID field.
    • Enter the ID of the tag to remove in the Tag ID field. This field defaults to the {{id}} value from the incoming record.

    Upload Agreement Attachment

    This endpoint uploads a new attachment—such as an exhibit, schedule, or supporting document—to an existing agreement. Send the attachment payload as JSON.

    • Enter the ID of the organization the agreement belongs to in the Organization ID field.
    • Enter the ID of the agreement to upload the attachment to in the Agreement ID field. This field defaults to the {{id}} value from the incoming record.

    Create Folder

    This endpoint creates a new folder within an organization using an HTTP POST request. Send the folder payload (name, parent, and other properties) as JSON.

    • Enter the ID of the organization to create the folder under in the Organization ID field.
    • Ensure each Nexset record contains the folder name and any other properties expected by the ConcordNow folders endpoint.

    Create Tag

    This endpoint creates a new tag in the system using an HTTP POST request. Send the tag payload (name, color, and other properties) as JSON.

    • This endpoint requires no path parameters. Ensure each Nexset record contains the tag properties expected by the ConcordNow tags endpoint.

    Add Organization Member

    This endpoint invites or adds a new member to an organization using an HTTP POST request. Send the member payload (email, role, and other properties) as JSON.

    • Enter the ID of the organization to add the member to in the Organization ID field.
    • Ensure each Nexset record contains the member email, role, and any other properties expected by the ConcordNow members endpoint.

    Remove Organization Member

    This endpoint removes a member from an organization using an HTTP DELETE request.

    • Enter the ID of the organization the member belongs to in the Organization ID field.
    • Enter the ID of the member to remove in the Member ID field. This field defaults to the {{id}} value from the incoming record.

Configure Manually​

Concord destinations can be manually configured to send data to any valid ConcordNow API endpoint.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Concord API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, 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 write operations use POST to create resources, PUT to update agreements, and DELETE to remove agreements, members, or tags.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Concord API from the Content Format pulldown menu. The ConcordNow API expects JSON, so select the JSON format. Nexla will automatically convert the data to the selected format for each API call.

API Endpoint URL​

  1. Enter the URL of the Concord API endpoint to which you want to send the Nexset data in the URL field. 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. For update or delete operations, include the ID of the object to be modified at the end of the URL path.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    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.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Concord destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings.

Response Webhook​

Optional

Nexla can automatically send the response received from the Concord API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call—for example, the ID of a newly created agreement or signature request.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Concord API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the Concord API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Concord API using the current settings.

Save & Activate the Destination​

  • Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to Concord, open the destination resource menu, and select Activate.

    The Nexset data will not be sent to Concord until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.