Search tasks with the Wrike API
Searches the tasks of the whole account, such as the tasks assigned to someone or due this week, up to 1000 per page. When the response brings nextPageToken, send it to fetch the next page.
- Identifier
- wrike_search_tasks
The request
POST https://connect.reportei.com/api/tools/wrike_search_tasks/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"title": "<title>"
}
}Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| title | string | No | Only tasks whose title contains this text. |
| status | string | No | Only tasks in these statuses: JSON array of statuses, any of Active, Deferred, Completed and Cancelled, such as ["Active"]. |
| importance | string | No | Only tasks with this importance.Values: High, Normal, Low |
| responsibles | string | No | Only tasks assigned to any of these users: JSON array of user ids from List contacts, such as ["KUAJ25LC"]. |
| customStatuses | string | No | Only tasks in these custom statuses: JSON array of custom status ids from List workflows, such as ["IEAAAAAAJMAAAAAA"]. |
| startDate | string | No | Start date filter: JSON object with an exact date in equal, or a range in start and end, as yyyy-MM-dd with an optional THH:mm:ss, such as {"start":"2026-11-01","end":"2026-11-30"}. |
| dueDate | string | No | Due date filter: JSON object with an exact date in equal, or a range in start and end, as yyyy-MM-dd with an optional THH:mm:ss, such as {"start":"2026-11-01","end":"2026-11-30"}. |
| createdDate | string | No | Created date filter: JSON object with start and end in UTC, as yyyy-MM-ddTHH:mm:ssZ, such as {"start":"2026-11-01T00:00:00Z","end":"2026-11-30T23:59:59Z"}. |
| updatedDate | string | No | Updated date filter: JSON object with start and end in UTC, as yyyy-MM-ddTHH:mm:ssZ, such as {"start":"2026-11-01T00:00:00Z","end":"2026-11-30T23:59:59Z"}. |
| completedDate | string | No | Completed date filter: JSON object with start and end in UTC, as yyyy-MM-ddTHH:mm:ssZ, such as {"start":"2026-11-01T00:00:00Z","end":"2026-11-30T23:59:59Z"}. |
| type | string | No | Only tasks of this type: Planned has dates, Backlog has none, Milestone has only a due date.Values: Planned, Backlog, Milestone |
| subTasks | boolean | No | True to also search the subtasks. |
| sortField | string | No | Field the tasks are sorted by.Values: Status, Importance, UpdatedDate, CreatedDate, Title, StartFinishInterval, DueDate, LastAccessDate, CompletedDate |
| sortOrder | string | No | Sort order.Values: Asc, Desc |
| pageSize | integer | No | Tasks per page, up to 1000. |
| nextPageToken | string | No | The nextPageToken of the previous response, to fetch the next page. Send the same fields again. |
| fields | string | No | JSON array of optional fields to add to each task, such as ["responsibleIds","description","customFields"]. Assignees and description only come when asked here. |
| permalink | string | No | Permalink of a task, as Wrike shows it, to find that one. |
Supported connections
Your customer connects their Wrike account once, with one of the modes below. The same connection serves every tool of the toolkit.
OAuth with your product's app
You register your product's OAuth app once, with POST /api/merchants/credentials/wrike, and your customer authorizes the account on a consent screen. Connect renews the token when it is about to expire.
When connecting, your customer also enters {host}: the address of their account on the app's API.
The response
On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.
Ready for AI agents
This tool's input is a JSON Schema, available at GET /api/tools/wrike_search_tasks. It becomes your agent's tool definition with no conversion.
Other Wrike tools
- List foldersGETLists the spaces, folders and projects of the account. Without filters it returns the whole folder tree, with the id, title, childIds and scope of each item, the root folder of the account included (scope WsRoot). Any filter returns a flat list with the full fields, including the status and dates of projects, up to 1000 per page.
- Create folderPOSTCreates a folder inside a space, folder or project, or a project when project is sent. Requires title. Lists and objects go as JSON text.
- Update folderPUTUpdates the fields sent of a folder or project and keeps the others, such as the title, the project status, dates and owners, or the folders that hold it. Lists and objects go as JSON text.
- List tasksGETLists the tasks of a space, folder or project, up to 1000 per page. When the response brings nextPageToken, send it to fetch the next page.
- Get taskGETReturns one or more tasks with their description, assignees, dates, status, custom status, the folders that hold them, custom fields and subtasks.
- Create taskPOSTCreates a task in a space, folder or project. Requires title. Without dates the task goes to the backlog. Lists and objects go as JSON text.
- Update taskPUTUpdates the fields sent of a task and keeps the others. To complete it, send status Completed or a custom status of the Completed group. Lists and objects go as JSON text.
- Delete taskDELETEMoves a task to the Recycle Bin. Update task with restore true brings it back.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
