Actions7
Overview
This node enables interaction with SAP Business One through a Unified MCP Server, supporting two connection types: direct database access and service layer API calls. Specifically, for the Data - Insert operation, it allows inserting JSON-formatted data into a specified database table when using the direct database connection type.
Common scenarios include automating data entry into SAP Business One tables, such as adding new records to custom or standard tables directly via database insertions. This is useful in workflows where external systems generate data that needs to be pushed into SAP Business One without manual intervention.
Example use case: Automatically inserting new customer information into a "Customers" table after receiving data from a web form.
Properties
| Name | Meaning |
|---|---|
| Connection Type | Type of connection to use: - Direct Database (db) - Service Layer (sl) |
| Table | Name of the database table where data will be inserted (required for Direct Database). |
| Data | JSON object representing the data to insert into the specified table (required for Direct Database). |
Output
The node outputs an array of JSON objects corresponding to the response from the MCP server after attempting the insert operation. The exact structure depends on the MCP server's API response but generally includes success status and any relevant metadata about the inserted record.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to a Unified MCP Server endpoint.
- Needs credentials containing the MCP API URL and authentication details (e.g., API key or session token).
- For the direct database connection type, the MCP server must support database insert operations at the
/api/db/insertendpoint. - The node uses HTTP requests to communicate with the MCP server, relying on proper network connectivity and valid credentials.
Troubleshooting
- Invalid Table Name: If the specified table does not exist or is misspelled, the MCP server will likely return an error. Verify the table name matches exactly what exists in the database.
- Malformed JSON Data: The
Dataproperty must be valid JSON. Errors parsing this input will cause failures. Use JSON validators to ensure correctness. - Authentication Issues: If credentials are missing or invalid, the node will fail to connect. Ensure the MCP API credentials are correctly configured and have sufficient permissions.
- Connection Type Mismatch: Using the Insert operation with the Service Layer connection type is not supported for direct inserts; ensure the connection type is set to Direct Database (
db) for this operation. - Network Errors: Timeouts or unreachable MCP server endpoints will cause request failures. Check network connectivity and MCP server availability.