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 connection types: direct database access and service layer API calls. Specifically for the Data resource with the 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 directly from workflows.
  • Integrating external systems by pushing structured data into SAP Business One.
  • Quickly adding new records to SAP Business One without manual input.

For example, you can insert a new customer record into a specific table by providing the table name and the customer data as a JSON object.

Properties

Name Meaning
Connection Type Type of connection to use: "Direct Database" or "Service Layer".
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 table (required for Direct Database).

Output

The node outputs an array of JSON objects, each corresponding to one input item processed. The json field contains the response data returned by the Unified MCP Server after attempting the insert operation. This typically includes confirmation of the inserted record or any error messages.

No binary data output is produced by this operation.

Dependencies

  • Requires credentials for the Unified MCP Server, including its base URL and an API authentication token.
  • The node uses the Axios HTTP client to communicate with the MCP server endpoints.
  • For direct database operations, the MCP server must support the /api/db/insert endpoint.
  • Proper permissions on the MCP server are necessary to perform insert operations on the target tables.

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.
  • Malformed JSON Data: The Data property must be valid JSON. Errors in JSON syntax will cause failures before the request is sent.
  • Authentication Issues: Ensure that the provided API credentials are valid and have sufficient rights.
  • Connection Type Mismatch: The Insert operation for the Data resource is only supported with the "Direct Database" connection type. Using "Service Layer" with this operation may result in errors.
  • Server Errors: Network issues or MCP server downtime will cause request failures. Check connectivity and server status.

Links and References

Discussion