Which functionality is not offered by flows?

Flows in Salesforce offer a range of automation functionalities, allowing users to create, manage, and manipulate data efficiently. However, sending an outbound message is a capability that is not natively supported by flows. While flows can initiate a variety of actions such as updating records or calling Apex classes, they do not directly handle outbound messages. Outbound messages are typically associated with workflow rules, which can send messages to external web services when certain criteria are met.

The other functionalities listed are indeed part of what flows can do. For example, flows can automate data updates by allowing users to modify existing records through a series of steps, which can include gathering user input or processing data based on specific criteria. Similarly, flows can be designed to create records, and while flows are generally designed for individual record creation, they can utilize other strategies or tools to manage bulk record creation efficiently.

Triggering workflows, although an older automation technique than flows, is another aspect that flows are designed to handle indirectly. Flows can execute actions that could lead to workflow triggers, but they operate under a different logic framework than traditional workflow rules.

Understanding the unique capabilities of each automation tool within Salesforce helps ensure that organizations utilize the right tools for their specific business processes.