Actions27
- Project Actions
- Project Task Actions
- User Actions
- Company Actions
Overview
This node integrates with the awork API to automate workflow management related to projects and tasks. Specifically, for the "Project Task" resource and the "Create Type of Work" operation, it allows users to create a new "Type of Work" entity within a project task context. This is useful for categorizing or defining different types of work items or activities in project management.
Practical examples include:
- Creating a new type of work such as "Design", "Development", or "Testing" to classify tasks.
- Adding descriptive metadata and icons to visually distinguish types of work in project dashboards.
- Automating the setup of project templates by programmatically adding predefined types of work.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the type of work to be created (required). |
| Description | A textual description providing more details about this type of work (optional). |
| Icon | The icon representing this type of work, used for visual identification (required). |
Output
The node outputs JSON data representing the newly created "Type of Work" entity. This typically includes fields such as the unique identifier, name, description, icon, and any other metadata returned by the awork API for the created entity.
If the node supports binary data output, it would generally relate to file attachments or media associated with the type of work, but based on the provided code and properties, no binary output is indicated.
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 requests is
https://api.awork.com. - HTTP headers include standard JSON content type and a custom header identifying the originating app.
Troubleshooting
- Authentication errors: Ensure that the API key or token credential is correctly set up and has sufficient permissions.
- Validation errors: Missing required fields like "Name" or "Icon" will cause the API to reject the request. Make sure these are provided.
- Network issues: Verify network connectivity to
https://api.awork.comand that no firewall or proxy blocks the requests. - API limits: If you encounter rate limiting, consider implementing retries or checking your API usage quota.
Links and References
- awork API Documentation – Official API docs for detailed endpoint information.
- n8n Documentation – For guidance on setting up credentials and using HTTP Request nodes.