ClientifyInstall

Summary

Create a Clientify task by sending the provided task details to the /tasks/ endpoint. Each incoming n8n item triggers a separate request; map values from prior steps as needed. Empty optional values, nulls, and numeric zero are omitted from the request to avoid sending default n8n values. The operation now includes parsing and merging a JSON body field if defined in the operation catalog.

Inputs

• Type (required) — Set Owner (can be mapped from previous steps).
• Name (required) — Set Assigned To (can be mapped from previous steps).
• Owner — Set Type (can be mapped from previous steps).
• Assigned To — Set Name (can be mapped from previous steps).
• Description — Set Description (can be mapped from previous steps).
• Remarks — Set Remarks (can be mapped from previous steps).
• Due Date — Set Due Date (can be mapped from previous steps).
• Status — Set Status (can be mapped from previous steps).
• Recurring Type — Set Recurring Type (can be mapped from previous steps).
• Recurring End Date — Set Recurring End Date (can be mapped from previous steps).
• Recurring Days Of Week — Set Recurring Days Of Week (can be mapped from previous steps).
• Recurring Interval — Set Recurring Interval (can be mapped from previous steps).
• Priority — Set Priority (can be mapped from previous steps).

Output shape

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

_meta includes the resource, operation, HTTP method, and path. Empty optional values and numeric zero are omitted from the request. If the API response is empty, the output is { "ok": true }; a primitive response is returned under data. With Continue On Fail enabled, failed items instead contain success: false, operation, and error.

Links

• n8n community nodes installation guide