Rest Accounting

Interact with Rest Accounting API
Join our community

Actions13

Overview

This node integrates with the Rest Accounting API to manage accounting data programmatically. It supports multiple resources such as Accounts, Journal Entries, Reports, and Health checks. Specifically for the Accounts - Create operation, it allows users to create a new account by specifying various account fields.

Typical use cases include automating the creation of new accounts in an accounting system during financial setup or integration workflows, syncing account structures from other systems, or dynamically adding accounts based on business logic.

For example, you might use this node to:

  • Automatically add a new ledger account when onboarding a new client.
  • Create sub-accounts under a parent account to organize finances better.
  • Integrate with external ERP or CRM systems to keep chart of accounts synchronized.

Properties

Name Meaning
Account Fields A collection of fields defining the new account to create. Includes:
- Code: The unique code identifier for the account (string).
- Name: The name of the account (string).
- Type: The type/category of the account (string).
- Parent ID: Numeric ID of the parent account if creating a sub-account (number).

Note: The "Account Fields" property is optional but typically required to specify meaningful account details.

Output

The node outputs a JSON object representing the response from the Rest Accounting API after creating the account. This usually includes details of the newly created account such as its ID, code, name, type, parent ID, and any metadata returned by the API.

Example output structure (simplified):

{
  "id": 123,
  "code": "4000",
  "name": "Sales Revenue",
  "type": "Revenue",
  "parent_id": 0
}

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Rest Accounting API.
  • The base URL and API key must be configured in the node's credentials.
  • The node uses HTTP requests with JSON payloads to communicate with the API.

Troubleshooting

  • Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
  • Validation errors: If required account fields like "code" or "name" are missing or invalid, the API may reject the request. Double-check field values.
  • Network issues: Connectivity problems or incorrect base URL configuration can cause request failures.
  • API errors: The node surfaces API error messages; review these for hints on what went wrong (e.g., duplicate account codes).

If you encounter a generic "Request failed" error, inspect the detailed message provided by the API response to diagnose further.

Links and References

Discussion