Actions22
Overview
This node operation updates an existing time tracking entry in FreshBooks. It allows users to modify details such as the client, project, service, note, date, duration, and logged status of a specific time entry identified by its ID. This is useful for correcting or refining time logs after they have been initially created, ensuring accurate billing and record-keeping.
Practical examples include:
- Adjusting the duration of a time entry if the originally recorded time was incorrect.
- Changing the associated project or service if the work was logged under the wrong category.
- Adding or updating notes to provide more context about the time entry.
- Marking a time entry as logged or unlogged depending on whether it should be included in invoices.
Properties
| Name | Meaning |
|---|---|
| Business ID | Your FreshBooks Business ID, found in your account URL or via user info API endpoint. |
| Time Entry ID | The unique identifier of the time entry you want to update. |
| Client ID | Numeric ID of the client associated with this time entry. |
| Project ID | Numeric ID of the project linked to this time entry. |
| Service ID | Numeric ID of the service related to this time entry. |
| Note | Text note describing or annotating the time entry. |
| Date | The start date of the time entry (only date part, formatted as yyyy-MM-dd). |
| Duration | Duration of the time entry in seconds (e.g., 28800 equals 8 hours). |
| Is Logged | Boolean flag indicating whether the time entry is marked as logged (true) or not (false). |
Output
The output JSON contains the updated time entry data returned from FreshBooks after the update operation. This typically includes all fields of the time entry such as IDs, timestamps, duration, notes, and status flags reflecting the new state after the update.
No binary data output is involved in this operation.
Dependencies
- Requires an active FreshBooks account with appropriate permissions.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node communicates with the FreshBooks API endpoint at
https://api.freshbooks.com. - The "Business ID" must be correctly specified to target the right FreshBooks business.
Troubleshooting
- Invalid or missing Business ID: Ensure the Business ID is correct and corresponds to your FreshBooks account.
- Time Entry ID not found: Verify that the Time Entry ID exists and belongs to the specified business.
- Permission errors: Confirm that the API token has sufficient rights to update time entries.
- Incorrect data types: For example, duration must be a number representing seconds; date must be in the correct format.
- API rate limits: If many requests are sent rapidly, you might hit FreshBooks API rate limits; implement retries or delays.
- Network issues: Check connectivity and proxy settings if requests fail to reach the FreshBooks API.
Common error messages usually come directly from the FreshBooks API and indicate issues like unauthorized access, resource not found, or validation errors on input fields. Reviewing the error message details and adjusting inputs accordingly resolves most problems.
Links and References
- FreshBooks API Documentation - Time Tracking
- FreshBooks Developer Portal
- n8n Documentation - HTTP Request Node (for understanding API calls)