Call an OmniStudio Integration Procedure action directly via REST
domain: Salesforce OmniStudio · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify the Integration Procedure's Type and SubType (e.g., Type = 'Account', SubType = 'GetDetails'); these form the identifier used in the REST call.
POST to the Integration Procedure REST endpoint; the path pattern is /services/apexrest/{namespace}/v1/integrationprocedures/actions/{Type}/{SubType} — confirm the namespace ('omnistudio' or 'vlocity_cmt') for your environment.
Set the request body to {'input': { ... your input parameters ... }, 'options': {}} where options may include debug flags.
Include the Salesforce Authorization: Bearer {token} header.
Parse the response: a successful response contains an 'output' map with the procedure's return values; check for error keys in the response to detect procedure-level failures.
If the Integration Procedure calls external systems or uses Remote Actions, ensure the relevant Named Credentials or remote site settings are configured in the org.
Known gotchas
Integration Procedures must be in Active status to be invokable via REST; a draft or inactive procedure returns an error.
Input parameter names are case-sensitive and must match the IP's defined input variable names exactly.
Governor limits apply to Integration Procedure execution since it runs in an Apex context; complex procedures with many steps or callouts may hit SOQL query or callout limits.
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?