ClientifyInstall

Summary

Creates a Clientify task by sending a POST request to /tasks/. Provide the required task name and type; optionally include ownership, assignment, details, due date, status, recurrence, and priority.

Inputs

• Name (required) — Task name.
• Type (required) — Numeric task or activity type.
• Owner — Numeric owner ID; omitted when left at its default of 0.
• Assigned To — Numeric assignee ID; omitted when left at its default of 0.
• Description — Task description.
• Remarks — Task remarks.
• Due Date — Task due date.
• Status — Numeric task status; omitted when left at its default of 0.
• Recurring Type — Numeric recurrence type; omitted when left at its default of 0.
• Recurring End Date — End date for a recurring task.
• Recurring Days Of Week — Days of the week for recurrence; accepts an expression.
• Recurring Interval — Numeric recurrence interval; omitted when left at its default of 0.
• Priority — Numeric priority; omitted when left at its default of 0.

Output shape

A single output item per input item, containing the Clientify response fields and a _meta object.

_meta includes the resource, operation, HTTP method, and request path. If Clientify returns no body, the item contains { "ok": true } plus _meta; primitive responses are wrapped in data. With Continue On Fail enabled, a failed item instead contains success: false, the operation, and an error message.

Links

• n8n community nodes installation guide