Actions26
- Project Actions
- Project Task Actions
- User Actions
- Company Actions
Overview
This n8n node integrates with the awork API, enabling users to automate workflows involving projects, tasks, users, and companies within the awork platform. The node is designed as a generic entry point for various awork resources and operations, making it suitable for scenarios such as project management automation, task tracking, user administration, and company data synchronization.
Practical examples:
- Automatically create or update projects in awork when new records are added to your CRM.
- Sync tasks between awork and other project management tools.
- Manage user accounts or company information programmatically from n8n workflows.
Properties
| Display Name | Type | Description | Required |
|---|---|---|---|
| Type | String | The type of this entity | Yes |
- Type: Specifies the type of entity being processed by the node. This property is required and determines how the node interacts with the awork API.
Output
The node outputs a json field containing the response from the awork API based on the selected resource and operation. The exact structure of the output will depend on the specific resource (e.g., Project, Task, User, Company) and operation chosen, but generally, it will reflect the corresponding awork API response for the requested action.
Dependencies
- External Service: Requires access to the awork API.
- API Key: You must configure valid awork API credentials in n8n under the name
aworkApi. - n8n Configuration: No additional configuration is needed beyond setting up the credentials.
Troubleshooting
Common Issues:
- Missing or Invalid Credentials: If the awork API credentials are not set up correctly in n8n, the node will fail to authenticate.
- Incorrect "Type" Value: Providing an invalid value for the "Type" property may result in errors or unexpected behavior.
- API Rate Limits: Excessive requests to the awork API may trigger rate limiting.
Common Error Messages:
"401 Unauthorized": Indicates missing or incorrect API credentials. Ensure that theaworkApicredential is properly configured in n8n."400 Bad Request": Usually caused by invalid input parameters. Double-check the "Type" property and any other required fields for correctness."429 Too Many Requests": The awork API rate limit has been exceeded. Wait before retrying or reduce the frequency of requests.