FreshBooks icon

FreshBooks

FreshBooks Node

Actions22

Overview

This node integrates with the FreshBooks API to manage clients, projects, services, time tracking, and users. Specifically, the Client - Delete operation allows users to delete a client from their FreshBooks account by specifying the client's Account ID. This is useful for cleaning up or removing outdated or incorrect client records from your accounting system.

Practical examples include:

  • Removing a client who is no longer active or relevant.
  • Automating client data cleanup as part of a larger workflow.
  • Integrating with CRM systems to sync client deletions.

Properties

Name Meaning
Account ID Your FreshBooks Account ID. This identifies the account from which the client will be deleted. It is required and can be found in your FreshBooks account settings.

Output

The node outputs JSON data representing the response from the FreshBooks API after attempting to delete the client. Typically, this will include confirmation of deletion or an error message if the deletion failed.

The node does not output binary data.

Dependencies

  • Requires an API authentication token configured in n8n to access the FreshBooks API.
  • The node uses the FreshBooks API base URL: https://api.freshbooks.com.
  • The user must provide a valid FreshBooks Account ID.
  • The node depends on the FreshBooks OAuth2 API credentials configured in n8n.

Troubleshooting

  • Common issues:
    • Invalid or missing Account ID: The operation requires a valid Account ID; ensure it is correctly entered.
    • Authentication errors: Ensure the API credentials are valid and have the necessary permissions.
    • Client not found: If the client ID does not exist, the API will return an error.
  • Error messages:
    • Unauthorized or 401 errors indicate invalid or expired credentials.
    • 404 errors indicate the specified client or account was not found.
    • 400 errors may indicate malformed requests or missing required parameters.
  • Resolutions:
    • Verify and update API credentials.
    • Double-check the Account ID and client identifiers.
    • Review API rate limits and ensure requests are within allowed quotas.

Links and References

Discussion