Actions5
- Integrations Actions
Overview
This node, named "Basic Integration," provides a generic API integration interface primarily designed to interact with various data resources. Specifically, for the Integrations resource and the Delete operation, it allows users to delete a record identified by a unique data reference within a specified data category (logo data type). This is useful in scenarios where automated workflows need to remove entries from external systems or databases based on dynamic input.
Practical examples include:
- Automatically deleting outdated or invalid records from an ERP system.
- Removing specific transactional data entries as part of a cleanup process.
- Integrating with accounting or inventory management systems to maintain synchronized data states.
Properties
| Name | Meaning |
|---|---|
| Data Reference | The unique numeric identifier of the record to be deleted. Must be between 1 and 9999999999. |
| Logo Data Type | The category/type of data to operate on. Options include a wide range of predefined categories such as ITEMS, PURCHASE_ORDERS, SALES_INVOICES, EMPLOYEES, CUSTOMERS, PROJECTS, and many others representing different business entities or document types. |
| Additional Fields | Optional fields to specify tenant, firm number, and firm period for the operation. If not provided, these values default to those set in the node's credentials. |
Logo Data Type Options (examples)
- ITEMS
- MATERIAL_SLIPS
- PURCHASE_SERVICES
- SALES_ORDERS
- PURCHASE_ORDERS
- EMPLOYEES
- CUSTOMERS
- PROJECTS
- SALES_INVOICES
- BANK_ACCOUNTS
- FIXED_ASSET_REGISTRY
- And many more (total over 140 options)
Output
The node outputs JSON data representing the result of the delete operation for each input item processed. Typically, this will include confirmation of deletion or any relevant response from the external system indicating success or failure.
If the operation fails and "Continue On Fail" is enabled, the output JSON will contain an error field with the error message for that particular item.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the external system.
- Depends on the external system's API supporting the delete operation for the specified data types.
- The node uses internal helper methods to construct execution metadata and handle multiple input items.
Troubleshooting
Common Issues:
- Invalid or missing Data Reference: Ensure the data reference number is valid and exists in the target system.
- Incorrect Logo Data Type: Selecting an unsupported or incorrect data type may cause the operation to fail.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network or connectivity issues with the external API.
Error Messages:
- Errors returned from the external API will be included in the output if "Continue On Fail" is enabled.
- Common error messages might relate to authorization failures, invalid identifiers, or resource not found.
Resolution Tips:
- Double-check input parameters for correctness.
- Confirm API credentials and access rights.
- Review API documentation of the external system for required parameters and constraints.
Links and References
- No direct external links are provided in the source code.
- Users should refer to their external system's API documentation corresponding to the data types and delete operations for detailed behavior and requirements.