OmniStudioArchitect (Hardest)integration-procedureinsuranceparallel
Architect Integration Procedure parallel HTTP actions for multi-carrier quote comparison
Real World Scenario
Broker OmniScript requests quotes from 4 carrier APIs sequentially; 20-second wait loses shopper to competitor site.
Expected Answer
• IP parallel HTTP actions invoke 4 carriers concurrently
• Aggregate response step merge quotes sort by premium
• Per-carrier timeout 5 seconds partial results if one slow
• Circuit breaker exclude carrier down after 3 failures session
• Named Credential per carrier OAuth isolation
• Display loading state per carrier OmniScript progress
• Cache quote 15 minutes same inputs reduce carrier API cost
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. IP parallel HTTP actions invoke 4 carriers concurrently. Aggregate response step merge quotes sort by premium. Pick based on your integration pattern and team capability. Sequential carrier calls lose shoppers—parallel IP with partial results beats perfect slow. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Sequential carrier calls lose shoppers—parallel IP with partial results beats perfect slow.