Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "Wrike" |
| 4 | description: "Public support knowledge for Wrike." |
| 5 | category: "authentication" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-06-24T00:00:00Z" |
| 8 | tags: |
| 9 | - "wrike" |
| 10 | --- |
| 11 | # Wrike |
| 12 | |
| 13 | |
| 14 | ## Use the Wrike user id, not the account id, when assigning or updating task users |
| 15 | |
| 16 | For Wrike task update or assignment fields, pass the Wrike user `id` value rather than the `accountId`. Wrike validates the user identifier shown in the user object, not the account identifier. |
| 17 | |
| 18 | ## Wrike task responses expose multiple user-id fields and can resolve names |
| 19 | |
| 20 | Wrike task data can contain several user-id fields, including `authorIds`, `responsibleIds`, `sharedIds`, and `followerIds`. For fetch-task results, use the `resolve_user_names` parameter, which is enabled by default, to return those ids along with their names. If identifying the creator specifically, check `authorIds`. |
| 21 | |
| 22 | ## Assignee is not a native field in Wrike fetch-task API responses |
| 23 | |
| 24 | Do not expect a separate `assignee` field from the Wrike tasks API or the corresponding fetch-tasks tool. Wrike represents user relationships through id arrays such as responsible/user fields instead of a top-level `assignee` field. |
| 25 | |
| 26 | ## Use the Composio proxy endpoint or SDK executeRequest for direct Wrike API calls |
| 27 | |
| 28 | For direct Wrike API calls through an existing Composio connected account, call the Composio proxy endpoint with the Wrike path and method, for example `endpoint: "/tasks"`, `method: "GET"`, and the `connected_account_id`. In SDK code, the same pattern can be done with `toolset.client.actions.executeRequest({ connectedAccountId, endpoint: "/tasks", method: "GET", parameters: [] })`. Ensure endpoint values are quoted strings. |
| 29 | |
| 30 | ## Pass entityId as a string when getConnections returns 404 in v3 SDK flows |
| 31 | |
| 32 | When using v3 SDK connection APIs, pass the `entityId` as a string. If the code stores the value as `enterpriseId`, pass it through the SDK entity helper, for example `.getEntity("enterpriseId")`. Also use a current v3 SDK package rather than an older release candidate. |
| 33 | |
| 34 | ## Use the latest Wrike toolkit version for nested folder pagination |
| 35 | |
| 36 | For Wrike folder APIs, avoid the base `00000000_00` toolkit version when dealing with nested folders. Retry with `latest` so the request uses the current nested-folder pagination behavior. |