Skip to content
  • There are no suggestions because the search field is empty.

Wrike Integration: Sync Projects & Tasks into Cascade

Automatically align Wrike projects and tasks with Cascade objectives

Overview

The Wrike Integration allows you to automatically sync Wrike Projects and Tasks into Cascade so your strategic plan stays aligned with execution.

Instead of manually updating progress in Cascade, this integration ensures that:

  • Project updates in Wrike automatically reflect in Cascade
  • Task completion updates strategic progress
  • Project metadata (dates, owners, status) stays in sync
  • Custom fields can be mapped across systems

This creates a single source of truth between strategic planning (Cascade) and execution (Wrike).

How It Works

There are two supported sync methods:

Option 1 — Scheduled Pull (Most Common)

Cascade pulls Wrike data on a defined schedule (e.g., hourly or daily) and updates corresponding Objectives and Actions.

Option 2 — Webhook-Based Updates

Wrike sends updates to Cascade when changes occur in real-time.

Cascade stores Wrike’s unique IDs (not names) to ensure mappings remain stable even if titles change.

Authentication

Option A — Permanent Access Token (fastest, best for POC)

Use when: you want to stand up a proof-of-concept quickly or you’re okay with the integration running under a single Wrike user identity.

Refer to the following link to setup a Permanent Access Token:
https://help.wrike.com/hc/en-us/articles/210409445-Wrike-API

Customer steps (Wrike UI)

  1. In Wrike, click your profile image (sidebar).
  2. Go to Apps & Integrations.
  3. Open the API
  4. Select an existing API app (or create one) and Generate a permanent token.
    • Save it securely — it’s typically shown once.
    • You can revoke and regenerate if needed.

What the customer provides to Cascade

  • A Permanent Access Token
  • Confirmation of what Spaces/Projects the token-user can access (permissions)

The integration runs under the identity of the token owner.

Option B — OAuth 2.0 (recommended for production)

Use when: you want a scalable, secure integration where the customer authorizes access through Wrike’s standard OAuth flow (recommended for long-term deployments).

Refer to the following link to setup OAuth 2.0:
https://developers.wrike.com/oauth-20-authorization/

Wrike’s API uses OAuth 2.0 authorization code flow.

Customer steps

  1. Create / configure a Wrike API application in the Wrike App Console (this generates a Client ID and Client Secret).
  2. Configure the redirect/callback URL provided by Cascade (your team supplies this).
  3. Complete the OAuth authorization step (customer logs in, approves access).

What the customer provides to Cascade

  • The Client ID / Client Secret and confirm the redirect URI is configured

Wrike API requests are authorized via the Authorization header using an OAuth access token.


Syncing the Data

Select the Wrike Space

Wrike Spaces act as the top-level container.

Customer provides:

  • Space name(s) to integrate

(Cascade retrieves the Space ID automatically.)

Select Projects to Sync

Projects within the selected Space will map to Cascade Objectives.

Customer provides:

  • Which Wrike Projects to sync
  • Where they map inside Cascade (Plan / Focus Area)
  • Any project-level custom fields to sync

Select Tasks to Sync

Tasks inside selected Projects typically map to Cascade Actions.

Customer provides:

  • Confirmation of task structure
  • Status mapping logic (Wrike → Cascade)
  • Any task-level custom fields to sync

Store the Cascade Action ID inside a Wrike custom field to maintain stable mapping.

Scheduling & Sync Logic

Most integrations run on a fixed schedule (e.g., hourly or daily).

Best Practices:

  • Scope to selected Spaces/Projects only
  • Avoid syncing unnecessary historical tasks
  • Confirm ownership mapping rules

Cascade updates items based on Wrike IDs, ensuring title changes do not break mappings.

What We Need From You (Checklist)

For fastest implementation, please provide:

  • Authentication method (PAT or OAuth)
  • Space name(s) to integrate
  • Project list to sync
  • Mapping location inside Cascade
  • Status mapping rules
  • Custom fields to sync
  • Desired sync frequency

Troubleshooting

  • Projects/Tasks not appearing – Confirm the integration user has access to the selected Space/Projects and that items are not archived.

     

  • Status not updating – Verify Wrike status mapping to Cascade was configured correctly.

     

  • Custom fields not syncing – Ensure the field was included in the approved sync scope and exists in the selected Space.

     

  • Authentication errors – Check that the token is active (PAT) or that OAuth credentials and redirect URL are correctly configured.

     

  • Delayed updates – Confirm the scheduled sync frequency or webhook configuration.