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. It allows managing transactions among other operations such as querying data, manipulating records, authentication, and custom API calls.

Specifically, the Transaction - Begin operation starts a new transaction session either on the database connection or via the service layer. This is useful when you want to group multiple operations into a single atomic unit, ensuring all succeed or fail together.

Practical examples:

  • Starting a transaction before inserting multiple related records to ensure data consistency.
  • Beginning a transaction to perform several updates and then committing or rolling back based on success or failure.
  • Using the service layer connection type to begin a transaction in SAP Business One's API context.

Properties

Name Meaning
Connection Type Type of connection to use. Options: "Direct Database" (db), "Service Layer" (sl).

Output

The output is a JSON object containing the response from the Unified MCP Server after attempting to begin a transaction. Typically, this includes details such as a transaction ID or status confirmation that the transaction has started successfully.

If the node supports binary data output, it would represent any binary content returned by the server, but for the Transaction Begin operation, the output is purely JSON.

Example output structure (simplified):

{
  "transactionId": "string",
  "status": "string"
}

Dependencies

  • Requires an API key credential configured in n8n to authenticate with the Unified MCP Server.
  • The node depends on the MCP Server URL and credentials being correctly set up.
  • Uses the axios library internally to make HTTP requests to the MCP Server endpoints.
  • The MCP Server must support the /api/transactions/begin endpoint for both connection types (db and sl).

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials can cause authentication failures.
    • Using the wrong connection type may lead to endpoint errors.
    • Network connectivity problems between n8n and the MCP Server.
    • Invalid or expired session when using the Service Layer connection.

  • Error messages:

    • Authentication errors: Verify API key and credentials.
    • Endpoint not found or 404 errors: Check the connection type and resource path.
    • JSON parsing errors: Ensure input parameters are valid JSON where required.
    • Transaction start failures: Confirm the MCP Server supports transactions and the user has permissions.

To resolve these, verify credentials, network access, and correct parameter usage.

Links and References

Discussion