Short answer: Drop the "Zoho People → Add Employee" 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 |
|---|---|---|---|
Employee ID EmployeeID | string | Required | Employee ID. Example: HRM02 |
First Name FirstName | string | Required | First Name. e.g. "John" |
Last Name LastName | string | Required | Last Name. e.g. "Doe" |
Email EmailID | string | Required | Email. e.g. "john@company.com" |
Department Department | string | Optional | e.g. "e.g. Engineering" |
Designation Designation | string | Optional | e.g. "e.g. Senior Developer" |
{"EmployeeID": "e.g. HRM02","FirstName": "John","LastName": "Doe","EmailID": "john@company.com","Department": "e.g. Engineering"}
{"response": {"result": {"pkId": "759415000000240001"},"status": 0,"message": "Successfully Added"}}
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.