Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Microsoft Dynamics 365 Business Central

All-in-one business management solution by Microsoft.

CategorySales And Crm
Authenticationcustom
Version0.3.0
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect Microsoft Dynamics 365 Business Central with Flows360

All-in-one business management solution by Microsoft.

Use the Microsoft Dynamics 365 Business Central connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and 1 trigger.

Available actions

  • Create Record
  • Delete Record
  • Get Record
  • Update Record
  • Search Records
  • Custom API Call

Available triggers

  • New or Updated Record

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Microsoft Dynamics 365 Business Central
  • Package: @activepieces/piece-microsoft-dynamics-365-business-central@0.3.0
  • Exact artifact digest: sha256:06b8fde1b2b7ee7c3a591993fe8eacc31bb27608b1185d53c30318f66fc3d587
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Record (create-record), Creates a new record. Classification: read.
  • Delete Record (delete-record), Deletes an existing record. Classification: read.
  • Get Record (get-record), Retrieves the details of a record by it's ID. Classification: read.
  • Update Record (update-record), Updates an existing record. Classification: read.
  • Search Records (search-records), Retrieves a list of records. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New or Updated Record, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects7
Supported actions6
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Access token Required · protected credential
  • Cloud Environment Required
  • Environment Required

Supported objects

ObjectReadWriteNotes
Create Record Yes No Creates a new record.
Delete Record Yes No Deletes an existing record.
Get Record Yes No Retrieves the details of a record by it's ID.
Update Record Yes No Updates an existing record.
Search Records Yes No Retrieves a list of records.
Custom API Call Yes No Make a custom API call to a specific endpoint
New or Updated Record Yes No polling trigger declared by the pinned package.

Supported actions

Create Record · Read

Creates a new record.

create_record · Risk: low · Retry: safe

Inputs

  • company_id · string · Required
  • record_type · string · Required
  • record_fields · object · Required
Delete Record · Read

Deletes an existing record.

delete_record · Risk: low · Retry: safe

Inputs

  • company_id · string · Required
  • record_type · string · Required
  • record_id · string · Required
Get Record · Read

Retrieves the details of a record by it's ID.

get_record · Risk: low · Retry: safe

Inputs

  • company_id · string · Required
  • record_type · string · Required
  • record_id · string · Required
Update Record · Read

Updates an existing record.

update_record · Risk: low · Retry: safe

Inputs

  • company_id · string · Required
  • record_type · string · Required
  • record_id · string · Required
  • record_fields · object · Required
Search Records · Read

Retrieves a list of records.

search_records · Risk: low · Retry: safe

Inputs

  • company_id · string · Required
  • record_type · string · Required
  • markdown · string · Optional, You can search on any and all of the property fields below. We'll return only exact matches (capitalization matters!) on all values provided.
  • record_filter_fields · object · Required
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New or Updated Record · Poll

Triggers when a new record is added or modified.

Inputs

  • company_id · string
  • record_type · string

Setup

Setup

  1. Add the Microsoft Dynamics 365 Business Central connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Cloud Environment (cloud), required.
  • Environment (environment), required.

OAuth scopes

  • https://api.businesscentral.dynamics.com/user_impersonation
  • https://api.businesscentral.dynamics.com/Financials.ReadWrite.All
  • openid
  • email
  • profile
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-microsoft-dynamics-365-business-central@0.3.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Microsoft Dynamics 365 Business Central connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-microsoft-dynamics-365-business-central@0.3.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com