Actions26
- Project Actions
- Project Task Actions
- User Actions
- Company Actions
Overview
This node allows you to create a new "Type of Work" within the "Project Task" resource in Awork via its API. This is useful for teams managing projects in Awork who want to automate the creation of custom work types, such as categorizing tasks or defining specific workflows. For example, you might use this node to automatically add a new type of work when onboarding a new project template.
Properties
| Display Name | Type | Meaning |
|---|---|---|
| Name | String | The name of the new Type of Work. This is required and identifies the entity. |
| Description | String | (Optional) A description providing more details about this Type of Work. |
| Icon | String | The icon representing this Type of Work. This is required. |
Output
The output will be a JSON object containing the details of the newly created Type of Work. Typical fields may include:
{
"id": "string",
"name": "string",
"description": "string",
"icon": "string",
// ...other metadata returned by the Awork API
}
Dependencies
- Awork API: Requires an active Awork account.
- API Key: You must configure n8n with valid Awork API credentials (
aworkApi). - n8n Configuration: No additional configuration is needed beyond setting up the credentials.
Troubleshooting
- Missing Required Fields: If "Name" or "Icon" are not provided, the node will likely throw a validation error. Ensure all required fields are filled.
- Authentication Errors: If your API key is missing or invalid, you may receive authentication errors from the Awork API. Double-check your credentials in n8n.
- API Rate Limits: Excessive requests may trigger rate limiting on the Awork API. If you see errors related to too many requests, try reducing the frequency of node execution.