FreeloInstall

Summary

Creates a new subtask under an existing Freelo task, using a declarative POST with the name and optional scheduling, priority, comment and tracking-user fields.

Inputs

• Task Name or ID (TaskId) (required) — Parent task. Pick from a searchable list or enter a numeric task ID (digits only), which can be an expression.
• Task Name (required) — Name of the new subtask, sent as name in the request body.
• Additional Fields > Due Date — Due date for the subtask, sent as due_date.
• Additional Fields > Due Date End — End of a date range, sent as due_date_end. Used together with Due Date.
• Additional Fields > Priority — High (h), Medium (m) or Low (l), sent as priority_enum. None omits the field.
• Additional Fields > Comment — Initial comment text, sent as comment.content.
• Additional Fields > Tracking User Names or IDs — Users to track the subtask, chosen from a list or given as custom IDs. Sent as tracking_users_ids.
• Request Options — Node settings for batching (items per batch, interval), SSL certificate bypass, proxy and timeout (default 10000 ms).

Output shape

The API response for the created subtask, returned as an item for each input item.

The source pack contains only signature stubs, so the exact response fields are not visible. The properties declare the request as routing-based, with no custom output shaping. The properties' displayOptions reference createSubTask and SubTask, which differ from the 'Create' and 'Sub Task' labels. The wiring may therefore be inconsistent, so verify the operation shows its fields in the UI.

Examples

Example 1: Add a checklist step to a task when a ticket is escalated

Select the parent task by ID using an expression, set Task Name to 'Escalation review', and set Priority to High.

Example 2: Create a dated subtask with an initial comment and assignee tracking

Set Task Name, Due Date and Due Date End, add a Comment, and choose Tracking Users.

Links

• n8n community nodes installation guide