Rest Accounting

Interact with Rest Accounting API
Join our community

Actions13

Overview

This node interacts with a Rest Accounting API to manage journal entries among other accounting resources. Specifically, the Delete operation under the Journal Entries resource allows users to delete a journal entry by its unique Entry ID.

Typical use cases include:

  • Automating cleanup of erroneous or obsolete journal entries in an accounting system.
  • Integrating with workflows that require removing specific financial records based on business logic.
  • Maintaining data accuracy by programmatically deleting entries without manual intervention.

For example, a user might configure this node to delete a journal entry after verifying it was duplicated or created in error.

Properties

Name Meaning
Entry ID The unique numeric identifier of the journal entry to delete. This is required.

Output

The node outputs a JSON object representing the response from the API after attempting to delete the journal entry. Typically, this will contain confirmation of deletion or details about the deleted entry depending on the API's design.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "message": "Journal entry deleted successfully",
  "entryId": 123
}

or an empty object if the API returns no content on successful deletion.

Dependencies

  • Requires an API key credential for authenticating requests to the Rest Accounting API.
  • The base URL and API key must be configured in the node credentials.
  • The node uses HTTP DELETE method to call the endpoint /journal-entries/{entryId}.

Troubleshooting

  • Common issues:

    • Invalid or missing Entry ID: The node requires a valid numeric Entry ID; ensure this is provided.
    • Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
    • Network or connectivity problems: Check network access to the API base URL.
    • Entry not found: If the Entry ID does not exist, the API may return a 404 error.

  • Error messages:

    • "Request failed": Generic failure, check the detailed message for specifics.
    • API error responses are wrapped and thrown as node errors; review the error message for clues.

  • Resolution tips:

    • Double-check the Entry ID value.
    • Confirm API key validity and permissions.
    • Inspect API documentation for expected request format and error codes.
    • Use logging or debug mode in n8n to capture full request/response details.

Links and References

Discussion