Skip to main content

Cue Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a sync or streaming data flow that sends data to a Cue location.
cue_api.png

Cue

Create a Cue Destination​

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

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

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

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

    Save Contact

    This endpoint saves contacts to your Cue account. Use this endpoint when you need to create or update contacts in your Cue account from your data sources.

    • This endpoint automatically saves contacts to your Cue account. No additional configuration is required beyond selecting this endpoint template.
    • The endpoint uses POST requests to {api_url}/v1/contacts where {api_url} is your Cue API URL from the credential configuration. The endpoint URL is automatically constructed based on the Cue API base URL.
    • The endpoint sends data from your Nexset as the request body in JSON format. Each record in your Nexset will be sent as a JSON object containing the contact data to save. The request body should follow the Cue API specification for saving contacts, including required fields and field names.
    • Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to save a contact. If you need to save multiple contacts, you can send multiple records, but each will be processed as a separate request.

    The request body must be properly formatted JSON that matches the Cue API specification for saving contacts. The endpoint requires JWT/Token authentication with custom headers (X-Api-Consumer and X-Cue-UserId) and an Authorization header, which are handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about saving contacts, including required fields, field names, and request formats, see the Cue API documentation.

    Save Account

    This endpoint saves accounts to your Cue account. Use this endpoint when you need to create or update accounts in your Cue account from your data sources.

    • This endpoint automatically saves accounts to your Cue account. No additional configuration is required beyond selecting this endpoint template.
    • The endpoint uses POST requests to {api_url}/v1/accounts where {api_url} is your Cue API URL from the credential configuration. The endpoint URL is automatically constructed based on the Cue API base URL.
    • The endpoint sends data from your Nexset as the request body in JSON format. Each record in your Nexset will be sent as a JSON object containing the account data to save. The request body should follow the Cue API specification for saving accounts, including required fields and field names.
    • Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to save an account. If you need to save multiple accounts, you can send multiple records, but each will be processed as a separate request.

    The request body must be properly formatted JSON that matches the Cue API specification for saving accounts. The endpoint requires JWT/Token authentication with custom headers (X-Api-Consumer and X-Cue-UserId) and an Authorization header, which are handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about saving accounts, including required fields, field names, and request formats, see the Cue API documentation.

Configure Manually​

Cue destinations can be manually configured to send data to any valid Cue 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 Cue 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 Cue API from the Method pulldown menu. The Cue API primarily uses POST requests for data writing operations. The most common methods are:

    • POST: For creating new resources or performing actions (e.g., saving contacts, saving accounts)
    • PUT: For updating existing data
    • PATCH: For partial updates to existing data
    • DELETE: For removing data

Data Format​

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

API Endpoint URL​

  1. Enter the URL of the Cue 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. Cue API endpoints typically follow the pattern {api_url}/v1/{endpoint_path} where {api_url} is your Cue API URL 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 JWT/Token authentication with custom headers (X-Api-Consumer and X-Cue-UserId) and an Authorization header, which are handled automatically by your credential configuration. For detailed information about Cue API endpoints and available APIs, see the Cue API documentation.

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. The Cue API requires JWT/Token authentication with custom headers (X-Api-Consumer and X-Cue-UserId) and an Authorization header, which are handled automatically by your credential configuration. The Content-Type: application/json header is typically set automatically for JSON request bodies.

Request Body​

Optional

  • If the API endpoint requires a specific request body format, configure how Nexla should format the request body from your Nexset data. The request body can be sent as JSON, XML, or form data, depending on the API endpoint requirements.

    • For JSON format, select JSON from the Request Body Format dropdown, and the Nexset data will be sent as a JSON object in the request body. Cue API endpoints typically use JSON format for request bodies.

    • For XML format, select XML from the Request Body Format dropdown, and the Nexset data will be converted to XML format in the request body.

    • For Form data format, select Form Data from the Request Body Format dropdown, and the Nexset data will be sent as form-encoded data in the request body.

Save the Destination​

  1. Once all configuration steps have been completed, click the Save button to save your destination configuration.

  2. The destination will now be available in your data flow and will begin sending data to the Cue endpoint according to the configured settings.