What does Make list for Business Central?
Make lists 8 Business Central modules and labels the app Enterprise, supported and maintained by Make. Module names and counts are copied from Make's Business Central page as read on November 17, 2026. Make updates its apps, so treat this as a snapshot and check the page before you scope work.
- Trigger (1): Watch Records.
- Searches (2): Search Records, Search Records (Advanced).
- Actions (5): Create a Record, Delete a Record, Get a Record, Make an API Call, Update a Record.
Make's Enterprise label matters for scoping: check which Make plan includes the app before you commit. Our Make Enterprise page explains how we scope against it.
Which systems connect to Business Central?
Any app in Make's app list can sit on the other side of a Business Central scenario. Make's own page says you can integrate over 3,500 apps. The table is a sample of the kinds of system finance and IT teams ask us to connect, with the hand-off we usually build.
| App in Make | Kind of system | Typical hand-off with Business Central |
|---|---|---|
| CRM | A won deal creates the customer and sales order in Business Central; the order number and status go back to the CRM. | |
| CRM | A won deal creates the customer and sales order in Business Central; the order number and status go back to the CRM. | |
| Ecommerce | Web orders become Business Central sales orders; shipment and tracking updates go back to the store. | |
| Ecommerce | Web orders become Business Central sales orders; shipment and tracking updates go back to the store. | |
| Payments | Payment and payout records are matched to open invoices; anything that does not match goes to a person. | |
| Payments | Payment and payout records are matched to open invoices; anything that does not match goes to a person. | |
| Payroll and HR | Payroll or HR results are checked, then posted to Business Central after a named person approves them. | |
| Payroll and HR | Payroll or HR results are checked, then posted to Business Central after a named person approves them. | |
| Expenses and procurement | Approved expenses and purchase orders are created or matched in Business Central; exceptions wait in a queue with an owner. | |
| Expenses and procurement | Approved expenses and purchase orders are created or matched in Business Central; exceptions wait in a queue with an owner. | |
| Expenses and procurement | Approved expenses and purchase orders are created or matched in Business Central; exceptions wait in a queue with an owner. | |
| Tax | Tax lookups for a document are made and stored; a failed lookup stops the write and alerts an owner. | |
| Support | Order and customer context shows up in the ticket; credits and refunds are raised for approval, not posted automatically. | |
| Support | Order and customer context shows up in the ticket; credits and refunds are raised for approval, not posted automatically. | |
| Support | Order and customer context shows up in the ticket; credits and refunds are raised for approval, not posted automatically. | |
| Chat, email and files | Approvals, alerts and documents move between Business Central and the places your team already works. | |
| Chat, email and files | Approvals, alerts and documents move between Business Central and the places your team already works. | |
| Chat, email and files | Approvals, alerts and documents move between Business Central and the places your team already works. | |
| Spreadsheets and BI | Search results load on a schedule into a sheet or database, with a row-count check against Business Central. | |
| Spreadsheets and BI | Search results load on a schedule into a sheet or database, with a row-count check against Business Central. | |
| Spreadsheets and BI | Search results load on a schedule into a sheet or database, with a row-count check against Business Central. | |
| Spreadsheets and BI | Search results load on a schedule into a sheet or database, with a row-count check against Business Central. | |
| SFTP, FTP and HTTP | Partner and EDI files | Partner files arrive by SFTP or an API call; a scenario validates each one, creates the records, and rejects bad files with a reason. |
We build partner and EDI hand-offs around whatever your EDI provider exposes: file drops over SFTP or FTP, or API calls over HTTP. Make lists apps for all three. Being listed does not mean every module suits your job; we scope against the modules.
Which Business Central module fits which job?
Make's Business Central list is short, so the choice is simple: watch for changes, search for lists, read or write one record, and use the raw API call when the job is not covered.
- Watch Records is the one trigger, for reacting when records change.
- Search Records and Search Records (Advanced) return lists to work through; the Advanced one is for more precise filtering.
- Get a Record, Create a Record and Update a Record read and write one record at a time. Delete a Record is there, and we only use it where you have asked.
- Make an API Call reaches Business Central endpoints the other modules do not cover. Microsoft's API v2.0 reference lists the endpoints Microsoft publishes, and a scenario that uses one is only as stable as that endpoint.
- Make lists no file module for Business Central, so documents such as invoice PDFs are stored in your document store and linked from the record, or sent through Make an API Call where Microsoft's API supports it.
What do you settle before the first scenario goes live?
A short list, agreed before we build, so the first scenario is safe to turn on and someone is accountable for it.
- Pick one process, and name the person who owns it.
- Decide what the scenario may read and what it may write. We start read-only and add writes one at a time.
- Use a dedicated integration user in Business Central with the narrowest permissions that work, never a person's login.
- Name who receives the error alert and who fixes the problem.
- Test against a sandbox or a copy of your data first, if you have one.
- Decide how long run history must be kept for audit.
Frequently asked questions
Does connecting Business Central through Make replace or change our setup?
No. Scenarios read and write Business Central records through Make's modules. Your configuration, extensions and users stay yours, and we ask for a dedicated integration user with the narrowest permissions that work.
Can we connect a system that has no Make app?
Often, yes. Make lists an HTTP app for calling web APIs and FTP and SFTP apps for file drops. We confirm the other system's API or file options before we promise anything.
Which Make plan do we need?
Make labels the Business Central app Enterprise on its page. Make describes its plans on its own pages and our Make Enterprise page explains how we scope against them. This page does not quote Make's prices or ours.
Where do we start?
Book a 15-minute call and bring the one Business Central process that takes your team the most hours. We will review it with you.
Want us to look at your Business Central processes?
We build and run automations and integrations around your existing Business Central; we do not replace it. See our Business Central guides and services, and the Make Enterprise Business Central page, and the workflow automation page.





