Rest Accounting

Interact with Rest Accounting API
Join our community

Actions13

Overview

This node integrates with a RESTful Accounting API to perform various operations on accounting data. Specifically, for the Accounts - Get operation, it retrieves detailed information about a single account by its unique Account ID.

Common scenarios where this node is beneficial include:

  • Fetching account details for financial reporting or reconciliation.
  • Integrating account data into workflows that require up-to-date account metadata.
  • Automating audits or validations by retrieving specific account information programmatically.

For example, you might use this node to get the details of an account before creating a journal entry linked to that account, ensuring the account exists and is active.

Properties

Name Meaning
Account ID The unique numeric identifier of the account to retrieve. This is required.
Query Parameters (Not used in the Get operation for Accounts)

Note: Although the node supports a "Query Parameters" collection property, it is not applicable for the "Get" operation on Accounts.

Output

The output is a JSON object representing the retrieved account's data as returned by the external REST Accounting API. The structure depends on the API response but typically includes fields such as:

  • Account ID
  • Account Code
  • Account Name
  • Account Type
  • Parent Account ID (if any)
  • Other metadata related to the account

The node outputs this data under the json key in the standard n8n item format.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the external REST Accounting API.
  • The base URL and API key must be configured in the node credentials.
  • The node uses HTTP requests with JSON payloads and expects JSON responses.

Troubleshooting

  • Common issues:

    • Invalid or missing Account ID will cause the API request to fail.
    • Incorrect or expired API key will result in authentication errors.
    • Network connectivity problems can cause request timeouts or failures.

  • Error messages:

    • "Request failed": Generic error indicating the HTTP request did not succeed. Check network, API key, and endpoint URL.
    • Errors from the API may be wrapped and surfaced via the node's error handling; inspect the message for details.

  • Resolution tips:

    • Verify the Account ID is correct and exists in the accounting system.
    • Ensure the API key credential is valid and has necessary permissions.
    • Confirm the base URL is correctly set in the credentials.
    • Test connectivity to the API endpoint outside n8n to isolate network issues.

Links and References

Discussion