Microsoft Dynamics365 Business Central Zapier integrationAutomate Microsoft Dynamics365 Business Central with Zapier.
Microsoft Dynamics365 Business Central Zapier integration: 0 triggers, 1 action and 1 search. Business Central never starts the automation itself. Another app kicks it off, then Business Central answers: it finds a shipment by its number, or takes a request you write yourself.
Verified Trustpilot reviews · AI, automation & growth agency
What the Microsoft Dynamics365 Business Central Zapier integration actually does
This integration plugs Business Central, Microsoft's ERP for finance, operations and sales, into the other tools you connect through Zapier. It has no event of its own to start an automation, so Business Central always comes second: something happens elsewhere, then Zapier asks Business Central for a shipment or sends it a request.
A shipment number that turns into a full record. Find Shipment takes a company and a shipment number, looks the shipment up and hands it to whatever step comes next. Which details come back is something you check at the test, on a real shipment.
A request the ready-made list doesn't cover. API Request (Beta) lets you pick the HTTP method and the URL yourself, while Zapier adds the sign-in of your connection. It's the escape hatch when one search is not enough.
A step that stops when Business Central refuses. The same action carries a required Stop on error setting. On Yes, the step halts if Business Central returns an error and Zapier refreshes the sign-in on its own; on No, the step goes on regardless.
Now the limits, because they shape every Zap you build here. Nothing that happens inside Business Central can start a Zap through this integration: there is no trigger at all. There is no ready-made create or update action either. Anything beyond the shipment lookup goes through API Request (Beta), which Zapier still labels Beta, and its URL can only point to domains tied to the app. If you are still deciding whether Zapier is the right tool, see our Zapier review.
Zapier vocabulary in one minute
Eight words you will meet in the editor. Each is explained once here, then used as is.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. Business Central has none, so another app plays this role.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like API Request (Beta) here.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The number on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked on a timer for new items. An instant trigger is reported by the app itself, so nothing waits for the next check.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Search step
- A step that looks up something already stored in an app, so the steps that follow can use what it found. Find Shipment is one.
- Connection
- Your Business Central account, linked to Zapier once, then reused by every step that talks to Business Central.
What it really costs
Zapier bills tasks, not Zaps. The trigger never costs a task, and checking for new data costs nothing however often it happens. A task is counted only when an action completes; an action that fails is not counted.
- Free plan100 tasks a month, unlimited two-step Zaps
- TriggerNever costs a task
- Failed actionNot counted
- Search or filterMakes the Zap multi-step, paid plan
Business Central is not reserved for paid plans, so it works from the free plan: 100 tasks a month and unlimited Zaps, but each Zap stops at two steps, one trigger and one action. Add Find Shipment before an action, or a filter, and the Zap becomes a multi-step Zap, which needs a paid plan. The grid below only concerns a polling trigger, which here means the trigger of the app that starts your Zap, since Business Central has no trigger of its own.
Connect your Business Central account
- 01
Open the Apps page
Go to the Apps page of your Zapier account and click + Add connection. You need an account on Business Central, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 02
Pick Business Central
In the dialog, type Microsoft Dynamics365 Business Central, pick it from the results, then click Add connection. A new tab opens on the Business Central sign-in.
- 03
Sign in and grant access
Sign in with the account the Zap should act as, then grant Zapier access to it. From then on, every Business Central step in every Zap reuses this connection.
Your first Zap: a shipment number in a sheet, the shipment in your chat
GoalEach new row of a spreadsheet carries a shipment number. Zapier looks the shipment up in Business Central and posts what it found to your team chat.
- 01
Build: start from the other app
Create a Zap and pick your spreadsheet and its new-row event as the trigger. Business Central can't start a Zap, so the starting point always sits in another tool.
- 02
Test the trigger
Run the trigger test. Zapier brings back the three most recent rows of the connected sheet, so pick one that really holds a shipment number.
- 03
Add Find Shipment
Add a step, choose Business Central and Find Shipment. Choose the Company, then map the shipment number column from the test row into Shipment Number.
- 04
Send the result to your chat
Add the chat step and map the values Find Shipment returned into the message. Test each step once and read what came back before going further.
- 05
Publish
Click Publish to switch the Zap on. With a search in the middle, this is a multi-step Zap: it needs a paid plan. How fast it starts depends on the spreadsheet's trigger type, shown on that app's page.
The Business Central action
Microsoft Dynamics365 Business Central gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
API Request (Beta)
ActionIn Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”
Sends Business Central a request you build yourself: you choose the HTTP Method and the URL, and Zapier signs it with your existing connection. Stop on error is required and decides whether an error halts the step.
The Business Central search
1 search step looks for data that already exists in Microsoft Dynamics365 Business Central, so a later step can use it.
A search step reads, it does not write. In the editor, Business Central's search sits at the bottom of the Action event list, under the SEARCH heading. Some action fields also offer + Add search step, which inserts the search just before and wires its result in. Three settings decide what happens when the result is not the one you expected.
Find Shipment
SearchIn Zapier“Finds a shipment by Number”
Looks up one shipment from its number inside the company you pick, then hands it to the following steps. Both Company and Shipment Number are required.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?On apps that offer it, this box turns a search into a find-or-create. Business Central exposes no find-or-create variant, so Find Shipment stays a pure lookup.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When it breaks
The traps here come from Zapier's general rules and from the required settings of the action and the search. Six of them are worth knowing.
Read them before you publish. For the general method, see our Zapier troubleshooting guide.
No history is picked up
A Zap only reacts to what happens after you switch it on. Shipment numbers already sitting in your sheet are never looked up; moving that backlog is a separate job.Find Shipment finds nothing
On the default setting, an empty search stops the Zap and skips the steps that depended on it. Switch on Successful if no search results are found? only if the rest can run without it.Stop on error left on No
On No, API Request (Beta) carries on even when Business Central returns an error, so the next steps run on a failed answer. Yes halts the step instead.URL outside the app's domains
API Request (Beta) only accepts URLs on domains tied to the app. Any other address is refused, whatever the method you picked.A Zap that sets itself off
A Zap that writes into the very place its own trigger watches can start itself again and again and burn through tasks. Keep the trigger and the write apart.A sudden flood of rows
After a bulk import into the app that starts your Zap, a trigger returning a huge batch can be held back by Zapier's flood protection.
Need help automating Microsoft Dynamics365 Business Central with Zapier?
A person reads every message.
