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 projects and other related resources such as clients, tasks, time entries, users, and more. Specifically for the Project - Delete operation, it allows you to delete a project by specifying its unique Project ID.
Common scenarios where this node is beneficial include automating project lifecycle management within your workflows, such as cleaning up completed or obsolete projects automatically, or integrating project deletion into larger automation processes involving project data synchronization or archival.
Practical example:
You have a workflow that triggers when a project reaches a certain status in another system (e.g., "Completed"). Using this node's Project Delete operation, you can automatically remove the corresponding project from Everhour without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project to delete. This is a required string input. |
Output
The output JSON object after a successful delete operation contains a simple confirmation:
{
"success": true
}
This indicates that the project was successfully deleted. There is no additional data returned about the deleted project.
No binary data output is involved in this operation.
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 Project ID: Ensure the Project ID provided exists and is correctly formatted.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network connectivity problems: Confirm that the node can reach the Everhour API endpoint.
Common error messages:
"404 Not Found": The specified Project ID does not exist. Double-check the ID."401 Unauthorized"or"403 Forbidden": Authentication failed or insufficient permissions. Check API key validity and scopes.- Timeout or network errors: Check internet connection and firewall settings.
To resolve these, verify inputs, credentials, and network conditions.
Links and References
- Everhour API Documentation – Official API docs for detailed information on endpoints and authentication.
- n8n Documentation – For general guidance on using n8n nodes and credentials.