---
schema_version: "1"
id: c796a14738f2ba78eb1d099c7d42b1da87225c9df5484f2435b948d6f5366875
title: Invoke an Integration Procedure
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_integration_procedure_invocation_55721.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_integration_procedure_invocation_55721.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 6baebf22a3539e7929d96686a98ec3058c31f7c64efeffdde6d6b6a7b97326be
description: You can invoke Integration Procedures from other Omnistudio tools such as Omniscripts and Cards. You can also invoke Integration Procedures from Apex classes, batch jobs, REST APIs, or Salesforce flows.
products:
  - Omnistudio
release: "264"
---
# Invoke an Integration Procedure

You can invoke Integration Procedures from other Omnistudio tools such as Omniscripts and Cards. You can also invoke Integration Procedures from Apex classes, batch jobs, REST APIs, or Salesforce flows.

- **[Integration Procedure Invocation from Apex](https://help.salesforce.com/s/articleView?id=xcloud.os_integration_procedure_invocation_from_apex_55724.htm&release=264.0.0&type=5)**  
    Starting with Summer’ 25, use the ConnectAPI.OmniDesignerConnect.integrationProcedureExecute(ipName, apexInput) Connect API for Integration Procedure calls from the IntegrationProcedureService Apex class. This Connect API removes the dependency on the managed package and provides up to 21% better performance for Integration Procedure calls from an Apex class compared to the previous method.
- **[Integration Procedure Unit Testing from Apex](https://help.salesforce.com/s/articleView?id=xcloud.os_integration_procedure_unit_testing_from_apex_55739.htm&release=264.0.0&type=5)**  
    You can set up a test class in Apex and use it to call and test an Integration Procedure. In the core runtime, HTTP mocking isn’t possible, and real HTTP calls occur during test execution.
- **[Integration Procedure Invocation from REST APIs](https://help.salesforce.com/s/articleView?id=xcloud.os_integration_procedure_invocation_from_rest_apis_55792.htm&release=264.0.0&type=5)**  
    With a REST API, you can use either a GET or a POST call to invoke an Integration Procedure and retrieve the result. The difference between the two is that a GET call can't pass data with a JSON request body.
- **[Integration Procedure Invocation from Salesforce Flow](https://help.salesforce.com/s/articleView?id=xcloud.os_integration_procedure_invocation_from_salesforce_flow_55876.htm&release=264.0.0&type=5)**  
    To call an Integration Procedure from a Salesforce Flow, create a Salesforce Flow component by defining a class using the Salesforce Developer Console, as shown in the following example. Note that the class must have the `@InvocableMethod` annotation.
- **[Batch Jobs for Integration Procedures and Vlocity Open Interfaces](https://help.salesforce.com/s/articleView?id=xcloud.os_batch_jobs_for_integration_procedures_and_vlocity_open_interfaces_55910.htm&release=264.0.0&type=5)**  
    The Vlocity batch framework lets you run an Integration Procedure or VlocityOpenInterface on a schedule. Typical use cases are a recurrent billing cycle or a scan for insurance policies that come up for renewal in the next 60 days. When a job is run, it sends its input to an Integration Procedure or Apex method that processes the records.