Short answer: Drop the "Plutio → Create Plutio Project" 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 | Project title |
Description description | string | Optional | Project description |
Due Date dueDate | string | Optional | Project due date (YYYY-MM-DD) |
Status status | string | Optional | Project status |
{"title": "{{trigger.title}}","description": "{{trigger.description}}","dueDate": "2025-06-30","status": "active"}
{"_id": "abc124","title": "Website Redesign","status": "active","dueDate": "2025-06-30","createdAt": "2025-03-15T10:00:00Z","description": "Redesign the company website"}
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.