What is one of the categories of integration processes that is initiated by user actions?

In the context of integration processes that are initiated by user actions, the most suitable category is the ad-hoc request. An ad-hoc request refers to a process that is performed on an as-needed basis, typically in response to a specific user action or request. This type of process allows users to manually invoke integrations without prior scheduling or automation, thereby offering flexibility for one-off or infrequent tasks.

User-initiated actions often require immediate responses, which ad-hoc requests provide, facilitating quick access to real-time data or functionality. For instance, a user might need to retrieve updated customer information or execute a specific report, triggering an automated integration on demand.

In contrast, a scheduled process involves pre-defined times for execution, making it less dependent on direct user intervention. An automated process runs automatically based on certain criteria or triggers rather than requiring user action at the moment. A batch process typically involves the processing of a collection of records at once, often on a schedule, rather than being activated by users directly. Therefore, ad-hoc requests stand as the correct choice for user-initiated integration processes.