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
Department → Delete
AI-generatedOverview
This node provides integration with the Flowyteam API to manage company departments, among other resources. Specifically, the Delete Department operation allows users to remove a department from their organization by specifying its unique ID. This is useful for automating organizational changes, cleaning up obsolete departments, or managing departmental data programmatically.
Practical examples include:
- Automatically deleting a department when it is no longer active.
- Integrating with HR systems to sync department removals.
- Cleaning up test or temporary departments created during workflows.
Properties
| Name | Meaning |
|---|---|
| Department ID | ID of the department to delete |
The "Department ID" property is required and must be a number representing the unique identifier of the department you want to delete.
Output
The output of this operation is JSON data representing the result of the delete request. Typically, this will confirm whether the deletion was successful or provide details about the deleted department. The exact structure depends on the Flowyteam API response but generally includes status information.
This node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Flowyteam API.
- The node depends on the Flowyteam API being accessible and the provided credentials having sufficient permissions to delete departments.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Department ID will likely cause an error.
- Insufficient permissions in the API key may prevent deletion.
- Network or API downtime can cause request failures.
Error messages:
- Errors indicating "department not found" suggest the Department ID does not exist.
- Authentication errors indicate problems with the API key or credentials.
- Timeout or connection errors suggest network issues.
Resolutions:
- Verify the Department ID is correct and exists.
- Ensure the API key has delete permissions.
- Check network connectivity and Flowyteam API status.
Links and References
- Flowyteam API Documentation (general reference for API endpoints and authentication)
- n8n documentation on creating custom nodes