Short answer: Drop the "Plutio → Create Plutio 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 |
|---|---|---|---|
Title title | string | Required | Task title |
Project ID projectId | string | Optional | Project to add the task to |
Description description | string | Optional | Task description |
Due Date dueDate | string | Optional | Task due date (YYYY-MM-DD) |
Priority priority | string | Optional | Task priority: low, normal, high, urgent |
{"title": "{{trigger.title}}","projectId": "e.g. abc123","description": "{{trigger.description}}","dueDate": "2025-04-15","priority": "normal"}
{"_id": "task002","title": "Create wireframes","status": "active","dueDate": "2025-04-15","priority": "high","createdAt": "2025-03-15T10:00:00Z","projectId": "abc123"}
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.