Add Comment: Wrike action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Task ID task_id	string	Required	The Task ID assigned by Wrike. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.
Comment Text text	string	Required	—
Plain Text Mode plain_text	options	Optional	—

Sample request

{
  "task_id": "{{trigger.task_id}}",
  "text": "{{trigger.text}}",
  "plain_text": "{{trigger.plain_text}}"
}

Returns

{
  "data": [
    {
      "id": "C123",
      "text": "Comment"
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Add Comment.

What does the Add Comment action do in Wrike?

Adds a comment to a Wrike task with optional @mentions. Use for automation activity logs, status updates, or AI summarization of attachments.

What inputs does Add Comment require?

Required: Task ID, Comment Text. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Wrike returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Add Comment support batch operations?

Yes. Run Add Comment inside a Loop node to process arrays. Tiny Command handles Wrike's rate limits automatically so you don't have to throttle manually.

More actions