Wrike

Developer tools

Wrike for AI agents. Managed auth, ready-made tools.

List, create and update tasks, browse folders and add comments in Wrike on behalf of each of your users.

About Wrike

With the Wrike connector, your agent works in each user’s own Wrike workspace. It can list and read tasks, create or update a task, browse folders and projects, and read or add comments, using only the tools your project allows.

Wrike is a work management platform for planning projects and tracking tasks across teams.

Tools

What your agent can do in Wrike.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Wrike connection.

  • List tasks

    Read
    wrike_list_tasks

    List tasks with their status and due dates.

  • Get a task

    Read
    wrike_get_task

    Read a task's details.

  • Create a task

    Write
    wrike_create_task

    Create a task in a folder or project.

  • Update a task

    Write
    wrike_update_task

    Change a task's status, dates or assignees.

  • List folders

    Read
    wrike_list_folders

    List the folders and projects in the workspace.

  • List comments

    Read
    wrike_list_comments

    Read the comments on a task.

  • Add a comment

    Write
    wrike_add_comment

    Comment on a task.

Control

Limits you can set.

You decide what your agent may do in Wrike, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let the agent read tasks and add comments, and switch off wrike_update_task so it can never change a task.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use, for example reading the workspace but not editing it. A call outside them is refused.

Get started

Connect Wrike
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect Wrike

    Each end user authorizes their own Wrike account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own Wrike account, once.
    const connection = await agent200
      .user("user_123")
      .connect("wrike");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the Wrike tools

    Name the user, the model and the tools. The model decides which Wrike tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "What tasks are due this week in the Website project",
        tools: ["wrike"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, on Wrike's own sign-in page. You never see or store their Wrike password.

  • What access is requested

    The scopes the connection needs, such as reading the workspace or reading and writing it, listed on Wrike's authorization screen. Users can remove the app later from their Wrike account settings.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Wrike connector and how to use it.

Agent brief
Connector: Wrike, through Agent200. In code: "wrike".
What it does: List, create and update tasks, browse folders and add comments in Wrike on behalf of each of your users.
Page: https://www.agent200.com/connectors/wrike/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Wrike's own page, through the authorization link Agent200 returns. Never ask a user for a Wrike password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: wrike_list_tasks, wrike_get_task, wrike_list_folders, wrike_list_comments. Write tools: wrike_create_task, wrike_update_task, wrike_add_comment. Name "wrike" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/wrike/framework/claude/
   https://www.agent200.com/connectors/wrike/framework/chatgpt/
   https://www.agent200.com/connectors/wrike/framework/claude-code/
   https://www.agent200.com/connectors/wrike/framework/muse/
   https://www.agent200.com/connectors/wrike/framework/grok-bot/
   https://www.agent200.com/connectors/wrike/framework/openai-dots/
   https://www.agent200.com/connectors/wrike/framework/claude-duet/
   https://www.agent200.com/connectors/wrike/framework/hermes-agent/
   https://www.agent200.com/connectors/wrike/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /connectors/wrike.md

Guides

Use Wrike with the AI you build on.

Step-by-step setup for Wrike with a specific model, assistant or agent framework.

FAQ

Wrike and Agent200, answered.

Who handles the Wrike OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Wrike.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Wrike connection, never another user's. It cannot reach anything the user or Wrike has not authorized.

Can I limit what my agent can do in Wrike?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • GitHub

    GitHub

    Read repositories and work with issues and pull requests as the connected user.

    Managed OAuth Developer tools
  • GitLab

    GitLab

    Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.

    Managed OAuth Developer tools
  • Bitbucket

    Bitbucket

    List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.

    Managed OAuth Developer tools
  • Jira

    Jira

    Search, create and transition Jira issues for the connected user.

    Managed OAuth Developer tools
200 OK

Start with Wrike.
Your agent does the rest.

Your users connect their own Wrike accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)