Actions26
- Project Actions
- Project Task Actions
- User Actions
- Company Actions
Overview
The Project Task: Create Task operation in this custom n8n node allows users to create a new task within a specified project using the awork API. This is useful for automating project management workflows, such as programmatically adding tasks when certain triggers occur (e.g., when a new client is onboarded or a milestone is reached). For example, you could use this node to automatically generate a set of onboarding tasks for every new project created in your system.
Properties
Below are the input properties supported by this operation:
| Display Name | Type | Meaning |
|---|---|---|
| Project ID | String | The unique identifier of the project where the task will be created. (Required) |
| Task Name | String | The name/title of the new task. (Required) |
| Task Description | String | A description providing more details about the task. |
| Type of Work ID | String | The identifier for the type of work associated with the task. (Required) |
| Task Status ID | String | The identifier representing the status of the task. (Required) |
| Due Date | DateTime | The due date and time for the task's completion. |
| Planned Duration | Number | The planned duration for the task, in seconds. |
Output
The output of this operation will be a JSON object containing the details of the newly created task as returned by the awork API. While the exact structure depends on the API response, it typically includes fields such as:
{
"id": "string",
"name": "string",
"description": "string",
"projectId": "string",
"typeOfWorkId": "string",
"taskStatusId": "string",
"dueDate": "string (ISO 8601)",
"plannedDuration": number,
...
}
Additional fields may be present depending on the awork API's response.
Dependencies
- External Service: Requires access to the awork API.
- API Key: You must configure valid awork API credentials in n8n under the credential type
aworkApi. - n8n Configuration: No special environment variables are required beyond standard credential setup.
Troubleshooting
- Missing Required Fields: If any required property (Project ID, Task Name, Type of Work ID, Task Status ID) is missing, the node will likely throw an error indicating which field is absent.
- Invalid IDs: Providing incorrect or non-existent IDs (for project, type of work, or status) may result in errors from the awork API, such as "Not Found" or "Invalid ID".
- Authentication Errors: If the API key is missing or invalid, you may see authentication errors like "401 Unauthorized". Ensure your credentials are correctly configured in n8n.
- Date Format Issues: The Due Date should be in a valid ISO 8601 format; otherwise, the API may reject the request.