Actions7
Overview
This node allows interaction with SAP Business One via a Unified MCP Server, supporting operations on various resources including Transactions. Specifically, the Transaction Commit operation finalizes and commits a previously started transaction, ensuring all changes within that transaction are saved permanently in the system.
This node is beneficial when you need to manage database or service layer transactions programmatically within an n8n workflow, such as:
- Committing a transaction after a series of data modifications to ensure atomicity.
- Integrating SAP Business One transactional control into automated business processes.
- Coordinating multiple operations that must succeed or fail together.
For example, after beginning a transaction and performing several inserts or updates, you would use this node's commit operation to finalize those changes.
Properties
| Name | Meaning |
|---|---|
| Connection Type | Type of connection to use: - Direct Database - Service Layer |
| Transaction ID | ID of the transaction to commit. This identifies which open transaction should be finalized. |
Output
The output is a JSON object representing the response from the Unified MCP Server after attempting to commit the transaction. It typically contains confirmation details or status information about the commit operation.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"status": "success",
"transactionId": "abc123",
"message": "Transaction committed successfully"
}
Dependencies
- Requires an API key credential for authentication with the Unified MCP Server.
- The node communicates with the MCP server URL configured in the credentials.
- The MCP server must support the
/api/transactions/{transactionId}/commitendpoint for both connection types (dbandsl).
Troubleshooting
- Invalid Transaction ID: If the provided transaction ID does not exist or has already been committed/rolled back, the server may return an error. Verify the transaction ID is correct and active.
- Connection Issues: Network or authentication failures can prevent committing. Ensure the MCP API credentials are valid and the server URL is reachable.
- Operation Not Allowed: Attempting to commit a transaction that was not properly begun or belongs to a different connection type might cause errors.
- Error Messages: Errors returned from the MCP server will be included in the node output if "Continue On Fail" is enabled. Review these messages for specific causes.