A finance manager finishes invoicing a batch of customers in Microsoft Dynamics 365 Business Central and wants those people texted straight away rather than chased up next week. Business Central covers finance, operations, sales and customer service in one system, so plenty of moments inside it are worth a text, a paid order, an updated customer record, a job marked complete.

The catch is that this integration only offers one item on the Zapier side, the API Request (Beta) action, which sends a raw HTTP call carrying Business Central's own authentication. There's no trigger here, so a Zap can't start the moment something changes inside Business Central. What it can do is sit at the end of a Zap and post data into Business Central once another app, or Mobile Message, has already done its part.

In practice that means a Zap can start from Mobile Message's Inbound SMS Received or Delivery Status Updated trigger and use the API Request action to record that reply or delivery outcome against a Business Central record, a workaround rather than a built in connection. Anyone comfortable with Business Central's own API endpoints and authentication can wire this up in Zapier, though it takes more setup than a standard trigger and action pairing.