Actions32
- Assignment Actions
- Client Actions
- Project Actions
- Report Actions
- Task Actions
- Time Actions
- Timecard Actions
- Webhook Actions
Overview
This node interacts with the Everhour API to manage assignments related to users and projects. Specifically, the "Delete Assignment" operation allows you to remove an existing assignment by its ID. This is useful in scenarios where a user is no longer assigned to a project or task, or when cleaning up outdated or incorrect assignment data.
Practical examples:
- Automatically removing a user's assignment from a project when they leave a team.
- Cleaning up assignments that were created by mistake.
- Managing project resources dynamically by deleting assignments as project scopes change.
Properties
| Name | Meaning |
|---|---|
| User ID | The numeric ID of the user associated with the assignment operations (required). |
| Assignment ID | The numeric ID of the specific assignment to delete (required). |
Output
The output JSON contains a simple confirmation object indicating success:
{
"success": true
}
This confirms that the assignment was successfully deleted. There is no binary data output.
Dependencies
- Requires an API key credential for authenticating requests to the Everhour API.
- The node uses the Everhour API base URL configured in the credentials.
- Network access to the Everhour API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing assignment ID will cause the deletion to fail.
- Incorrect or expired API authentication token will result in authorization errors.
- Network connectivity problems can prevent the API call from succeeding.
Error messages:
- Errors returned from the API are caught and reported. If "Continue On Fail" is enabled, the error message will be included in the output JSON under an
errorfield. - Typical error might be "Assignment not found" if the provided assignment ID does not exist.
- Authentication errors indicate issues with the API key or permissions.
- Errors returned from the API are caught and reported. If "Continue On Fail" is enabled, the error message will be included in the output JSON under an
Resolution:
- Verify that the assignment ID is correct and exists.
- Ensure the API key credential is valid and has sufficient permissions.
- Check network connectivity and API endpoint availability.