awork icon

awork

Automate your workflows with the awork API

Actions26

Overview

The Create Project operation in the "awork" n8n node allows users to create a new project within the awork platform via its API. This node is useful for automating project management workflows, such as onboarding new clients, initiating internal projects, or integrating project creation with other business processes (e.g., when a deal is closed in a CRM, automatically create a corresponding project in awork).

Example scenarios:

  • Automatically create a new project when a sales opportunity is won.
  • Set up recurring projects with predefined types and statuses.
  • Integrate project creation into onboarding workflows for new customers.

Properties

Below are the input properties supported by the Create Project operation:

Display Name Type Meaning
Project Name String The name of the project. (Required)
Project Description String A description providing details about the project.
Start Date DateTime The date when the project is scheduled to start.
Due Date DateTime The deadline or due date for the project.
Project Type ID String The identifier for the type/category of the project. (Required)
Project Status ID String The identifier for the current status of the project. (Required)

Output

The node outputs a json object containing the details of the newly created project as returned by the awork API. The structure typically includes fields such as:

{
  "id": "string",
  "name": "string",
  "description": "string",
  "startDate": "string (ISO 8601)",
  "dueDate": "string (ISO 8601)",
  "projectTypeId": "string",
  "projectStatusId": "string",
  // ...other project metadata fields provided by awork
}

Note: The exact output fields depend on the awork API response.

Dependencies

  • External Service: Requires access to the awork API.
  • API Key: You must configure valid awork API credentials in n8n under the credential type aworkApi.
  • n8n Configuration: No additional configuration required beyond setting up credentials.

Troubleshooting

Common Issues:

  • Missing Required Fields: If "Project Name", "Project Type ID", or "Project Status ID" are not provided, the node will fail to create a project.
  • Invalid Dates: Providing incorrectly formatted dates for "Start Date" or "Due Date" may result in errors from the API.
  • Authentication Errors: Invalid or missing awork API credentials will cause authentication failures.

Common Error Messages:

  • "400 Bad Request": Usually indicates missing or invalid input data. Double-check required fields and data formats.
  • "401 Unauthorized": Indicates issues with API credentials. Ensure your awork API key is correct and has sufficient permissions.
  • "404 Not Found": May occur if provided IDs (e.g., Project Type ID or Status ID) do not exist in your awork account.

How to resolve:

  • Verify all required fields are filled.
  • Check that date fields use the correct format (ISO 8601).
  • Confirm that the provided IDs correspond to existing entities in awork.
  • Re-authenticate or update your awork API credentials in n8n if you encounter authorization errors.

Links and References

Discussion