EverhourInstall

Overview

This node integrates with the Everhour API to manage clients and other resources. Specifically, for the Client - Delete operation, it allows users to delete a client by specifying its unique ID. This is useful in scenarios where you want to automate the removal of outdated or irrelevant client records from your Everhour account.

Practical examples include:

• Automatically cleaning up client data when a project ends.
• Removing test or temporary clients created during development or testing phases.
• Integrating with other systems to synchronize client deletions.

Properties

Output

The output JSON object for the delete operation contains a simple confirmation of success:

{
  "success": true
}

This indicates that the client was successfully deleted. There is no additional data returned.

Dependencies

• Requires an API key credential to authenticate requests to the Everhour API.
• The node uses the Everhour API base URL configured in the credentials.
• The node depends on n8n's built-in HTTP request helper with authentication support.

Troubleshooting

• Common issues:

  • Providing an invalid or non-existent Client ID will likely result in an error from the Everhour API.
  • Missing or incorrect API credentials will cause authentication failures.
  • Network connectivity issues can prevent successful API calls.

• Error messages:

  • Errors thrown by the node will contain the message from the Everhour API or network layer.
  • If the node is set to continue on fail, errors will be returned as JSON objects with an error field describing the issue.

• Resolutions:

  • Verify the Client ID exists in your Everhour account before attempting deletion.
  • Ensure the API key credential is correctly configured and has sufficient permissions.
  • Check network connectivity and proxy settings if applicable.

Links and References

• Everhour API Documentation
• n8n HTTP Request Node Documentation (for understanding requestWithAuthentication helper)