Unified MCP icon

Unified MCP

Interact with SAP Business One via Unified MCP Server

Actions7

Overview

This node enables interaction with SAP Business One through a Unified MCP Server, supporting two types of connections: Direct Database and Service Layer. Specifically for the Transaction - Begin operation, it initiates a new transaction session either directly on the database or via the service layer.

Use cases include:

  • Starting a transaction to group multiple operations into an atomic unit, ensuring all succeed or fail together.
  • Managing complex business processes where data consistency is critical.
  • Integrating SAP Business One transactional workflows within automated n8n workflows.

For example, you might begin a transaction before inserting multiple related records, then commit or rollback based on subsequent steps' success.

Properties

Name Meaning
Connection Type Type of connection to use; options are:
- Direct Database
- Service Layer

Output

The node outputs JSON data representing the response from the Unified MCP Server's transaction begin endpoint. This typically includes information such as a transaction ID that can be used in subsequent commit or rollback operations.

No binary data output is involved.

Example output structure (simplified):

{
  "success": true,
  "data": {
    "transactionId": "some-unique-id"
  }
}

Dependencies

  • Requires an API key credential configured for the Unified MCP Server.
  • The node uses the base URL and authentication session (for Service Layer) or direct DB access parameters from these credentials.
  • Axios HTTP client is used internally to make requests to the MCP server endpoints.

Troubleshooting

  • Common issues:

    • Invalid or expired session when using Service Layer connection type. Solution: Re-login to refresh the session.
    • Incorrect API URL or network connectivity problems. Verify the MCP server URL and network access.
    • Missing or invalid credentials causing authentication failures.

  • Error messages:

    • Errors returned from the MCP server will be included in the node output if "Continue On Fail" is enabled.
    • Typical errors include authentication failures, invalid transaction requests, or malformed parameters.

To resolve, ensure correct credentials, valid session, and proper parameter values.

Links and References

Discussion