Everhour icon

Everhour

Interact with Everhour API
Join our community

Actions32

Overview

The node integrates with the Everhour API to manage projects, including updating existing projects. Specifically, the "Update Project" operation allows users to modify details of a project such as its name and associated client ID. This is useful in scenarios where project information changes over time, for example, renaming a project or reassigning it to a different client.

Practical examples:

  • Updating a project’s name after a rebranding.
  • Changing the client associated with a project when account management shifts.
  • Automating project updates based on external triggers or workflows.

Properties

Name Meaning
Project ID The unique identifier of the project to update.
Project Name The new name to assign to the project.
Client ID The client ID to associate with the project (optional; defaults to 0 if not provided).

Output

The output is a JSON object representing the updated project as returned by the Everhour API. It contains the project's current state after the update, including fields like project ID, name, client association, and any other metadata provided by the API.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "id": "string",
  "name": "string",
  "clientId": 123,
  // ... other project details ...
}

Dependencies

  • Requires an API key credential for authenticating requests to the Everhour API.
  • The node uses HTTP methods (PUT) to send update requests to the /projects/{projectId} endpoint.
  • The base URL for the API is obtained from the configured credentials.
  • No additional environment variables are required beyond the API authentication setup.

Troubleshooting

  • Common issues:

    • Invalid or missing Project ID will cause the API request to fail.
    • Providing an invalid Client ID may result in errors or unexpected behavior.
    • Network or authentication failures can prevent successful updates.

  • Error messages:

    • Errors from the API typically include HTTP status codes and messages indicating the problem (e.g., 404 Not Found if the project does not exist).
    • Authentication errors occur if the API key is invalid or missing.

  • Resolutions:

    • Ensure the Project ID is correct and corresponds to an existing project.
    • Verify that the Client ID is valid within the Everhour system.
    • Confirm that the API key credential is correctly configured and has necessary permissions.
    • Check network connectivity and API availability.

Links and References

Discussion