Basic Integration

Overview

The "Basic Integration" node provides a flexible API integration interface primarily designed to interact with various data types within an external system referred to as "Logo." It supports multiple operations on different resources, including retrieving, creating, updating, and deleting records. Specifically, for the Integrations resource, the node can perform a "Get" operation that fetches a record based on a unique data reference and a specified data type.

This node is beneficial in scenarios where users need to automate data retrieval or manipulation tasks across diverse datasets in the Logo system without writing custom API calls manually. For example, it can be used to fetch detailed information about sales orders, purchase invoices, employees, or any other supported data category by specifying the appropriate data reference and data type.

Practical examples:

• Retrieve details of a specific sales order by providing its data reference number and selecting the "SALES_ORDERS" data type.
• Fetch employee records by specifying the employee's unique identifier and choosing the "EMPLOYEES" data type.
• Automate extraction of bank voucher information for financial reconciliation processes.

Properties

Output

The node outputs JSON data representing the retrieved record(s) from the Logo system corresponding to the specified data reference and data type. The structure of the JSON output depends on the selected data type and the underlying data schema of the Logo system. Each output item contains the full details of the requested record.

If the node supports binary data (not explicitly shown here), it would typically represent files or attachments related to the record, but this node appears focused on JSON data retrieval.

Dependencies

• Requires an API key credential configured in n8n to authenticate requests to the Logo system.
• The node relies on internal helper functions and resource modules to perform API calls.
• Proper configuration of tenant, firm number, and firm period may be necessary either via additional fields or credentials to access the correct dataset in the Logo environment.

Troubleshooting

• Common issues:

  • Invalid or missing data reference number: Ensure the data reference is a valid number within the allowed range.
  • Incorrect logo data type selection: Selecting a data type that does not correspond to the intended record will result in no data or errors.
  • Authentication failures: Verify that the API key credential is correctly set up and has sufficient permissions.
  • Missing tenant, firm number, or firm period: If these are required by the Logo system and not provided, the request may fail or return incorrect data.

• Error messages:

  • Errors returned from the Logo API will be surfaced as error messages in the node output if "Continue On Fail" is enabled.
  • Common error messages might include "Record not found," "Unauthorized," or "Invalid parameters."

• Resolution tips:

  • Double-check input parameters for correctness.
  • Confirm credential validity and permissions.
  • Use the additional fields to explicitly specify tenant, firm number, and firm period if defaults do not apply.

Links and References

• No direct external links are provided in the source code.
• Users should refer to the official Logo system API documentation for detailed information on data types and authentication requirements.
• n8n documentation on creating and configuring API integration nodes may provide helpful guidance.