Actions22
Overview
This node integrates with the FreshBooks API to manage various resources such as clients, projects, services, time tracking entries, and users. Specifically, for the Service resource with the Delete operation, the node allows users to delete a service record from their FreshBooks account. This is useful for cleaning up outdated or incorrect service entries.
A practical example: If a user has a service that is no longer offered or was created by mistake, they can use this node to remove that service from their FreshBooks business account programmatically within an n8n workflow.
Properties
| Name | Meaning |
|---|---|
| Business ID | Your FreshBooks Business ID. This identifies the specific business account in FreshBooks. You can find it in your FreshBooks account URL or by calling the /auth/api/v1/users/me endpoint. |
Note: Although the provided properties JSON only lists "Business ID," the node internally requires additional parameters such as the Service ID to identify which service to delete, but these are not explicitly listed in the user-provided properties snippet.
Output
The output of the node after a Delete operation on a Service resource will be a JSON object representing the response from the FreshBooks API. Typically, for a successful deletion, this might be an empty object or a confirmation message indicating the service was deleted.
No binary data is output by this node.
Dependencies
- Requires an API authentication token credential configured in n8n to authenticate requests to the FreshBooks API.
- The node sends HTTP DELETE requests to the FreshBooks API endpoint corresponding to services.
- The base URL used is
https://api.freshbooks.com.
Troubleshooting
Common issues:
- Incorrect or missing Business ID: The node requires a valid Business ID; if incorrect, the API will reject the request.
- Missing or invalid Service ID (not shown in the provided properties but required internally): Without specifying which service to delete, the operation cannot proceed.
- Authentication errors: If the API key or OAuth token is invalid or expired, the request will fail.
- Network connectivity issues may prevent the node from reaching the FreshBooks API.
Common error messages and resolutions:
- 401 Unauthorized: Check that the API authentication token is correctly set up and has not expired.
- 404 Not Found: Verify that the Business ID and Service ID exist and are correct.
- 400 Bad Request: Ensure all required parameters are provided and formatted correctly.
- 429 Too Many Requests: The API rate limit has been exceeded; wait before retrying.