Save action results into calculated fields

Use Add result to form on a submission action to save a selected output into an ordinary calculated component. This works with AI and other submission actions; sign-in actions are excluded.

Create a saved result

1. Open the source action and select Add result to form.
2. Choose a label, result property and destination page.
3. Review the calculated field's Value source → Action result and visibility settings.
4. Run the source action with test data and inspect the saved field, later actions and the intended review/answer views.

The field updates immediately after its source action finishes, before the next action, redirect or review pause. Adding a field does not run its source action or backfill previous responses. Several fields can share one source.

Value-source settings reference

Setting	Property	Behaviour
Action result	actionResultSourceId	The existing submission action ID. Do not also configure prepopValue.
Select result	actionResultSourceMode	path (default) or liquid.
Result property	actionResultPath	Dotted path relative to the stored action result, for example response.summary.
Result template	actionResultTemplate	Liquid evaluated after the action using the current form context. Objects/arrays remain structured.

Use the action's actual result shape. AI summaries use response.summary; categorisation can use response.categoryId, response.categoryLabel or response.status. API responses, including HTTP 300–399 results, may expose bodies and headers.

Visibility settings reference

Setting	Property	New action-result default
Show on service page	calculatedShowOnPage	false
Show on applicant check answers	calculatedShowOnApplicantAnswers	false
Show in reviews	calculatedShowOnReview	true

These are independent string true/false settings. Applicant answer PDFs follow applicant visibility; authorised reviewer answers follow review visibility. A saved result is read-only and escaped for display. To collect a person's decision, use a separate input rather than making the generated value their answer.

Missing, failed or oversized results

New services limit a selected result to 128 KiB of UTF-8 JSON; legacy services retain a 1 MiB extraction bound. The server-controlled creation version determines compatibility; it is not a setting to edit.

Missing, offloaded, invalid or oversized values clear the previous field value and record an error under actions.actionId.resultFieldErrors.fieldId. Strict Liquid missing-variable errors also clear it. Extraction errors do not change the source action's success, failure alerts or charging; a successful AI call remains chargeable if saving its result fails.

On source failure, extraction exposes only error, response code, execution time and result-field errors. A retained success response cannot be saved as a new result. Check the action outcome and field outcome separately.

Test before deployment

Test success, no match where relevant, source failure, missing paths, malformed/large values, reruns after earlier success and all three visibility choices. Confirm later actions see the updated value in the intended order. A page refresh alone does not execute an action-result field's source.

See Calculated components, Actions and workflows and Response Hub.