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 projects, specifically supporting an "Update" operation for the Project resource. This operation allows users to modify existing project details such as the project name, start date, deadline, status, budget, and other related fields.
This node is beneficial in scenarios where project information needs to be kept current within automated workflows, such as updating project timelines, budgets, or statuses based on external triggers or data changes. For example, a user could automate updating a project's deadline when a related task is delayed or adjust the allocated hours after resource planning.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project to update (required). |
| Update Project Name | The new name to assign to the project. |
| Update Start Date | The new start date for the project, in MM/DD/YYYY format. |
| Update Deadline | The new deadline for the project, in MM/DD/YYYY format. |
| Additional Update Fields | A collection of optional fields to update: |
| - Update Category ID | New category ID for the project. |
| - Update Client ID | New client ID associated with the project. |
| - Update Currency ID | New currency ID used for the project budget. |
| - Update Default Project Member | Boolean indicating whether to add default project members. |
| - Update Hours Allocated | Number representing new hours allocated to the project. |
| - Update Manual Timelog | Boolean indicating if manual timelog is enabled. |
| - Update Notes | New notes or comments about the project. |
| - Update Project Budget | New budget amount for the project. |
| - Update Project ID (Reference) | New reference project ID, possibly linking to another project. |
| - Update Project Summary | New summary description of the project. |
| - Update Status | New status of the project; options include: Cancelled, Finished, In Progress, Not Started, On Hold. |
| - Update Template ID | New template ID to apply to the project. |
| - Update Without Deadline | Boolean indicating whether the project has no deadline. |
Output
The node outputs JSON data representing the updated project object returned from the Flowyteam API. This typically includes all the updated project fields reflecting the changes made by the update operation.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Flowyteam API.
- Requires an API authentication token or API key credential configured in n8n to authorize requests.
- The node depends on the Flowyteam API endpoints for project management.
Troubleshooting
Common Issues:
- Invalid or missing Project ID will cause the update to fail.
- Incorrect date formats for start date or deadline may result in API errors.
- Attempting to update fields with invalid values (e.g., non-existent category or client IDs) can cause failures.
- Network or authentication issues with the Flowyteam API will prevent successful updates.
Error Messages:
- Errors indicating "Project not found" suggest the provided Project ID does not exist.
- Authentication errors indicate missing or invalid API credentials.
- Validation errors from the API may specify which fields have incorrect formats or invalid values.
Resolutions:
- Verify that the Project ID is correct and exists in Flowyteam.
- Ensure dates are formatted as MM/DD/YYYY.
- Confirm that referenced IDs (category, client, currency, template) are valid.
- Check API credentials and network connectivity.
Links and References
- Flowyteam official API documentation (for project management endpoints) — consult for detailed field definitions and constraints.
- n8n documentation on setting up API credentials and using custom nodes.