Actions27
- Project Actions
- Project Task Actions
- User Actions
- Company Actions
Overview
This node integrates with the awork API to create a new project within an awork workspace. It is designed to automate project management workflows by programmatically defining project details such as name, description, dates, type, status, template, and associated company.
Common scenarios where this node is beneficial include:
- Automatically creating projects based on triggers from other systems (e.g., CRM, issue trackers).
- Setting up standardized projects using templates and predefined statuses.
- Associating projects with specific companies for organizational clarity.
Practical example: When a new client is onboarded in a CRM system, this node can be used to automatically create a corresponding project in awork with relevant start/due dates and assign it to the client's company.
Properties
| Name | Meaning |
|---|---|
| Project Name | The name of the project (required). |
| Project Description | A textual description providing more details about the project. |
| Start Date | The date and time when the project is planned to start. |
| Due Date | The deadline or expected completion date for the project. |
| Project Type ID | Identifier specifying the type/category of the project. |
| Project Status ID | Identifier indicating the current status of the project (e.g., active, completed). |
| Project Template ID | Identifier of a project template to base the new project on, enabling standardized setup. |
| Company ID | Identifier of the company to which the project will be linked. |
Output
The node outputs JSON data representing the newly created project object as returned by the awork API. This typically includes all project details such as its unique ID, name, description, dates, type, status, template, company association, and metadata.
If the node supports binary data output, it would generally relate to file attachments or related resources, but for this operation, the output is purely JSON describing the created project.
Dependencies
- Requires an API key credential for authenticating with the awork API.
- The node uses the base URL
https://api.awork.comand expects JSON content-type headers. - Proper permissions on the API key are necessary to create projects.
- No additional external dependencies beyond the awork API.
Troubleshooting
- Missing Required Fields: If "Project Name" is not provided, the node will likely throw a validation error. Ensure all required fields are filled.
- Authentication Errors: Invalid or missing API credentials will cause authentication failures. Verify that the API key is correctly configured and has sufficient permissions.
- Invalid IDs: Providing incorrect or non-existent IDs for project type, status, template, or company may result in API errors. Confirm these IDs exist in your awork account.
- Date Format Issues: Ensure that start and due dates are in valid ISO 8601 format as expected by the API.
- API Rate Limits: Excessive requests might trigger rate limiting; handle retries or backoff accordingly.