EverhourInstall

Overview

This node interacts with the Everhour API to manage assignments related to users and projects. Specifically, for the Assignment resource with the Get Many operation, it retrieves multiple assignment records, typically filtered by user or project.

Common scenarios where this node is beneficial include:

• Fetching all assignments for a specific user to understand their workload.
• Retrieving assignments linked to a particular project to monitor resource allocation.
• Integrating Everhour assignment data into workflows for reporting or automation purposes.

For example, you might use this node to get all assignments of a user before generating a report on their scheduled tasks or to synchronize assignment data with another system.

Properties

Note: Although the provided property definition only includes "User ID", the code also supports an optional "projectId" query parameter when getting many assignments, but since it's not in the input properties, it is not listed here.

Output

The output is an array of JSON objects, each representing an assignment retrieved from Everhour. Each assignment object typically contains details such as:

• Assignment type (e.g., project or time-off)
• Associated project ID
• User ID
• Start and end dates of the assignment
• Scheduled time in seconds
• Other metadata related to the assignment

The output does not include binary data.

Example output snippet (simplified):

[
  {
    "type": "project",
    "project": "project-id-string",
    "user": 123,
    "startDate": "2024-01-01T00:00:00Z",
    "endDate": "2024-01-31T23:59:59Z",
    "scheduledTime": 3600
  },
  ...
]

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.
• No additional external dependencies beyond the Everhour API and n8n's built-in HTTP request helpers.

Troubleshooting

• Authentication errors: Ensure that the API key credential is correctly configured and has sufficient permissions to access assignments.
• Empty results: If no assignments are returned, verify that the specified User ID exists and has assignments in Everhour.
• API rate limits: Frequent calls may hit Everhour API rate limits; consider adding delays or handling retries.
• Invalid parameters: Passing incorrect or missing required parameters (like User ID) will cause errors; always provide valid inputs.

If the node throws errors related to HTTP requests, check network connectivity and API endpoint availability.

Links and References

• Everhour API Documentation — Official API docs for understanding assignment endpoints and parameters.
• n8n Documentation — For general guidance on using credentials and HTTP request nodes.