Klue

Klue is a competitive intelligence platform that helps sales and marketing teams track competitors, create battlecards, and manage competitive intelligence. The Klue connector enables you to extract competitive intelligence data including Cards, Battlecards, and Usage Data, and ingest Cards with support for Boards, Lanes, and Battlecards. This connector is particularly useful for applications that need to extract competitive intelligence, analyze competitor information, track battlecard usage, or integrate Klue data with other business systems.

Power end-to-end data operations for your Klue API with Nexla. Our bi-directional Klue connector is purpose-built for Klue, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Klue or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Klue workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Klue credential, you'll need to obtain an API key from your Klue account. Klue API keys are created and managed by Klue Admins in the Apps & Integrations section of your Klue workspace.

To obtain a Klue API key:

1. Log in to your Klue account at https://app.klue.com or your organization's Klue instance.

2. Navigate to Settings (typically accessible from the user menu or workspace settings).

3. In the Settings menu, locate and click on Apps & Integrations or API to access the API configuration page.

4. On the Apps & Integrations page, you'll find options to create or manage API keys. Klue uses Bearer token authentication for API access.

5. Click Create API Key or Generate New Key to create a new API key for your application. You may need to provide a name or description for the API key.

6. Copy the API key immediately after generation, as it may only be displayed once for security purposes. Store it securely, as you'll need it to authenticate API requests.

API keys in Klue are managed by Klue Admins. If you don't have admin access, you'll need to contact your Klue administrator to create an API key for you. The API key is used as a Bearer token in the Authorization header for all API requests.

For detailed information about Klue API authentication and API key management, refer to the Klue API Overview Documentation.

Authenticate

Credentials required

API Key authentication using Bearer token. API keys are created and managed by Klue Admins in the Apps & Integrations section.

Field	Required	Secret	Description
API Key	Yes	Yes	Your Klue API Key (Bearer Token) created by Klue Admins in Apps & Integrations section.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Klue

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. In the API Key field, enter the API key that you obtained from your Klue Apps & Integrations settings. This is the Bearer token used to authenticate requests to the Klue API.

   The API key is sensitive information and should be kept secure. If you've lost your API key, you'll need to generate a new one in your Klue Apps & Integrations settings. API keys are used in the Authorization header as a Bearer token for all API requests.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Klue connector tile, then select the credential that will be used to connect to the Klue API, and click Next; or, create a new Klue credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Klue API endpoints. 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.

Extract Cards

This endpoint returns published Cards (drafts if audiences=curators) from your Klue workspace. Supports filtering by audiences, battlecards, competitors, topics, tags, IDs, and date ranges. Use this endpoint when you need to extract competitive intelligence cards for analysis, reporting, or integration with other systems.

• Optionally, enter the page number for pagination in the Page Number field. The default value is 1. This endpoint uses pagination to handle large datasets efficiently.
• Optionally, enter the number of Cards to return per page in the Results Per Page field. The default value is 100. You can adjust this value based on your needs and API rate limits.
• Optionally, enter filters as a query string in the Optional Filters field. Filters can include audiences, battlecards, competitors, topics, tags, IDs, and date ranges. Example: &audiences[]=everyone&battlecards[]=Sales&createdAfter=2024-01-01T00:00:00Z. You can combine multiple filters using the & separator.

This endpoint uses pagination to handle large datasets efficiently. The endpoint automatically fetches additional pages using incrementing page numbers, ensuring all Cards matching your filters are retrieved. For more information about the Extract Cards endpoint, refer to the Klue API Documentation.

Extract Battlecards

This endpoint returns metadata about published battlecards including structure, competitor associations, and card IDs. Use this endpoint to get context before fetching card content. Use this endpoint when you need to extract battlecard metadata for analysis, reporting, or integration with other systems.

• Optionally, enter the page number for pagination in the Page Number field. The default value is 1. This endpoint uses pagination to handle large datasets efficiently.
• Optionally, enter the number of Battlecards to return per page in the Results Per Page field. The default value is 100. You can adjust this value based on your needs and API rate limits.
• Optionally, enter filters as a query string in the Optional Filters field. Filters can include IDs, competitors, creation dates, and other criteria. Example: &ids[]=123&competitors[]=CompanyX&createdAfter=2024-01-01T00:00:00Z. You can combine multiple filters using the & separator.

This endpoint returns battlecard metadata including structure, competitor associations, and card IDs. Use the "Extract Cards" endpoint to retrieve the actual card content. For more information about the Extract Battlecards endpoint, refer to the Klue API Documentation.

Usage Data - Events

This endpoint returns user event activity logs (card views, clicks, actions) from your Klue workspace. Updated daily at 00:00 UTC with a 3-day delay. Use this endpoint when you need to extract usage analytics, track user engagement, or analyze battlecard performance.

• Enter the date for usage data in ISO 8601 format (YYYY-MM-DD) in the Date (Required) field. Example: 2024-10-01. The default value is {now-3dd}, which retrieves data from 3 days ago. Data is updated daily at 00:00 UTC with a 3-day delay, so ensure you're requesting data that is at least 3 days old.

This endpoint returns user event activity logs including card views, clicks, and actions. The data is updated daily at 00:00 UTC with a 3-day delay, so recent data may not be immediately available. For more information about the Usage Data - Events endpoint, refer to the Klue API Documentation.

Usage Data - Sessions

This endpoint returns user session logs (entry page, exit page, session duration) from your Klue workspace. Updated daily at 00:00 UTC with a 3-day delay. Use this endpoint when you need to extract session analytics, track user behavior, or analyze workspace usage patterns.

• Enter the date for usage data in ISO 8601 format (YYYY-MM-DD) in the Date (Required) field. Example: 2024-10-01. The default value is {now-3dd}, which retrieves data from 3 days ago. Data is updated daily at 00:00 UTC with a 3-day delay, so ensure you're requesting data that is at least 3 days old.

This endpoint returns user session logs including entry page, exit page, and session duration. The data is updated daily at 00:00 UTC with a 3-day delay, so recent data may not be immediately available. For more information about the Usage Data - Sessions endpoint, refer to the Klue API Documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Klue data sources can also be manually configured to ingest data from any valid Klue API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Klue API endpoints typically follow the pattern https://app.klue.com/extract/{resource}.json for extraction endpoints or https://api.klue.com/connect/reports/{resource}.json for usage data endpoints, and require Bearer token authentication in the Authorization header, which Nexla adds automatically based on your Klue credential. Common paths to data include $ for the entire response or $.results for results arrays.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Klue 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.

Use as a destination

Click the + icon on the Nexset that will be sent to the Klue destination, and select the Send to Destination option from the menu. Select the Klue connector from the list of available destination 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.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Klue API endpoints. 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.

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.

Manual configuration

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, such as destinations that send data to multiple endpoints or that require custom authentication headers or request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Klue API endpoints typically follow the pattern https://app.klue.com/ingest/{resource}.json for ingestion endpoints, and require Bearer token authentication in the Authorization header, which Nexla adds automatically based on your Klue credential. The Content-Type: application/json header is typically included automatically for ingestion endpoints. For most Klue ingestion endpoints, the default request body template {message.json} sends the entire record as JSON; customize it if the API requires a different structure.

Save & activate

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 send the data to the configured Klue endpoint, open the destination resource menu, and select Activate.

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