Gainsight CS NXT Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to a Gainsight CS NXT location.

Gainsight CS NXT

Create a Gainsight CS NXT Destination

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

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

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

   Gainsight CS NXT destinations can also be configured manually, allowing you to send data to Gainsight CS NXT 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 Gainsight CS NXT endpoints. Each template is designed specifically for the corresponding Gainsight CS NXT endpoint, making destination setup easy and efficient.

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

  Insert one or more companies

  Insert one or more records into the Company object.

  • This endpoint automatically inserts one or more company records into your Gainsight CS NXT account using data from your Nexset. No additional configuration is required beyond selecting this endpoint template.
  • The endpoint uses POST requests to https://{base_url}/v1/data/objects/Company. The endpoint URL is automatically constructed based on your Gainsight CS NXT API base URL from the credential configuration.
  • The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each batch of records will be sent as a JSON object containing a records array with the company data to insert.
  • Batch mode is enabled for this endpoint. Records are automatically batched into groups of 50 records per request. If you need to insert multiple companies, you can send multiple records, and they will be automatically batched for efficient processing.
  • This endpoint does not automatically create a data source to track the responses received from the Gainsight CS NXT API after each call.

  The request body must be properly formatted JSON that matches the Gainsight CS NXT API specification for inserting companies. The request body is automatically transformed to include a records array containing your Nexset data. The endpoint requires API Access Key authentication via the Accesskey header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is enabled by default (batch.mode: true) with a batch size of 50 records per request. For detailed information about inserting companies, including required fields, field names, and request formats, see the Gainsight CS NXT API documentation.

  Insert one or more custom object records

  Insert one or more records into a custom object.

  • Enter the API name of the custom object to insert records into in the Custom Object Name field. This should be the API name of the custom object (e.g., CustomObjectName__gc). The default value is CustomObjectName__gc if not specified.

  • The endpoint uses POST requests to https://{base_url}/v1/data/objects/{object_name}. The endpoint URL is automatically constructed based on your Gainsight CS NXT API base URL from the credential configuration and the custom object name.
  • The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each batch of records will be sent as a JSON object containing a records array with the custom object data to insert.
  • Batch mode is enabled for this endpoint. Records are automatically batched into groups of 50 records per request. If you need to insert multiple custom object records, you can send multiple records, and they will be automatically batched for efficient processing.
  • This endpoint does not automatically create a data source to track the responses received from the Gainsight CS NXT API after each call.

  Custom object names should be the API name of the custom object (typically ending with __gc). The request body must be properly formatted JSON that matches the Gainsight CS NXT API specification for inserting custom object records. The request body is automatically transformed to include a records array containing your Nexset data. The endpoint requires API Access Key authentication via the Accesskey header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is enabled by default (batch.mode: true) with a batch size of 50 records per request. For detailed information about inserting custom object records, including required fields, field names, and request formats, see the Gainsight CS NXT API documentation.

Configure Manually

Gainsight CS NXT destinations can be manually configured to send data to any valid Gainsight CS NXT 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 Gainsight CS NXT destinations, such as destinations that use custom request headers, different HTTP methods, or custom data formatting.

Content Format

1. Select the format in which the Nexset data will be sent to the Gainsight CS NXT API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. The Gainsight CS NXT API typically uses JSON format for request bodies.

API Endpoint URL

2. Enter the URL of the Gainsight CS NXT API endpoint to which you want to send the Nexset data in the URL field. This should be the complete URL including the protocol (https://) and any required path parameters. Gainsight CS NXT API endpoints typically follow the pattern https://{yourcompany}.gainsightcloud.com/v1/{endpoint_path} where {yourcompany} is your company identifier from the credential configuration.

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 endpoint requires API Access Key authentication via the Accesskey header, which is handled automatically by your credential configuration. For detailed information about Gainsight CS NXT API endpoints and available APIs, see the Gainsight CS NXT API documentation.