Calculation Procedures are OmniStudio objects that define multi-step calculation logic (similar to a spreadsheet); Calculation Matrices are lookup tables used within procedures to return values based on input combinations.
Create a Calculation Matrix in OmniStudio: define the input columns (lookup keys) and output columns (result values), then populate rows with the lookup data.
Create a Calculation Procedure and add steps that reference the Calculation Matrix for lookups; the procedure can also perform arithmetic, conditional logic, and aggregation across steps.
Invoke the Calculation Procedure from an Integration Procedure by adding a Calculation Procedure action step; pass input parameters and retrieve output variables.
Alternatively, invoke a Calculation Procedure directly via the OmniStudio REST API if your version supports direct invocation — verify the endpoint pattern against your namespace documentation.
Test Calculation Procedures using the built-in debug/test panel in the OmniStudio Calculation Procedure editor before wiring them into Integration Procedures.
Known gotchas
Calculation Matrices perform exact-match lookups by default; if the input values do not exactly match a matrix row, the lookup returns no result, which may propagate as null or zero in the procedure — design with a default/fallback row.
Step execution order in a Calculation Procedure matters; steps can reference outputs from earlier steps, but referencing a later step's output from an earlier step will produce null.
Calculation Procedures and Matrices must be activated before use; changes made in the editor do not take effect until the procedure is saved and activated.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp