---
title: "Wrike"
description: "Read task pages and folder summaries in your authorized Wrike region."
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Wrike

<p>Read task pages and folder summaries in your authorized Wrike region.</p>

<details data-command-index><summary>What you can do (2)</summary>
<h2>What you can do</h2>
<p>Available commands: 2 (2 read, 0 write). Enable only the commands your application needs.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Command</th>
<th>Effect</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://help.tooluse.net/integrations/wrike#command-wrike-tasks-list">List task summaries</a> — <code>wrike.tasks.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/wrike#command-wrike-folders-get">Get folder summary</a> — <code>wrike.folders.get</code></td>
<td>Read</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://www.tooluse.net/tools/integrations/wrike">Connect and use</a></p>
<p>Open the integration&#39;s connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.</p>
<h2>Get your provider credentials</h2>
<p>Follow these steps for Wrike, then enter the issued values in the connection form below.</p>
<ol>
<li>Register an OAuth app in the Wrike App Console at <a href="https://www.wrike.com/frontend/apps/index.html">https://www.wrike.com/frontend/apps/index.html</a> and register <a href="https://api.tooluse.net/v1/oauth/callback">https://api.tooluse.net/v1/oauth/callback</a> exactly. Obtain its client ID and client secret. In My tools &gt; Wrike &gt; Use my provider credentials choose the data-center origin matching your account (US <a href="https://www.wrike.com/">https://www.wrike.com</a> or EU <a href="https://app-eu.wrike.com/">https://app-eu.wrike.com</a>), enter the OAuth client ID and secret, select reads and save, then Sign in to provider. Consent requests wsReadOnly only; no account administration or write scope is requested and no undocumented PKCE is added. The initial exchange must return the same region in host; if it differs, correct the region and reconnect. Saved region edits invalidate consent. Tokens are encrypted and rotating refresh tokens are renewed at the validated regional host, with no automatic retry after an uncertain refresh. List a single task page with pageSize=20; pass its opaque nextPageToken explicitly to continue. For a folder use its API v4 ID, not the numeric ID from a web permalink. Summaries omit descriptions, people, custom fields and financial data. Disconnect locally and revoke the application in Wrike when finished; no unsupported remote revocation endpoint is invented. Customer app registration and any provider review remain external requirements.</li>
</ol>
<p><a href="https://developers.wrike.com/docs/oauth-20-authorization">Official credential setup</a></p>
<h2>Where to enter credentials</h2>
<p>In the integration page, sign in, choose your workspace and open Connect. If a <strong>Credentials</strong> choice is shown, select <strong>Use my credentials</strong>. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Connection field</th>
<th>Requirement</th>
</tr>
</thead>
<tbody><tr>
<td>Wrike data-center origin</td>
<td>Required</td>
</tr>
<tr>
<td>OAuth access token (optional)</td>
<td>Optional</td>
</tr>
<tr>
<td>Wrike OAuth client ID</td>
<td>Optional</td>
</tr>
<tr>
<td>Wrike OAuth client secret</td>
<td>Optional</td>
</tr>
<tr>
<td>Registered OAuth redirect URI (optional)</td>
<td>Optional</td>
</tr>
<tr>
<td>Return URL after authorization</td>
<td>Optional</td>
</tr>
</tbody></table>
</div><p>Open API keys and create a Tooluse.net key for the enabled commands.</p>
<p>Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.</p>
<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Permissions and results</h2>

<p>If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net&#39;s existing permissions. Disabling a connection or revoking a key immediately prevents new calls.</p>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<p>Your connection&#39;s daily allowance and key permissions also apply. Adding a connection does not make a provider request.</p>

<p>Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.</p>

<h2>Call from your client</h2>

<p>Use the shared MCP configuration. Refresh your client&#39;s tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.</p>

<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Discover your enabled tools</h2>

<p>List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.</p>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"
</code></pre>

<p>Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.</p>

<h2>HTTP call</h2>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {
    "query": {
      "pageSize": 20
    }
  }
}'
</code></pre>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<h2>Commands</h2>

<details id="command-wrike-tasks-list">
<summary><span>List task summaries — <code>wrike.<wbr>tasks.<wbr>list</code></span></summary>
<p>Read one explicit page of task IDs, titles, statuses, importance and timestamps in the saved Wrike region. Pass nextPageToken deliberately to continue; no automatic traversal, descriptions, assignees, custom fields or writes.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/wrike?command=wrike.tasks.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.pageSize</code></td>
<td>integer</td>
<td>Required</td>
<td>Tasks requested on this explicit page; choose 20. The response byte budget also applies.</td>
<td><code>minimum: 1; maximum: 100</code></td>
</tr>
<tr>
<td><code>query.nextPageToken</code></td>
<td>string</td>
<td>Optional</td>
<td>Opaque token returned by the preceding task page; omit for the first page.</td>
<td><code>minLength: 1; maxLength: 2048; pattern: &quot;^[^\\r\\n]+$&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/wrike/commands/wrike.tasks.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "pageSize": 20
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-wrike-folders-get">
<summary><span>Get folder summary — <code>wrike.<wbr>folders.<wbr>get</code></span></summary>
<p>Read the ID, title, timestamps and permalink of one existing folder in your saved Wrike region. Excludes descriptions, people, custom fields, finance and writes.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/wrike?command=wrike.folders.get">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.folder_id</code></td>
<td>string</td>
<td>Required</td>
<td>Existing Wrike API v4 folder ID, not the numeric web permalink ID.</td>
<td><code>maxLength: 128; pattern: &quot;^[A-Za-z0-9_-]+$&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/wrike/commands/wrike.folders.get">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "folder_id": "IEAAABCDIETEST123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<h2>Errors</h2>

<p>Check the key&#39;s expiry, revocation, workspace and allowed operations.</p>

<p>Reuse the same idempotency key only for the same request.</p>

<p>The connection or provider limit has been reached. Check the receipt before retrying.</p>

<h2>Test the connection</h2>

<p>Open the integration&#39;s commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client&#39;s tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.</p>

<p><a href="https://developers.wrike.com/docs/oauth-20-authorization">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/wrike/index.mdx