Actions27
- Project Actions
- Project Task Actions
- User Actions
- Company Actions
Overview
This node integrates with the awork API to create a new task within a specified project. It is designed for automating task management workflows by programmatically adding tasks to projects, which can help teams streamline project planning and tracking.
Common scenarios include:
- Automatically creating tasks when new projects are initiated.
- Adding predefined tasks based on templates or triggers from other systems.
- Scheduling tasks with specific due dates and durations as part of workflow automation.
For example, when a new client project is created in your system, this node can automatically add initial setup tasks with assigned types and statuses, ensuring consistent project kickoff procedures.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project where the task will be created. |
| Task Name | The name/title of the task to be created. |
| Task Description | A detailed description of what the task entails (optional). |
| Type of Work ID | Identifier specifying the type/category of work for the task (e.g., development, design). |
| Task Status ID | Identifier representing the current status of the task (e.g., open, in progress). |
| Due Date | The deadline by which the task should be completed (date and time). |
| Planned Duration | Estimated time planned to complete the task, expressed in seconds. |
Output
The node outputs JSON data representing the newly created task object as returned by the awork API. This typically includes all task details such as its ID, name, description, type of work, status, due date, planned duration, creation timestamps, and any other metadata provided by the API.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the task, but this operation focuses on JSON task data only.
Dependencies
- Requires an active connection to the awork API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for API calls is
https://api.awork.com. - Proper permissions on the API key to create tasks within projects.
Troubleshooting
- Missing Required Fields: Errors may occur if mandatory fields like Project ID, Task Name, Type of Work ID, or Task Status ID are not provided. Ensure these inputs are correctly set.
- Authentication Errors: If the API key is invalid or missing, the node will fail to authenticate. Verify that the API credential is correctly configured and has sufficient permissions.
- Invalid IDs: Providing incorrect or non-existent project, type of work, or status IDs will cause API errors. Double-check these identifiers against your awork account.
- Date Format Issues: The due date must be in a valid datetime format; otherwise, the API may reject the request.
- API Rate Limits: Excessive requests might trigger rate limiting; consider adding delays or error handling for retries.