Everhour icon

Everhour

Interact with Everhour API
Join our community

Actions32

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 - Get operation, it retrieves detailed information about a single project by its unique ID.

Common scenarios where this node is beneficial include:

  • Fetching project details to display or use in workflows.
  • Automating project data retrieval for reporting or synchronization with other systems.
  • Integrating Everhour project data into broader automation pipelines.

For example, you might use this node to get a project's name, associated client, status, or other metadata before performing further actions like updating the project or generating reports.

Properties

Name Meaning
Project ID The unique identifier of the project to retrieve. This is required to specify which project to fetch.

Output

The node outputs the JSON representation of the requested project as returned by the Everhour API. This typically includes fields such as project name, client association, creation date, status, and other project-specific metadata.

The output structure is:

{
  "id": "string",
  "name": "string",
  "clientId": "number",
  "createdAt": "string (ISO date)",
  "updatedAt": "string (ISO date)",
  // ... other project-related fields as provided by Everhour API
}

Each execution returns one item containing the project data under the json property.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Everhour API.
  • The node uses the base URL from the configured credentials to make HTTP requests.
  • Proper permissions on the API key are necessary to read project data.

Troubleshooting

  • Missing or invalid Project ID: Ensure that the "Project ID" property is correctly set and corresponds to an existing project in Everhour.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Network or API errors: Check network connectivity and Everhour API status.
  • Error messages: If the node throws an error indicating failure to fetch the project, confirm the project ID exists and the API key is authorized to access it.

If the node is set to continue on fail, errors will be returned in the output JSON under an error field.

Links and References

Discussion