Skip to main content

Klue 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 Klue location.
klue_api.png

Klue

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 Klue connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Klue instance, and click Next; or, create a new Klue credential for use in this flow.

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

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

Endpoint Settings​

  • Select the endpoint to which this destination will send 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 destination for this endpoint.

    Ingest Card (Create/Update)

    This endpoint creates a new Card (POST) or updates an existing Card (PUT with id) in your Klue workspace. Supports auto-creation of Boards via competitorUrl and association with Battlecards, Lanes, and tags. Use this endpoint when you need to create or update competitive intelligence cards, sync card data from other systems, or automate card management workflows.

    • This endpoint accepts JSON data in the request body. The data should include card fields such as title, content, competitor information, battlecard associations, lanes, and tags. When creating a new card, use POST method. When updating an existing card, include the card ID in the data and use PUT method.
    • The endpoint supports auto-creation of Boards via the competitorUrl field. If a Board doesn't exist for the specified competitor, it will be created automatically.
    • You can associate cards with Battlecards, Lanes, and tags by including the appropriate fields in the request body. Refer to the Klue API documentation for the complete list of supported fields and their formats.

    This endpoint uses POST method for creating new cards and PUT method for updating existing cards. The endpoint accepts JSON data in the request body and does not support batch mode, so each record will be sent as a separate API request. For more information about the Ingest Card endpoint, refer to the Klue API Documentation.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can send a sample of the data that will be sent according to the current settings. This allows users to verify that the destination 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 sent & the response will be displayed in the Endpoint Test Result panel on the right.

  • If the test is not successful or the response 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 response to ensure that the destination is configured correctly.

Configure Manually​

Klue destinations can be manually configured to send data to any valid Klue 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 Klue destinations, such as destinations that send data to multiple endpoints or destinations that require custom authentication headers or request parameters.

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 Klue API from the Method pulldown menu. The most common methods are:

    • POST: For creating new resources (most Klue ingestion endpoints use POST)
    • PUT: For updating existing resources

API Endpoint URL​

  1. Enter the URL of the Klue API endpoint to which this destination will send data in the Set API URL field. This should be the complete URL including the protocol (https://) and any required path parameters. Klue API endpoints typically follow the pattern https://app.klue.com/ingest/{resource}.json for ingestion endpoints.

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. Klue API endpoints require Bearer token authentication in the Authorization header.

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). Additional headers are often required for API versioning, content type specifications, or custom authentication requirements.

    You do not need to include any headers already present in the credentials. Common headers like Authorization, Content-Type, and Accept are typically handled automatically by Nexla based on your credential configuration. For Klue, the Authorization header with Bearer token is automatically included from your credential, and Content-Type is typically set to application/json for ingestion endpoints.

Request Body Template​

Optional

  • If the API endpoint requires a specific request body format, you can customize how Nexla formats the data before sending it to the Klue API by entering a request body template in the Request Body Template field. The template should use {message.json} to include the entire record as JSON, or you can specify individual fields using dot notation (e.g., {message.field_name}).

    For most Klue ingestion endpoints, the default request body template {message.json} will work correctly, sending the entire record as JSON. You may need to customize the template if the API requires a specific structure or if you need to transform the data before sending.

Endpoint Testing​

After configuring all settings for the selected endpoint, Nexla can send a sample of the data that will be sent according to the current configuration. This allows users to verify that the destination 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 sent & the response will be displayed in the Endpoint Test Result panel on the right.

  • If the test is not successful or the response 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 response to ensure that the destination is configured correctly.

Save & Activate the Destination​

  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 Klue destination. Nexla will now begin sending data to the configured endpoint according to your data flow schedule.