WrikeWay Back to WrikeWay
Documentation

Wrike API Connector for Power Automate

Definition files and setup guide for building a custom Wrike API connector inside Microsoft Power Automate Online.

Overview

This connector wraps the Wrike REST API so you can drop Wrike's project-management capabilities straight into your automated Power Automate workflows. The folder ships several OpenAPI (formerly Swagger) definition files — you only need to import one of them to create the connector.

You need a Power Automate environment with rights to create custom connectors, plus the ability to register an app in the Wrike Developers Portal to obtain OAuth credentials.

Definition files in this folder

Download the file you intend to import into Power Automate.

Custom-crafted connector

Recommended JSON

The primary OpenAPI definition built by the WPP Wrike Global Team. Tailored to common team integration needs — a curated subset of the full Wrike API.

Download JSON

Custom-crafted connector

YAML

The YAML version of the custom connector — functionally identical to the JSON file, provided for tooling or preference that favours YAML.

Download YAML

Native Wrike API v4 connector

YAML

Based on the complete, officially published Wrike API v4 specification. Offers a more comprehensive set of actions mapping directly to the native API.

Download YAML

Which file should I use?

  • For most standard team use cases, start with the custom-crafted WrikeAPI-PAO-Connector.json.
  • If you need an endpoint not present in the custom version, use the native WrikeAPI-Native-PAO-Connector.yaml — or reach out to the team to add it to the curated connector.
  • The YAML files are alternatives if your tooling or preference favours YAML over JSON.

How to use

To use these files, create a new custom connector in your Power Automate environment.

  1. 1

    Create an API app in Wrike

    Register an application in Wrike to obtain a Client ID and Client Secret before creating the connector.

    1. Log in to Wrike and go to the Apps & Integrations section.
    2. Open the Wrike Developers Portal and create a new app.
    3. Set the Redirect URI to the value Power Automate provides in the next steps. A common initial placeholder is https://global.consent.azure-apim.net/redirect.
    4. Once created, securely copy the Client ID and Client Secret.
  2. 2

    Import the connector in Power Automate

    1. Navigate to Power Automate.
    2. In the left menu, go to Data › Custom connectors.
    3. Top-right, click New custom connector and select Import an OpenAPI file.
    4. Name the connector (e.g. "Wrike API Custom") and upload your chosen .json or .yaml file from this folder.
    5. Click Continue.
  3. 3

    Configure the connector

    General tab

    The API host and base URL pre-fill from the definition (e.g. app-eu.wrike.com and /api/v4). You can upload a connector icon here.

    Security tab

    • Select OAuth 2.0 as the Authentication type.
    • Choose Wrike as the Identity Provider. If it isn't listed, use Generic Oauth 2.
    • Enter the Client ID and Client Secret from Wrike.
    • Set the Authorization URL to https://login.wrike.com/oauth2/authorize/v4.
    • Set the Token URL and Refresh URL to https://login.wrike.com/oauth2/token.
    • Power Automate now generates the Redirect URL. Copy it and paste it into the Redirect URI field of your app in the Wrike Developers Portal.

    Definition tab

    Review the imported actions (API endpoints). Adjust summaries, descriptions, and visibility as needed.

    Create connector

    Click Create connector at the top.

  4. 4

    Test the connector

    Go to the Test tab and create a new connection. You'll be prompted to log in to Wrike and authorize the app. Once connected, test the various actions to confirm they work correctly.

Built by the WPP Enterprise Technology · Wrike Team

Back to WrikeWay