Everhour icon

Everhour

Interact with Everhour API
Join our community

Actions32

Overview

This node interacts with the Everhour API to generate time reports based on specified date ranges and optional project filters. It is useful for users who want to extract summarized or detailed time tracking data from Everhour for analysis, billing, or project management purposes.

Typical scenarios include:

  • Generating a report of all tracked time within a specific period.
  • Filtering reports by one or more project IDs to focus on particular projects.
  • Automating report generation for regular review or invoicing.

For example, a project manager could use this node to generate a report of hours logged between January 1 and January 31 for projects A, B, and C, helping them assess team productivity or prepare client invoices.

Properties

Name Meaning
From Date Start date for the report (required). Defines the beginning of the reporting period.
To Date End date for the report (required). Defines the end of the reporting period.
Project IDs Comma-separated list of project IDs to include in the report. Optional filter by projects.

Output

The output is a JSON object representing the generated report data retrieved from the Everhour API endpoint /dashboards/projects. The structure typically includes aggregated time tracking information for the specified date range and projects.

  • The json field contains the full report data as returned by the API.
  • The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating requests to the Everhour API.
  • The node uses the base URL configured in the provided API credentials.
  • No additional external dependencies are required.

Troubleshooting

  • Invalid Date Range: Ensure that "From Date" is earlier than or equal to "To Date". Incorrect date ranges may cause API errors or empty reports.
  • Project IDs Format: Provide project IDs as a comma-separated string without spaces. Malformed input might result in no data or API errors.
  • Authentication Errors: Verify that the API key credential is correctly set up and has sufficient permissions to access report data.
  • API Rate Limits: If many requests are made in a short time, the API might throttle requests. Implement retries or delays if necessary.
  • Empty Results: If the report returns no data, check that the date range and project IDs correspond to existing tracked time entries.

Links and References

Discussion