You are here:
Integration Procedure Actions
To compose an Integration Procedure, you add actions that run sequentially. These actions can set data values, perform functions, call Omnistudio Data Mappers, invoke Apex classes, send emails, invoke REST endpoints, run other Integration Procedures, and more.
To add actions, drag elements from the Action elements panel to the canvas or use the connectors (+) directly on the canvas. You can easily add, edit, rename, move, or delete actions, and rearrange elements between blocks using +. You can also use blocks to group actions for conditional execution, caching, list processing, and error handling.
This table describes the properties common to all Integration Procedure Actions.
Property |
Description |
|---|---|
Element Name |
Name of the element or node. |
Send JSON Path |
Trims the incoming JSON to the specified path before the action is executed. See Manipulate JSON with the Send/Response Transformations Properties. |
Send JSON Node |
Reparents the incoming JSON under the specified node. See Manipulate JSON with the Send/Response Transformations Properties. |
Response JSON Path |
After the action is executed, trims the output JSON to the specified path. See Manipulate JSON with the Send/Response Transformations Properties. |
Response JSON Node |
Reparents the output JSON under the specified node. To delimit the path, use colons;
for example, |
Send Only Additional Input |
If checked, accepts only the data in the Additional Input property. |
Additional Input |
Additional key-value pairs to be included in the input JSON data. Values can include formulas and merge fields. |
Return only additional output |
Returns only the data in the Additional Output property. |
Additional Output |
Additional key-value pairs to be returned in the output JSON data. Values can include formulas and merge fields. |
Send Only Failure Response |
Returns only the failure response if the action fails. |
Failure Response |
Key-value pairs to be returned in the output JSON data if the action fails. Values can include formulas and merge fields. |
Execution Conditional Formula |
Specifies a formula that runs before the step is executed. If the formula returns TRUE, the step is executed. If the formula returns FALSE, the step isn't executed. If no formula is specified, the step is executed. |
Failure Conditional Formula |
Specifies a custom failure condition that runs after the step is executed. For example, the Omnistudio Data Mapper Extract Action failing to find any records isn't normally considered an error. But you can use a Failure Conditional Formula to specify this condition. See the second example under Handle Errors by Using a Try-Catch Block. If the formula returns TRUE, execution of the step has failed and any key-value pairs configured in the Failure Response list are added to the JSON data. For example, if this JSON is returned: These settings identify the error and add the error code to the JSON data:
|
|
The Integration Procedure ends if this step fails. |
Chain On Step |
Allows the action to run in its own Salesforce transaction. This property can slow performance but decreases the likelihood of exceeding the Salesforce governor limits. For more information, see Settings for Long-Running Integration Procedures. |
Additional Chainable Response |
Specifies a key-value pair that is sent in the response. The value field accepts merge field syntax. |
- Assert Action for Integration Procedures
The Assert Action compares the expected and actual results of a Test Procedure using an expression that evaluates to true or false. You can use environment variables in the Assert Conditional Formula to test performance. - Chatter Action for Integration Procedures
The Chatter Action creates a Chatter post and sends it to a Chatter feed. - Decision Matrix Action for Integration Procedures
The Decision Matrix Action calls a Decision Matrix with specified inputs and returns the result to the Integration Procedure. - Delete Action
Enable users to delete one or more sObject records by using the Delete Action. Use an Object's Record Id to determine which record to delete. Vlocity recommends using a merge field in the Path to Id field that refers to an Id or a list of Ids in the data JSON. - Docusign Envelope Action for Integration Procedures
The Docusign Envelope Action emails a set of documents for signing. - Email Action for Integration Procedures
An Email Action sends the specified email. You can either specify all the email field values or use a Salesforce email template. - Expression Set Action for Integration Procedures
An Expression Set Action invokes the specified Expression Set and returns the results to the Integration Procedure. - HTTP Action for Integration Procedures
The HTTP Action executes a REST call and returns its results to the Integration Procedure. The HTTP Action in Integration Procedures supports only getBody() for returning the response. Use Apex directly via a Remote Action to handle binary responses. - Integration Procedure Action for Integration Procedures
The Integration Procedure Action runs a subordinate Integration Procedure. - Intelligence Action for Integration Procedures
The Intelligence Action provides input to and runs an Intelligence Machine on Omnistudio. - List Action for Integration Procedures
The List Action merges multiple lists by matching values of specified list item JSON nodes. A basic merge matches node names exactly. An advanced merge matches nodes that have different names or reside at different levels in the incoming lists. - Omnistudio Data Mapper Extract Action for Integration Procedures
The Data Mapper Extract Action calls the specified Data Mapper Extract to read data from Salesforce and returns it to the Integration Procedure. - Omnistudio Data Mapper Post Action for Integration Procedures
The Data Mapper Post Action calls a Data Mapper Load (post) to write data to Salesforce. - Omnistudio Data Mapper Transform Action for Integration Procedures
A Data Mapper Transform Action calls the specified Data Mapper Transform to execute transformations on the Data JSON and returns the transformed data. - Omnistudio Data Mapper Turbo Action for Integration Procedures
A Data Mapper Turbo Action calls the specified Data Mapper Turbo Extract to read data from Salesforce and returns it to the Integration Procedure. - Remote Action for Integration Procedures
The Remote Action element calls the specified Apex class and method or the specified invocable action. - Response Action for Integration Procedures
The Response Action ends an Integration Procedure and returns data to the entity that called it. It can also add data to the data JSON or end conditionally. Response Actions are useful for debugging Integration Procedures. - Set Values Action for Integration Procedures
The Set Values action sets values in the data JSON of an Integration Procedure using literal values, merge fields, or formulas.

