EverhourInstall

Overview

This node interacts with the Everhour API to manage tasks and other related resources. Specifically, for the Task - Get operation, it retrieves detailed information about a single task by its unique ID. This is useful when you want to fetch the current state or details of a specific task within your project management workflow.

Common scenarios include:

• Fetching task details to display or process in subsequent workflow steps.
• Verifying task existence or status before performing updates or deletions.
• Integrating task data into reports or dashboards.

Example: You have a task ID from a previous step or external source, and you want to retrieve all associated information such as name, estimate, and linked projects.

Properties

Output

The node outputs a JSON object representing the task's details as returned by the Everhour API. This typically includes fields such as:

• id: The task's unique identifier.
• name: The name/title of the task.
• estimate: Time estimate for the task (usually in seconds).
• projects: Array of projects the task belongs to.
• Other metadata related to the task.

The output is structured as an array of items, each containing a json property with the task data. There is no binary data output for this operation.

Example output snippet (simplified):

{
  "id": "12345",
  "name": "Design homepage",
  "estimate": {
    "total": 7200
  },
  "projects": ["projectId1", "projectId2"]
}

Dependencies

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

Troubleshooting

• Invalid Task ID: If the provided Task ID does not exist or is malformed, the API will return an error. Ensure the Task ID is correct and exists in your Everhour account.
• Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly set up and has necessary permissions.
• Network Issues: Connectivity problems can cause request failures. Check network access and Everhour service status.
• API Rate Limits: Excessive requests may be throttled by Everhour. Implement retry logic or reduce request frequency if needed.

Error messages from the node will typically include the API response message. Use these messages to diagnose issues.

Links and References

• Everhour API Documentation
• Everhour Official Website