Connect Microsoft Dynamics 365 Business Central

How Microsoft Dynamics 365 Business Central signs requests

Service-to-service sign-in uses the OAuth 2.0 client credentials flow: an app registered in Microsoft Entra ID gets a token from the Entra token endpoint, with the client ID and secret in the form body.

Can you connect it today?

Yes. Add an OAuth client-credentials credential with your Microsoft Entra token URL and scope, sending the client ID and secret in the form body.

A sample mapping

Your application sends the first request below. The mapping turns it into the body of POST /v2.0/{tenantId}/{environment}/api/v2.0/companies({companyId})/customers, shown second.

{
    "name": "Fabrikam Ltd",
    "email": "ap@fabrikam.example"
}

{
    "displayName": "Fabrikam Ltd",
    "email": "ap@fabrikam.example"
}

The mapping

{
    "$schema": "https://schemas.echorelay.dev/transform/mapping/v1.json",
    "root": {
        "type": "object",
        "id": "root",
        "properties": {
            "displayName": {
                "type": "field",
                "id": "display-name",
                "path": "name"
            },
            "email": {
                "type": "field",
                "id": "email",
                "path": "email"
            }
        }
    }
}

The grammar, the answer mapping and the dry run are in the mapping docs.

What you bring

This is not a ready-made connector. You bring a sample request or Microsoft Dynamics 365 Business Central’s OpenAPI document, you or your agent write the mapping, and we run the integration you define.