Everhour icon

Everhour

Interact with Everhour API
Join our community

Actions32

Overview

This node interacts with the Everhour API to update an existing task. It allows users to modify the name and time estimate of a specific task identified by its Task ID. This operation is useful in project management workflows where task details need to be adjusted dynamically, such as updating task names for clarity or revising time estimates based on new information.

Practical examples:

  • Renaming a task after scope changes.
  • Adjusting the estimated time required to complete a task as more accurate information becomes available.

Properties

Name Meaning
Task ID The unique identifier of the task to update (required).
Task Name The new name for the task (required).
Estimate (Seconds) The updated time estimate for the task in seconds (optional; defaults to 0 if not set).

Output

The node outputs the updated task object returned from the Everhour API in the json field. This typically includes all task details after the update, such as the task's ID, name, estimate, associated projects, and other metadata.

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 provided by the credential to send HTTP PUT requests to update tasks.
  • Proper configuration of the API authentication credential within n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Task ID will cause the API request to fail.
    • Insufficient permissions or invalid API credentials can result in authentication errors.
    • Providing an empty or invalid Task Name may cause the update to be rejected.

  • Error messages:

    • Errors from the Everhour API are propagated and wrapped as node operation errors.
    • If the node is configured to continue on failure, error messages will appear in the output JSON under an error property.

  • Resolutions:

    • Verify that the Task ID corresponds to an existing task.
    • Ensure the API key credential is valid and has appropriate permissions.
    • Provide a valid, non-empty Task Name.
    • Check network connectivity and API endpoint accessibility.

Links and References

Discussion