Business Central icon

Business Central

Interact with Microsoft Dynamics 365 Business Central

Web Services

AI-generated

Overview

This node integrates with Microsoft Dynamics 365 Business Central, specifically allowing users to interact with its Web Services via OData endpoints. It is useful for retrieving data from custom or standard Business Central services by specifying the service path. Typical use cases include fetching customer lists, sales orders, or other business data exposed through Business Central's web services. For example, a user might retrieve a list of customers from a custom "workflowCustomers" service to process or analyze them in an n8n workflow.

Properties

Name Meaning
Service Name The service path used in the API URL to access a specific Business Central web service. Examples include "workflowCustomers" or any other valid OData service endpoint name.

Output

The node outputs an array of items where each item contains a json field representing one record retrieved from the specified Business Central web service. The structure of each JSON object corresponds directly to the data returned by the Business Central OData API for that service.

No binary data output is produced by this node.

Dependencies

  • Requires an API authentication credential for Microsoft Dynamics 365 Business Central.
  • The node uses the tenant ID, environment name, and company ID from the credentials to construct the API URL.
  • The Business Central API must be accessible and the specified web service must exist and be enabled in the Business Central environment.

Troubleshooting

  • Common issues:
    • Incorrect or missing service name will result in failed API calls.
    • Invalid or expired API credentials will cause authentication errors.
    • Network connectivity issues or incorrect tenant/environment/company IDs can prevent successful requests.
  • Error messages:
    • If the API request fails, the node throws an error indicating "All API endpoint attempts failed" along with HTTP status codes if available.
    • The console logs the underlying error message for debugging.
  • Resolution tips:
    • Verify the service name matches exactly the exposed OData service in Business Central.
    • Ensure API credentials are valid and have sufficient permissions.
    • Confirm network access to the Business Central API endpoint.
    • Check that the tenant ID, environment name, and company ID are correctly configured in the credentials.

Links and References

Discussion