Short answer: Drop the "Zoho Projects → Create 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 |
|---|---|---|---|
Portal ID portal_id | string | Required | Portal ID. Example: 12345678 |
Project Name name | string | Required | Project Name. Example: Q1 Website Redesign |
Description description | string | Optional | Description |
Start Date start_date | string | Optional | Start Date. e.g. "MM-DD-YYYY" |
End Date end_date | string | Optional | End Date. e.g. "MM-DD-YYYY" |
Owner ID owner_id | string | Optional | Owner ID. Example: 2060758 |
{"portal_id": "e.g. 12345678","name": "e.g. Q1 Website Redesign","description": "{{trigger.description}}","start_date": "MM-DD-YYYY","end_date": "MM-DD-YYYY"}
{"projects": [{"id": "123456","name": "Q1 Website Redesign","status": "active"}]}
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.