Overview
This node integrates with the Exact Online API, allowing users to perform various operations on Exact Online data. It supports both REST and XML API endpoints and provides flexible options for authentication (Access Token or OAuth2). The node is useful for automating workflows involving Exact Online, such as retrieving records, creating new entries, updating existing data, or deleting records.
Common scenarios include:
- Fetching financial or business data from Exact Online divisions and services.
- Automating data synchronization between Exact Online and other systems.
- Managing Exact Online resources programmatically within n8n workflows.
For example, a user can retrieve all customers from a specific division and service, filter them by certain criteria, or create new invoices by posting XML data.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Exact Online API. Options: "Access Token" or "OAuth2". |
| Division Name or ID | Select or specify the Exact Online division to operate on. Can be chosen from a list or provided via expression. |
| Service Name or ID | Select or specify the Exact Online service to connect to, dependent on the selected division. |
Output
The node outputs an array of JSON objects representing the results of the performed operation:
- For GET operations, it returns the retrieved records matching the query or ID.
- For POST operations (including XML-based), it returns success messages and any response data parsed from XML or JSON.
- For PUT and DELETE operations, it returns confirmation messages indicating success.
- In case of errors, if "Continue On Fail" is enabled, error details are included in the output per item.
If the node interacts with XML endpoints, it parses XML responses into JSON objects for easier consumption in workflows.
The node does not output binary data.
Dependencies
- Requires valid credentials for Exact Online API access, either via an Access Token or OAuth2 authentication.
- Uses internal helper functions for making HTTP requests and parsing XML.
- No additional external dependencies beyond those bundled with the node.
Troubleshooting
- Missing mandatory fields: When creating or updating records, ensure all required fields are provided; otherwise, the node throws an error specifying which fields are missing.
- Invalid XML data: For XML POST operations, the node expects properly structured JSON arrays for certain fields (e.g., "MatchSets"). Invalid or empty arrays cause errors.
- Unsupported operations: Attempting unsupported operations for a given resource or endpoint will result in clear error messages.
- Rate limiting: If the "Disable waiting for minutely rate limit" option is false, the node waits to avoid 429 errors. Setting it true may cause rate limit errors.
- Parent ID requirement: For operations that require a parent resource ID, omitting this parameter causes an error.
- Parsing errors: XML response parsing failures provide detailed error messages including raw response content for debugging.
To resolve issues, verify input parameters, ensure correct authentication, and consult Exact Online API documentation for valid field names and values.
Links and References
If you need further details about specific operations or resources, please let me know!