> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Height on Vortex IQ

> Monitor Height performance signals, run automated checks, and prepare approved work through Vortex IQ.

Monitor Height performance signals, run automated checks, and prepare approved work through Vortex IQ.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=height)

<CardGroup cols={5}>
  <Card title="25">
    performance signals
  </Card>

  <Card title="6">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="11">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup cols={2}>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls.
  </Tab>

  <Tab title="Monitor (25)">
    ### Monitor performance

    25 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (24 signals)">
        | Signal                                      | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **Avg Cycle Time (days)**                   | Alert band 3 / 7   | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Lead Time (days)**                    | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Avg Time-to-Fix (days)**                  | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Backlog by Priority**                     | Merchant rule      | Backlog by Priority.                                                                                                                                   |
        | **Backlog by Status**                       | Watch only         | Backlog by Status.                                                                                                                                     |
        | **Blocked Tickets**                         | Alert band 3 / 8   | Tasks flagged blocked / impeded - the operational queue's stuck list.                                                                                  |
        | **Critical Findings Without a Height Task** | Merchant rule      | Critical / high audit findings older than 7 days with no Height task - coverage gap. Auto-dispatch missed these or the merchant disabled it; either wa |
        | **Cycle Time by Priority**                  | Merchant rule      | Cycle Time by Priority.                                                                                                                                |
        | **Finding Resolution Rate (90d)**           | Alert band 75 / 50 | Share of audit findings actually fixed via the Height pipeline. \<50% means we're filing faster than the team drains. Height runs 5-12 pts higher th   |
        | **Finding-to-Task Dispatch Lag**            | Merchant rule      | How fast we get findings into Height after detection. Slow dispatch = cold leads by the time the ops team sees them.                                   |
        | **In Progress**                             | Watch only         | Tasks with status.state = started - work actively in flight.                                                                                           |
        | **Oldest Open (days)**                      | Merchant rule      | Age of the longest-running open task - backlog-rot signal.                                                                                             |
        | **Open Tickets**                            | Merchant rule      | Total open tasks across the connected workspace - top-of-funnel backlog volume.                                                                        |
        | **Overloaded Assignees (>10 open)**         | Alert band 0 / 1   | People with >10 open tasks - capacity bottleneck candidates.                                                                                           |
        | **Scope Added Mid-Sprint**                  | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Sprint Progress**                         | Alert band 80 / 50 | Active-cycle burn - uses Height Cycles, the workspace must have Cycles enabled.                                                                        |
        | **Sprint Velocity (avg)**                   | Merchant rule      | Sprint Velocity (avg) over time.                                                                                                                       |
        | **Throughput Trend**                        | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Tickets Resolved (7d)**                   | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Tickets by Assignee**                     | Merchant rule      | Tickets by Assignee.                                                                                                                                   |
        | **Unassigned Tickets**                      | Alert band 5 / 20  | Description pending editorial review; the signal is live.                                                                                              |
        | **VortexIQ Findings In Progress**           | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **VortexIQ Findings Open**                  | Merchant rule      | Tasks we filed from audit findings that haven't been resolved yet - the live backlog of things VortexIQ surfaced. Calibrated 20% looser than Jira beca |
        | **VortexIQ Findings Resolved**              | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                                                                           |
        | ----------------------------------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Open Height tasks with vortexiq\_finding\_id set, not completed, and lastActivityAt older than 14 days - findings losing money silently. Copilot-accepte |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (6)">
    ### Audit risks and opportunities

    A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail.

    <AccordionGroup>
      <Accordion title="API token / credential expired or about to expire">
        **Severity** critical · **Outcome** Control risk and change · **Fix status** Report only

        Once this credential expires, VortexIQ stops seeing ticket and project activity from this tool entirely, and every backlog, capacity and cycle-time finding here goes stale from that moment, silently, until someone notices the numbers stopped updating.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-AUTH-001`
      </Accordion>

      <Accordion title="VortexIQ finding resolution rate below 50%">
        **Severity** high · **Outcome** Grow revenue · **Fix status** Report only

        Fewer than half of the tickets VortexIQ has created from its audit findings ever get resolved. That means the issues this dashboard surfaces, broken tracking, catalog problems, security gaps, are being logged but not fixed at better than a coin-flip rate, so the audit is producing visibility without

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-RESOLUTION-001`
      </Accordion>

      <Accordion title="VortexIQ-created findings abandoned (>14d no status change)">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 5 tickets VortexIQ created from its own audit findings have sat untouched for over two weeks. Whatever those findings flagged, whether it was a broken tracking pixel, a stockout, or a security gap, is still unresolved, and the audit that caught it is not doing its job if the resulting tick

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-ABANDONED-001`
      </Accordion>

      <Accordion title="Assignee overloaded (>10 open tickets)">
        **Severity** medium · **Outcome** Protect revenue · **Fix status** Report only

        At least one person is carrying more than 10 open tickets at once. Beyond the burnout risk, this usually means their tickets move slower than the team average simply from context-switching, which shows up later as missed deadlines that look unrelated to the real cause.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CAPACITY-001`
      </Accordion>

      <Accordion title="Backlog blocked-tickets count growing">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Blocked tickets grew more than 50% versus the prior period. Blocked work does not disappear, it queues up, so a growth rate this size now usually means a larger backlog crunch and slower delivery in the weeks ahead, once those tickets eventually unblock all at once.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-BACKLOG-001`
      </Accordion>

      <Accordion title="Cycle time degrading > 25% week-over-week">
        **Severity** medium · **Outcome** Run operations · **Fix status** Report only

        Tickets are taking over 25% longer to complete than they did the prior week. A shift this fast usually has a specific, findable cause, catching it this week is far easier than after it has become the new normal and nobody remembers what changed.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `PM-CYCLE-001`
      </Accordion>
    </AccordionGroup>

    #### Build your own automated fixes

    Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **8 read** and **3 write** operations across tasks, lists, activitys, fieldtemplates, taskcomments, users on Height. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words.

    Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution.

    [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=height)

    #### Ready to build your first Height workflow

    Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build.

    <Accordion title="Browse the operations you can build with">
      | Resource       | Read operations | Write operations |
      | -------------- | --------------- | ---------------- |
      | tasks          | 2               | 2                |
      | lists          | 2               | 0                |
      | activitys      | 1               | 0                |
      | fieldtemplates | 1               | 0                |
      | taskcomments   | 0               | 1                |
      | users          | 1               | 0                |
      | workspaces     | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>