Short answer: Drop the "FlowLu → Create FlowLu Task" 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 |
|---|---|---|---|
Task Name name | string | Required | Name of the task |
Description description | string | Optional | Task description |
Assignee ID assignee_id | string | Optional | User ID to assign the task to |
Project ID project_id | string | Optional | Project to add the task to |
Priority priority | string | Optional | Task priority: 0 (low), 1 (normal), 2 (high), 3 (urgent) |
Due Date due_date | string | Optional | Due date (YYYY-MM-DD) |
{"name": "{{trigger.name}}","description": "{{trigger.description}}","assignee_id": "e.g. 5","project_id": "e.g. 10","priority": "1"}
{"id": 102,"name": "Design mockups","status": 1,"due_date": "2025-04-01","priority": 2,"project_id": 10,"assignee_id": 5,"description": "Create UI mockups for the landing page","created_date": "2025-03-15 10:00:00"}
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.