Steuerboard icon

Steuerboard

Consume the Steuerboard API

Overview

The node integrates with the Steuerboard API to create a new client record. It is designed for accounting, bookkeeping, or financial management workflows where managing client information programmatically is essential. For example, an accountant could automate adding new clients from a CRM system or form submissions directly into Steuerboard, ensuring consistent and up-to-date client data without manual entry.

Properties

Name Meaning
Name The name of the client to be created.
Type The type of the client. Options are: Natural Person (individuals), Individual Enterprise (sole proprietorships), Legal Person (companies like UG, GmbH, AG, Ltd., Inc., etc).
Custom ID An optional custom identifier defined by the accountant for the client.
Address The client's address details, including:
- Address Line 1: First line of the address
- Address Line 2: Second line of the address
- City
- Postal Code
- Country Code: Two-letter ISO 3166-1 alpha-2 country code (default "DE")

Output

The node outputs JSON data representing the created client object as returned by the Steuerboard API. This typically includes all client details such as assigned IDs, names, types, addresses, and any metadata provided by the API response. There is no indication that binary data is output by this node.

Dependencies

  • Requires an active connection to the Steuerboard API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The base URL for the API is configurable via credentials.
  • The node sends JSON-formatted requests and expects JSON responses.

Troubleshooting

  • Missing Required Fields: If "Name" or "Type" is not provided, the API will likely reject the request. Ensure these required fields are filled.
  • Invalid Address Format: Providing incomplete or incorrectly formatted address fields may cause errors. Verify that the country code follows ISO 3166-1 alpha-2 format.
  • Authentication Errors: If the API key or token is invalid or missing, the node will fail to authenticate. Check credential configuration.
  • API Endpoint Issues: Incorrect base URL or network issues can cause request failures. Confirm the API endpoint is reachable.
  • Unexpected API Responses: If the API changes or returns unexpected data, the node might not handle it gracefully. Review API documentation and update node if necessary.

Links and References

Discussion