API-led connectivity is a powerful pattern in MuleSoft, but it is often over applied. Many teams introduce System, Process, and Experience APls even when reuse is limited and simpler approaches would be more effective. This session explores how overengineering MuleSoft integrations can increase cost, complexity, and resource consumption. We will walk through common scenarios where MuleSoft is overused, when Salesforce-native options like Flows with MuleSoft Connectors, external callouts, or Data Cloud may be a better fit, and how to right-size your architecture based on real business needs. Attendees will leave with a set of questions to ask before defaulting to API-led so you can tell the difference between integrations that deserve three layers and ones that don't.

Agenda:

5:15 - 5:45: arrival and networking. ***Please arrive by 5:45 as you need to be badged after 6p to use the elevator***

5:45 - 6:45: Presentation

6:45 - 7:00: Wrap-up