Integration Procedures and Integration Definitions in automated processes
Key Takeaway
An Integration Procedure gets, saves, and transforms data. An Integration Definition specifies how data is sent to and received from an external service. When a Flow calls out, use a Process integration if the rep shouldn't have to wait for the response. Use an External Services Defined Integration Definition, with Integration Procedures as the input and output processors, to format requests and handle responses without Apex.
Integration Procedures and Integration Definitions are the no-code and low-code tools Agentforce Financial Services uses to move data between Salesforce and outside systems, such as a core banking system or a verification provider. An Integration Procedure is an Omnistudio server-side process that does its work in one server call, with no user interaction. An Integration Definition describes the connection to an external service, so Flows, Omniscripts, and Flexcards can call that connection. When you design automation that reaches outside Salesforce, you decide which tool does each job, which Integration Definition type to use, and whether the rep waits for the response.
What an Integration Procedure does
An Integration Procedure is a declarative, server-side Omnistudio process that runs multiple actions in a single server call. Fewer round trips to the server mean faster performance. The server is also usually faster than the client at processing data.
Use an Integration Procedure when no user interaction is needed while it runs and you want to retrieve, transform, and send data between Salesforce and external systems. Other good reasons to use one include:
- Bundling several operations in one server transaction
- Offloading work to the server
- Caching frequently accessed data
An Integration Procedure works behind the scenes and returns data to the tool that called it, such as an Omniscript or Flexcard.