Everhour icon

Everhour

Interact with Everhour API
Join our community

Actions32

Overview

This node interacts with the Everhour API to manage clients, specifically allowing you to update an existing client's information. The "Update Client" operation modifies details such as the client's name and business details by sending a PUT request to the Everhour API.

Common scenarios where this node is beneficial include:

  • Keeping client records up-to-date in your project management or time tracking system.
  • Automating client data synchronization between Everhour and other systems.
  • Correcting or enhancing client information without manual intervention.

For example, if a client's business details change or their name needs correction, this node can be used within an n8n workflow to update those details automatically based on triggers or other inputs.

Properties

Name Meaning
Client ID The unique identifier of the client to update (required).
Client Name The new name for the client (optional; if provided, it will update the client's name).
Business Details Additional business details for the client (optional; if provided, it will update these).

Output

The output JSON contains the updated client object returned from the Everhour API after a successful update operation. This typically includes fields such as the client's ID, name, business details, and any other metadata the API provides about the client.

Example output structure (simplified):

{
  "id": 123,
  "name": "Updated Client Name",
  "businessDetails": "Updated business details",
  ...
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the Everhour API.
  • The node uses the base URL from the configured credentials to send HTTP requests.
  • The Everhour API must be accessible and the API key must have permissions to update client data.

Troubleshooting

  • Missing or invalid Client ID: The update operation requires a valid client ID. Ensure that the Client ID property is set and corresponds to an existing client in Everhour.
  • Authentication errors: If the API key is missing, expired, or incorrect, the node will fail to authenticate. Verify the API key credential configuration.
  • Validation errors from API: Providing invalid or incomplete data (e.g., empty client name when required) may cause the API to reject the update. Check the API response message for details.
  • Network issues: Connectivity problems to the Everhour API endpoint will cause request failures. Confirm network access and API availability.

If the node is set to continue on failure, errors will be returned in the output JSON under an error field for each failed item.

Links and References

Discussion