In OmniStudio (Vlocity) Salesforce, Integration Procedures (IP) are used to orchestrate data processing without writing Apex. One of the most important actions inside an Integration Procedure is DataRaptorPostAction, which allows you to insert, update, or upsert records in Salesforce using a DataRaptor Load (Post).
This post explains what DataRaptor Post is, when to use it, and how to configure it step by step inside an Integration Procedure.
What Is DataRaptor Post Action?
DataRaptorPostAction is used in an Integration Procedure to send data to Salesforce and perform DML operations, such as:
- Insert records
- Update records
- Upsert records
It uses a DataRaptor Load interface, which defines how incoming data maps to Salesforce objects.
When Should You Use DataRaptor Post in Integration Procedures?
Use DataRaptor Post when:
- You need to save OmniScript or API data into Salesforce
- You want to avoid Apex for DML operations
- You need high performance and bulk-safe processing
- You are updating records from OmniScript, FlexCard, or API requests
Step 1: Create an Integration Procedure
- Navigate to OmniStudio → Integration Procedures
- Click New
- Enter:
- Name
- Type (Reusable or Standard)
- Name
- Save the Integration Procedure
This Integration Procedure will act as the orchestrator for posting data.
Step 2: Add DataRaptorPostAction to the Structure Panel
- In the Structure panel, drag DataRaptor Post Action
- Place it at the correct position in the execution flow
- Rename it for clarity (example: Post_Account_Data)
Step 3: Configure DataRaptor Interface
In the DataRaptor Interface field:
- Select the DataRaptor Load (Post) that you want to use
- This DataRaptor must already be created and activated
This interface defines:
- Which Salesforce object will be updated
- Which fields will be mapped
- What operation will be performed (Insert / Update / Upsert)
Step 4: Configure Additional Input / Output / Failure Response
Inside DataRaptorPostAction, scroll to:
ADDITIONAL INPUT / OUTPUT / FAILURE RESPONSE
Important options:
Send Only Additional Input
- Set to True if you want to send only mapped input
- Set to False if you want to send full Integration Procedure data
Best Practice:
Set this to True for better performance and cleaner payloads.
Additional Output
You can define what response you want back from the DataRaptor, such as:
- Record Id
- Success flag
- Error message
Failure Response
Configure error handling to capture:
- Validation errors
- Required field errors
DML exceptions
Step 5: Configure Field Mapping in DataRaptor Load
Now open the DataRaptor Load (Post) used above.
Inside DataRaptor Load:
- Select the Target Object (e.g., Account)
- Choose the Operation Type:
- Insert
- Update
- Upsert
- Insert
- Map source fields to Salesforce fields
Step 6: Add ResponseAction to Send Data Back
To display or return results:
- Drag ResponseAction into the Structure panel
- Place it after DataRaptorPostAction
- Configure:
- Return Full Data JSON = True
OR - Return a specific node using %%PostResult%%
- Return Full Data JSON = True
This allows the Integration Procedure to return:
- Created/updated record Id
- Status of the operation
- Error messages (if any)
Step 7: Provide Input Parameters in Preview Tab
Go to the Preview tab of the Integration Procedure.
Example Input JSON:
{
“Name”: “Test Account”,
“Phone”: “1234567890”
}
These values must match:
- The input expected by the DataRaptor Load
- The field mapping defined earlier
Step 8: Execute the Integration Procedure
- Click Execute
- Check the response JSON
- Verify:
- Record is created or updated in Salesforce
- Record is created or updated in Salesforce
Response contains success or error details
Common Use Cases of DataRaptor Post in IP
- Save OmniScript form data
- Update Account, Contact, Case records
- Bulk record updates using ListAction + DataRaptor Post
- API-based data ingestion
- FlexCard action-based updates
Best Practices
- Always use Send Only Additional Input = True
- Validate required fields before posting
- Use ListAction for bulk updates
- Return minimal response data
- Handle errors using Failure Response
Common Mistakes to Avoid
- Using incorrect DataRaptor Interface name
- Missing required fields in input JSON
- Not activating DataRaptor Load
- Returning too much data in ResponseAction
- Skipping error handling
Conclusion
DataRaptorPostAction is the preferred way to perform create and update operations in OmniStudio Integration Procedures. It provides a declarative, high-performance, and scalable alternative to Apex, making it ideal for OmniScript and FlexCard integrations.
Mastering DataRaptor Post helps you build robust, maintainable OmniStudio solutions.