Actions32
- Assignment Actions
- Client Actions
- Project Actions
- Report Actions
- Task Actions
- Time Actions
- Timecard Actions
- Webhook Actions
Overview
This node integrates with the Everhour API to manage time entries and other related resources such as clients, projects, tasks, users, and more. Specifically, for the Time resource with the Delete operation, it allows users to delete a specific time entry by its ID.
Common scenarios where this node is beneficial include:
- Automating time tracking cleanup by removing incorrect or obsolete time entries.
- Integrating with other systems to synchronize time data and remove entries when necessary.
- Managing time entries programmatically in bulk workflows.
For example, you might use this node to delete a time entry after a task is canceled or if a user logs time incorrectly and needs to remove that record from Everhour.
Properties
| Name | Meaning |
|---|---|
| Time Entry ID | The ID of the time entry to delete. |
Output
The output JSON contains a simple confirmation object indicating success:
{
"success": true
}
This confirms that the specified time entry was successfully deleted.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the Everhour API.
- The node uses the Everhour API base URL configured in the credential.
- Network access to the Everhour API endpoint is required.
Troubleshooting
- Invalid or missing Time Entry ID: Ensure the "Time Entry ID" property is correctly set and corresponds to an existing time entry.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions to delete time entries.
- API rate limits or network issues: If requests fail due to rate limiting or connectivity, retry after some time or check network settings.
- Error messages from the API: The node will throw errors if the API returns failure responses; review the error message for details (e.g., "Not Found" if the time entry does not exist).
To resolve common errors:
- Double-check input parameters.
- Confirm API credentials.
- Review Everhour API documentation for permission requirements.