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

# Wrike on Vortex IQ

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

Monitor Wrike 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=wrike-api)

<CardGroup cols={5}>
  <Card title="42">
    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="23">
    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="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </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 (42)">
    ### Monitor performance

    42 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 (37 signals)">
        | Signal                                     | Alert behaviour    | What it tracks                                                                                                                                         |
        | ------------------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
        | **API Rate-Limit Headroom**                | Merchant rule      | Wrike throttles per-account; if we approach the limit, finding-creation slows or fails - surfaces here before it bites.                                |
        | **Avg Cycle Time (days)**                  | Alert band 3 / 7   | completedDate − createdDate, averaged over tasks closed in window.                                                                                     |
        | **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 Importance**                  | Merchant rule      | Open task split by Wrike importance (High/Normal/Low) - too many High = no real prioritisation.                                                        |
        | **Backlog by Priority**                    | Merchant rule      | Active tasks grouped by Wrike importance (High / Normal / Low).                                                                                        |
        | **Backlog by Status**                      | Watch only         | Backlog by Status.                                                                                                                                     |
        | **Blocked Tickets**                        | Alert band 3 / 8   | Tasks in a blocked / on-hold custom status - the operational queue's stuck list.                                                                       |
        | **Critical Findings Without a Wrike Task** | Merchant rule      | Critical / high audit findings older than 7 days with no Wrike task - coverage gap. Auto-dispatch missed these or the merchant disabled it; either way |
        | **Cycle Time by Importance**               | Merchant rule      | Cycle Time by Importance.                                                                                                                              |
        | **Cycle Time by Priority**                 | Merchant rule      | Avg cycle time bucketed by Wrike importance.                                                                                                           |
        | **Deferred Tasks**                         | Alert band 3 / 8   | Tasks parked in Deferred - Wrike's stuck/on-hold queue (maps to the archetype blocked-tickets sentiment).                                              |
        | **Finding Resolution Rate (90d)**          | Alert band 75 / 50 | What share of audit findings actually got fixed via the Wrike pipeline. \<50% means we're filing faster than the team drains.                          |
        | **Finding-to-Task Dispatch Lag**           | Merchant rule      | How fast we get findings into Wrike after detection. Slow dispatch = cold leads by the time the team sees them.                                        |
        | **Hours Logged (7d)**                      | Watch only         | Total tracked hours from the timelog endpoint - capacity-utilisation signal for billable teams.                                                        |
        | **In Progress**                            | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Oldest Open (days)**                     | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Open Tasks**                             | Merchant rule      | Total Active tasks across the account - top-of-funnel backlog volume.                                                                                  |
        | **Open Tickets**                           | Merchant rule      | Total active tasks across the default space - top-of-funnel backlog volume from GET /tasks.                                                            |
        | **Overdue Projects**                       | Merchant rule      | Projects past endDate that are not yet Completed.                                                                                                      |
        | **Overloaded Assignees (>10 open)**        | Alert band 0 / 1   | People with >10 open tasks - capacity bottleneck candidates.                                                                                           |
        | **Projects Newly Gone Red**                | Merchant rule      | Projects that flipped to Red status in the last day - escalate before the next status meeting.                                                         |
        | **Projects by Status**                     | Watch only         | Green / Yellow / Red / On-Hold split across all active projects.                                                                                       |
        | **Rate-Limit Exhausted**                   | Merchant rule      | Wrike is throttling us - finding dispatch will stall. Back off bulk-create and warn the merchant.                                                      |
        | **Scope Added Mid-Sprint**                 | Merchant rule      | Tasks added to the active project folder after its start date.                                                                                         |
        | **Sprint Progress**                        | Alert band 80 / 50 | % of the active project folder's tasks completed vs schedule. Wrike Projects stand in for sprints.                                                     |
        | **Sprint Velocity (avg)**                  | Merchant rule      | Completed tasks per project cycle, last 5 projects.                                                                                                    |
        | **Tasks Completed (7d)**                   | Merchant rule      | Description pending editorial review; the signal is live.                                                                                              |
        | **Tasks by Assignee**                      | Merchant rule      | Tasks by Assignee.                                                                                                                                     |
        | **Throughput Trend**                       | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
        | **Tickets Resolved (7d)**                  | Merchant rule      | Tasks completed in the last 7 days vs the prior 7 (completedDate filter).                                                                              |
        | **Tickets by Assignee**                    | Merchant rule      | Active tasks per responsible contact - capacity distribution.                                                                                          |
        | **Unassigned Tasks**                       | Alert band 5 / 20  | Description pending editorial review; the signal is live.                                                                                              |
        | **Unassigned Tickets**                     | Alert band 5 / 20  | Active tasks with an empty responsibleIds list - work nobody owns.                                                                                     |
        | **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 completed yet - the live backlog of things VortexIQ surfaced.                                     |
        | **VortexIQ Findings Resolved**             | Watch only         | Description pending editorial review; the signal is live.                                                                                              |
      </Accordion>

      <Accordion title="Protect revenue (3 signals)">
        | Signal                                    | Alert behaviour   | What it tracks                                                                                              |
        | ----------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------- |
        | **Abandoned Findings (>14d no movement)** | Alert band 5 / 15 | Findings sat in the backlog with no status change for two weeks - these are the ones losing money silently. |
        | **Abandoned-Findings Burst**              | Alert band 5 / 15 | Sudden spike in findings hitting the 14d abandonment threshold - capacity issue or process breakdown.       |
        | **Projects At Risk (Red)**                | Merchant rule     | Projects flagged Red - actively behind or blocked. The headline answer to 'what's at risk this morning?'.   |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                          | Alert behaviour | What it tracks                                                                                                             |
        | ------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------- |
        | **Wrike Token Expiry Imminent** | Merchant rule   | If the OAuth token expires we silently stop creating tasks - every audit finding goes into the void. Surface 7 days early. |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal            | Alert behaviour | What it tracks                                                      |
        | ----------------- | --------------- | ------------------------------------------------------------------- |
        | **Overdue Tasks** | Merchant rule   | Active tasks past dueDate - slippage signal feeding project health. |
      </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, 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, 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, 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, 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, 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, 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 **16 read** and **7 write** operations across tasks, foldertasks, contacts, folders, taskcomments, workflows on Wrike. 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=wrike-api)

    #### Ready to build your first Wrike 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        | 4               | 3                |
      | foldertasks  | 1               | 2                |
      | contacts     | 2               | 0                |
      | folders      | 2               | 0                |
      | taskcomments | 0               | 2                |
      | workflows    | 2               | 0                |
      | accounts     | 1               | 0                |
      | comments     | 1               | 0                |

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