Skip to main content

Height Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a Height location.
height_api.png

Height

Create a Height Destination​

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

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

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

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

    Create Task

    Creates a new task in a specified Height list. Use this endpoint to programmatically populate your Height workspace with tasks generated from external systems — for example, creating Height tasks from bug reports, support tickets, form submissions, or data records from other tools.

    • Enter the List ID of the Height list where the new task should be created. The list ID is required — tasks in Height must belong to a list. To find available list IDs, run the List Lists data source endpoint first and note the ID of the target list.

    • Map the Task Name field to the Nexset attribute that contains the task title. Task names are required and should be concise and descriptive.

    • Optionally, map additional task attributes from your Nexset to the corresponding Height task fields:

      • Description: A detailed description of the task, supporting plain text or markdown.
      • Assignees: One or more Height user IDs to assign the task to. User IDs can be obtained from the List Users endpoint.
      • Due Date: The task due date in ISO 8601 format (e.g., 2025-09-01T00:00:00.000Z).
      • Status: The initial task status. Must be a valid status value defined in your Height workspace.

    The Height API enforces a rate limit of 60 requests per minute for the task creation endpoint (POST /tasks). If your data flow creates a large number of tasks, use Nexla's record batching or scheduling settings to stay within this limit and avoid 429 Too Many Requests errors.

    Update Task

    Updates an existing task in your Height workspace. Use this endpoint to synchronize task data from external systems — for example, updating task statuses, reassigning tasks, changing due dates, or modifying descriptions based on events in other tools.

    • Enter the Task ID of the Height task to be updated in the destination URL. Task IDs are unique identifiers that can be obtained by running the Search Tasks data source endpoint.

    • Map the fields you want to update from your Nexset to the corresponding Height task attributes. Only the fields you include in the request will be updated — existing values for omitted fields will remain unchanged:

      • Name: The updated task title.
      • Description: The updated task description.
      • Status: The updated task status. Must match a valid status option in your Height workspace.
      • Assignees: Updated list of assignee user IDs. Providing an empty array removes all assignees.
      • Due Date: The updated due date in ISO 8601 format.

    Height task updates are performed using PATCH /tasks/{'{taskId}'}. Include only the fields you want to change in the request body — Height uses a partial update (patch) model, so unspecified fields are not modified.

    Post Activity (Task Comment)

    Posts a new activity (message or comment) to a Height task's activity thread. Use this endpoint to add contextual updates, notifications, or status messages to Height tasks from external systems — for example, appending deployment statuses, system alerts, or automated progress updates to relevant tasks.

    • Enter the Task ID of the Height task to which the activity should be posted. Task IDs can be obtained using the Search Tasks data source endpoint.
    • Map the Message field to the Nexset attribute containing the comment text. The message supports plain text content.
    • The activity will appear in the task's comment thread and will be attributed to the Height user associated with the API key used for authentication.

    The Height API enforces a rate limit of 60 requests per minute for the activity creation endpoint (POST /activities). If your flow generates a high volume of comments, use Nexla's scheduling settings to pace requests within this limit.

Configure Manually​

Height destinations can be manually configured to send data to any valid Height API endpoint.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Height 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 Height API from the Method pulldown menu. Common methods for Height write operations include:

    • POST: For creating new records — used for creating tasks (POST /tasks), posting activities (POST /activities), and search operations (POST /tasks/search)
    • PATCH: For partially updating existing records — used for updating tasks (PATCH /tasks/{'{taskId}'})
    • PUT: For replacing entire resource records where supported

Data Format​

  1. Select the format in which the Nexset data will be sent to the Height API from the Content Format pulldown menu. Height's REST API accepts JSON-formatted request bodies — select JSON as the content format. Nexla will automatically convert the data to JSON for each API call.

API Endpoint URL​

  1. Enter the URL of the Height API endpoint to which you want to send the Nexset data in the URL field. Height API endpoints use the base URL https://api.height.app. Some commonly used destination endpoints include:

    • https://api.height.app/tasks — Create a new task (POST)
    • https://api.height.app/tasks/{'{taskId}'} — Update a specific task (PATCH), replacing {'{taskId}'} with the task's unique ID
    • https://api.height.app/activities — Post a new activity or comment to a task (POST)

For update operations, include the task ID at the end of the URL path (e.g., https://api.height.app/tasks/task-id-here). Task IDs can be retrieved using the Height data source with the Search Tasks endpoint.

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

    You do not need to include the Authorization header here — it is automatically applied by Nexla based on your Height credential configuration.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Height destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

    The Height API processes individual task and activity records per request — it does not natively support bulk creation of multiple tasks in a single API call. If batching is enabled, ensure that the batching algorithm and request structure are configured to match the format expected by the target Height endpoint. For most Height write operations, a batch size of 1 (one record per request) is recommended to maintain compatibility with the API's single-record model.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings. Some algorithms require additional settings—click on an algorithm listed below to view instructions for configuring these settings.

Response Webhook​

Optional

Nexla can automatically send the response received from the Height API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call — for example, capturing the newly created task's ID and details for use in downstream flows.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Height API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the Height API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Height API using the current settings.

Save & Activate the Destination​

  • 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 Height endpoint, open the destination resource menu, and select Activate.

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