Create task with the Wrike API

Creates 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.

Identifier
wrike_create_task

The request

POST https://connect.reportei.com/api/tools/wrike_create_task/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "folderId": "<folderId>",
    "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

ParameterTypeRequiredDescription
folderIdstringYesId of the space, folder or project that will hold the task, from List folders. For a subtask, send the root folder of the account (scope WsRoot) and the parent in superTasks.
titlestringYesTitle of the task.
descriptionstringNoDescription, in plain text or in the limited HTML that Wrike accepts.
statusstringNoStatus of the task. Not available on the Team plan.Values: Active, Deferred, Completed, Cancelled
customStatusstringNoId of a custom status from List workflows, for a workflow status such as In review. Use it instead of status.
importancestringNoImportance of the task.Values: High, Normal, Low
datesstringNoJSON object with the dates of the task: type (Planned, Backlog or Milestone), start and due as yyyy-MM-dd with an optional THH:mm:ss, duration in minutes (one Wrike day is 480), and workOnWeekends. A start needs a due or a duration. Example: {"type":"Planned","start":"2026-11-03","due":"2026-11-07"}.
responsiblesstringNoUsers to assign: JSON array of user ids from List contacts, such as ["KUAJ25LC"].
followersstringNoUsers to add as followers: JSON array of user ids from List contacts, such as ["KUAJ25LC"].
superTasksstringNoTasks to put this one under as a subtask: JSON array of task ids from List tasks, such as ["IEAAAAAAKQAAAAAA"].

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_create_task. It becomes your agent's tool definition with no conversion.

Other Wrike tools

See all 13 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.