Short answer: Drop the "Wrike → Create Task" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Folder ID folder_id | string | Required | — |
Title title | string | Required | — |
Description description | string | Optional | — |
Status status | options | Optional | — |
Importance importance | options | Optional | — |
Responsible User IDs responsibles | array | Optional | — |
Due Date due_date | string | Optional | YYYY-MM-DD |
{"folder_id": "{{trigger.folder_id}}","title": "{{trigger.title}}","description": "{{trigger.description}}","status": "{{trigger.status}}","importance": "{{trigger.importance}}"}
{"data": [{"id": "ABCD","title": "Follow up","status": "Active","permalink": "https://www.wrike.com/..."}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.