FreshBooks

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, it allows users to delete a service record from their FreshBooks account.

A common use case is when a user wants to remove outdated or incorrect service entries from their FreshBooks business data. For example, if a service offering is discontinued or was created by mistake, this node can be used to delete that service programmatically within an n8n workflow.

Properties

Note: Although the provided properties JSON only lists "Business ID", the node internally requires additional parameters like serviceId (not shown explicitly here) to identify which service to delete. The deletion URL pattern suggests the need for a service identifier parameter.

Output

The output of the node after executing the Delete operation on a Service resource will be a JSON object representing the response from the FreshBooks API. Typically, for a successful delete request, the response might be empty or contain confirmation metadata.

• The json field contains the API response confirming the deletion.
• No binary data output is expected for this operation.

Dependencies

• Requires an API authentication token credential configured in n8n to authenticate requests against the FreshBooks API.
• The node uses the base URL https://api.freshbooks.com.
• The user must provide a valid Business ID to scope the API calls correctly.

Troubleshooting

• Common issues:

  • Invalid or missing Business ID: The API call will fail if the Business ID is incorrect or not provided.
  • Missing service identifier: The Delete operation requires the specific service ID to delete; failure to provide this will cause errors.
  • Authentication errors: If the API key or OAuth2 token is invalid or expired, the request will be rejected.
  • Permission errors: The authenticated user must have permission to delete services in the specified business.

• Error messages:

  • 404 Not Found: The service ID does not exist or is not associated with the given Business ID.
  • 401 Unauthorized: Authentication failed due to invalid credentials.
  • 400 Bad Request: Missing required parameters or malformed request.

• Resolutions:

  • Verify the Business ID and service ID are correct.
  • Ensure the API credentials are valid and have necessary permissions.
  • Check the FreshBooks API documentation for any changes in endpoint requirements.

Links and References

• FreshBooks API Documentation
• FreshBooks Developer Portal
• n8n Documentation on Creating Custom Nodes