Which OmniStudio action should you use to perform post-processing after a DataRaptor load?

Which OmniStudio action should you use to perform post-processing after a DataRaptor load?

• A. DataRaptor Load Action
• B. DataRaptor Post Action
• C. HTTP Action
• D. Integration Procedure Action

Answer: (B)

Post-processing after you load data with DataRaptor is handled by the DataRaptor Post Action. This dedicated step runs immediately after the Load Action, giving you a built-in hook to apply follow-up processing—such as adjusting fields, updating related records, or kicking off additional logic—using the data that was just loaded. The Load Action performs the actual data write, so you wouldn’t use it for post-load work. An HTTP Action is for calling external APIs, and an Integration Procedure Action would run a separate procedure; while those can be used for further steps, the Post Action is the designed mechanism for actions that should occur right after a DataRaptor load.

Post-processing after you load data with DataRaptor is handled by the DataRaptor Post Action. This dedicated step runs immediately after the Load Action, giving you a built-in hook to apply follow-up processing—such as adjusting fields, updating related records, or kicking off additional logic—using the data that was just loaded. The Load Action performs the actual data write, so you wouldn’t use it for post-load work. An HTTP Action is for calling external APIs, and an Integration Procedure Action would run a separate procedure; while those can be used for further steps, the Post Action is the designed mechanism for actions that should occur right after a DataRaptor load.