Actions32
- Assignment Actions
- Client Actions
- Project Actions
- Report Actions
- Task Actions
- Time Actions
- Timecard Actions
- Webhook Actions
Overview
The "Start Timer" operation in the Everhour node allows users to start a time tracking timer for a specific task. This is useful in scenarios where you want to track the duration spent on a particular task in real-time, such as during project management, billing clients based on hours worked, or monitoring productivity.
For example, a user working on a software development task can start a timer when they begin coding and stop it when they finish, ensuring accurate time logs without manual entry.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task for which the timer should be started. |
| Comment | An optional comment or note associated with the time entry to provide additional context. |
Output
The node outputs a JSON object representing the newly started timer entry as returned by the Everhour API. This typically includes details such as the timer ID, task information, start time, and any comments provided.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Everhour API.
- The node uses the Everhour API base URL configured in the credential.
- Network connectivity to the Everhour service is necessary.
Troubleshooting
Common Issues:
- Invalid or missing Task ID: The API will reject requests if the task ID is not provided or incorrect.
- Authentication errors: If the API key credential is invalid or expired, the request will fail.
- Network issues: Connectivity problems may cause request failures.
Error Messages:
- Errors from the API are propagated and include messages such as "Task not found" or "Unauthorized".
- To resolve, verify the task ID exists, ensure the API key credential is valid, and check network access.