Actions2
Overview
The Insert operation of the "InterSystems IRIS" n8n node allows you to add new rows to a specified table in an InterSystems IRIS database. This is useful for automating data entry, syncing records from other systems, or batch-inserting processed data into your IRIS instance.
Common scenarios:
- Adding new customer or order records from another workflow.
- Migrating or synchronizing data between different databases.
- Automating form submissions or API payloads directly into IRIS tables.
Example:
You could use this node to insert new sales transactions collected from an e-commerce platform into your IRIS database for further processing and reporting.
Properties
| Name | Type | Meaning |
|---|---|---|
| Table Name or ID | options | The name or ID of the target table where new rows will be inserted. You can select from a list or specify via an expression. |
| Columns | fixedCollection | A collection of columns and their values to insert. Each column entry includes: - Column Name or ID (options): The name/ID of the column. - Value (string): The value to insert into that column. |
Output
- The output is a JSON array containing the result of the insert operation.
- Each item in the output corresponds to a row inserted and contains the fields returned by the database after insertion (typically the inserted data, possibly with generated IDs or timestamps if the table is configured that way).
- No binary data is produced by this operation.
Example output:
[
{
"id": 123,
"name": "John Doe",
"email": "john@example.com"
}
]
Note: The actual structure depends on the table schema and what the database returns after insertion.
Dependencies
- External Service: Requires access to an InterSystems IRIS database.
- Credentials: An n8n credential named
irismust be configured with valid connection details. - Environment: The IRIS database must be reachable from the n8n instance.
Troubleshooting
Common issues:
- Invalid credentials: If the provided IRIS credentials are incorrect, the node will throw a connection error.
- Table or column not found: If the specified table or columns do not exist, the node will return an error indicating missing objects.
- Data type mismatch: Inserting a value of the wrong type (e.g., string into an integer column) may cause a database error.
- Permission denied: The user account used may lack INSERT privileges on the target table.
Error messages and resolutions:
"Connection successful!"– Connection test passed."Error: <message>"– Review the message for details; check credentials, network, and permissions."Cannot find table/column"– Double-check the table and column names/IDs."Data type mismatch"– Ensure values match the expected column types.