Unified MCP icon

Unified MCP

Interact with SAP Business One via Unified MCP Server

Actions7

Overview

This node enables updating data records in SAP Business One via a Unified MCP Server. It supports two connection types: direct database access and service layer API calls. The "Update" operation under the "Data" resource allows users to modify existing records either by specifying a table and condition for direct database updates or by targeting specific entities through the service layer.

Common scenarios include:

  • Updating customer or item information directly in the database.
  • Modifying business partner or order details via the service layer API.
  • Automating record updates as part of larger workflows integrating SAP Business One data.

For example, you might update a customer's address in the database by specifying the table, new data, and a condition identifying the customer record. Alternatively, you could update an order's status using the service layer by providing the order ID and updated fields.

Properties

Name Meaning
Connection Type Selects the method of connection: Direct Database or Service Layer.
Table (Direct Database only) The name of the database table where the update will occur.
Data JSON object containing the fields and values to update in the record.
Condition (Direct Database only) SQL WHERE clause condition to identify which records to update.
Condition Parameters (Direct Database only) JSON object with parameters used in the WHERE condition placeholders.

Output

The node outputs an array of JSON objects, each representing the response from the MCP server for each input item processed. The json field contains the data returned by the server after performing the update operation, typically including success confirmation or details about the updated record.

If errors occur and "Continue On Fail" is enabled, the output JSON will contain an error field describing the issue.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential configured in n8n to authenticate with the Unified MCP Server.
  • The MCP Server URL and connection type must be set in the credentials.
  • Uses the Axios HTTP client internally to send requests to the MCP Server endpoints.

Troubleshooting

  • Invalid Table or Condition: If the table name or condition is incorrect, the update may fail or affect unintended records. Verify the table exists and the condition correctly identifies target rows.
  • Malformed JSON Data: Ensure the JSON provided in the "Data" and "Condition Parameters" fields is valid and matches the expected schema.
  • Authentication Errors: If the API key or session is invalid, requests will fail. Re-authenticate or check credential configuration.
  • Network Issues: Connectivity problems to the MCP Server will cause request failures. Confirm network access and server availability.
  • Error Messages: The node returns error messages in the output JSON under the error key when "Continue On Fail" is enabled. Review these messages to diagnose issues.

Links and References

Discussion