Skip to main content

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 Qualtrics location.
qualtrics_api.png

Qualtrics

Create a Qualtrics Destination​

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

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

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

    Qualtrics destinations can also be configured manually, allowing you to send data to Qualtrics 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 Qualtrics endpoints. Each template is designed specifically for the corresponding Qualtrics 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.

    Trigger JSON Event

    This endpoint template triggers Qualtrics Workflows by routing data to Qualtrics JSON Events using records from a Nexset. Use this template when you need to trigger Qualtrics workflows or actions based on data from your Nexset. Check out the API documentation link to view examples.

    • Enter the Qualtrics JSON Event endpoint URL in the Qualtrics JSON Event Endpoint URL field. This should be the endpoint URL for the Qualtrics JSON Event. You can find this URL in your Qualtrics JSON Event Action Tab. The endpoint URL determines which Qualtrics JSON Event will be triggered.

    This endpoint sends data as JSON in the request body to trigger Qualtrics JSON Events in your Qualtrics account. Each record from your Nexset will be sent as a separate API request to trigger a JSON Event in Qualtrics. The request body should contain the event data in the format required by the Qualtrics JSON Event.

    The event structure must match the Qualtrics JSON Event's expected format. You can find the JSON Event endpoint URL in your Qualtrics JSON Event Action Tab. For detailed information about JSON Events, request body formats, available event properties, and workflow triggering, see the Qualtrics API documentation and Qualtrics JSON Events documentation.

Configure Manually​

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

Using manual configuration, you can also configure Nexla to automatically send the response received from the Qualtrics 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 Qualtrics API from the Method pulldown menu. Qualtrics API typically uses POST method for creating resources and triggering events.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Qualtrics API from the Content Format pulldown menu. Qualtrics API expects JSON format for all requests.

API Endpoint URL​

  1. Enter the URL of the Qualtrics API endpoint to which data will be sent in the URL field. This should be the complete URL including your datacenter hostname (from your credential), the API path, and any required query parameters. Include any required path parameters in the URL.

Ensure the API endpoint URL is correct and accessible with your current credentials. The Qualtrics API endpoint URL should point to the endpoint where you want to trigger events or create resources. The endpoint URL should include your datacenter hostname and the appropriate API path. You can test the endpoint using the Test button after configuring the URL.

Request Body​

  1. Configure the request body that will be sent to the Qualtrics API. The request body should contain the resource data formatted as JSON, with field names matching the Qualtrics API's expected structure. The request body format is typically {message.json} to send the entire Nexset data as JSON, or you can construct a custom JSON structure with specific field mappings.

The request body must be valid JSON and must match the Qualtrics API's expected format for the specific endpoint you're using. Qualtrics API uses specific structures for different endpoints (JSON Events, surveys, etc.). For detailed information about request body formats, available endpoints, and resource structures, see the Qualtrics API documentation.

Save the Destination​

  1. Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the destination configuration for later use.