Definition
Integration Procedure is a Salesforce automation capability that triggers predefined actions based on conditions or events. It reduces human error and speeds up business processes by handling routine operations programmatically.
Real-World Example
Consider a scenario where the Salesforce admin at FreshStart Inc. is working with Integration Procedure to automate a multi-step process that previously required three different people to complete manually. Integration Procedure now handles the entire sequence in seconds, sending notifications at each step and logging every action for audit purposes.
Why Integration Procedure Matters
Integration Procedures in Salesforce Industries (Vlocity) are server-side, declarative processes that orchestrate multiple data operations — including Salesforce DML, external API callouts, data transformations, and conditional logic — into a single, optimized transaction. Unlike Flows that execute each step sequentially with separate server round-trips, Integration Procedures batch operations together and execute them in a single server call, dramatically reducing processing time. They are the backbone of OmniScript-driven user experiences, providing the data layer that fetches, transforms, and saves complex data structures. This makes them essential for industries like telecommunications, insurance, and healthcare where a single customer interaction may require pulling data from five or more systems simultaneously.
As business processes grow more complex, Integration Procedures become critical for maintaining performance at scale. A quoting process that individually calls pricing APIs, inventory systems, and discount engines would take 15 seconds with sequential callouts but completes in 2 seconds when orchestrated through an Integration Procedure that parallelizes the calls. However, poorly designed Integration Procedures that fetch too much data or make unnecessary callouts can become performance bottlenecks themselves. Organizations must profile and optimize their Integration Procedures regularly, using the built-in preview and debug tools to identify slow steps. Teams that treat Integration Procedures as 'set and forget' components often discover during load testing that what worked for 100 users fails spectacularly for 1,000 concurrent users.
How Organizations Use Integration Procedure
- FreshStart Inc. — FreshStart's admin built an Integration Procedure that automates a customer onboarding process previously requiring three people. The procedure creates the Account, generates a welcome email via an external email service, provisions the customer's portal access, and logs the onboarding completion — all in a single 3-second transaction. What used to take 45 minutes of manual work across departments now completes instantly when a sales rep clicks 'Activate Customer.'
- TelcoMax Communications — TelcoMax uses an Integration Procedure behind their OmniScript-based order entry screen to simultaneously query their network inventory system for available equipment, fetch real-time pricing from the billing platform, and check credit scores from an external bureau. The Integration Procedure parallelizes all three callouts and returns consolidated results in under 2 seconds, enabling customer service reps to present complete order options during a live phone call without awkward hold times.
- PremierHealth Systems — PremierHealth's Integration Procedure orchestrates patient intake by pulling insurance eligibility from a clearinghouse API, retrieving the patient's medical history from an external EHR, and creating the visit record in Salesforce Health Cloud. The procedure includes conditional logic that routes uninsured patients to a financial counselor workflow. Processing 500 daily patient intakes that previously required 10 minutes of manual data gathering each now takes 4 seconds per patient.