Actions101
- Attendance Actions
- Client Actions
- Department Actions
- Designation Actions
- Employee Actions
- Holiday Actions
- KPI Actions
- KPI Category Actions
- KPI Data Actions
- Lead Actions
- Leave Actions
- OKR Key Result Actions
- OKR Objective Actions
- Performance Cycle Actions
- Project Actions
- Project Category Actions
- Task Actions
- Task Category Actions
- Ticket Actions
- Ticket Agent Actions
- Ticket Channel Actions
- Ticket Type Actions
Overview
The node provides integration with the Flowyteam API to manage various resources related to organizational and project management. Specifically, for the Project Category resource with the Update operation, it allows users to update the details of an existing project category by specifying its ID and new name.
This node is beneficial in scenarios where project categories need to be maintained dynamically within workflows, such as updating category names to reflect changes in project structuring or correcting naming errors without manual intervention in the Flowyteam system.
Example use case:
A project manager automates the renaming of a project category after a reorganization, ensuring all projects linked to that category remain consistent with the updated naming convention.
Properties
| Name | Meaning |
|---|---|
| Category ID | The unique identifier of the project category to update (required). |
| Update Category Name | The new name to assign to the specified project category. |
Output
The node outputs JSON data representing the updated project category object returned from the Flowyteam API. This typically includes fields such as the category's ID, updated name, and possibly other metadata related to the project category.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Flowyteam API.
- Requires an API authentication token credential configured in n8n to authorize requests.
- The node depends on the Flowyteam API endpoints for project category updates.
Troubleshooting
Common issues:
- Invalid or missing Category ID: The API will reject requests if the category ID does not exist or is not provided.
- Insufficient permissions: The API key used must have rights to update project categories.
- Network or API downtime: Connectivity issues can cause failures.
Error messages:
"The operation 'update' is not supported for Project Category resource": This indicates a misconfiguration or unsupported operation; ensure the correct resource and operation are selected.- API error responses indicating invalid input or authorization failure should be checked and resolved by verifying credentials and input parameters.
Links and References
- Flowyteam API Documentation (general reference for API endpoints and authentication)
- n8n documentation on Creating Custom Nodes