Flow Studio
Form Submission Data
How the Atlas Form's submitted field values become the UserFormNode's output — the output shape and downstream field access expressions.
Resume API Call
When the user submits the form, the FormRenderer component calls:
POST /api/executions/{executionId}/resume
Content-Type: application/json
Authorization: Bearer {actor-token}
{
"action": "submit",
"responseData": {
"approvalDecision": "approved",
"approvedAmount": 400.00,
"comments": "Approved with reduced amount - policy limit",
"attachmentId": "attach-xyz",
"reviewedAt": "2026-05-25T14:30:00Z"
}
}
Node Output Shape
The responseData from the resume call becomes the node output, wrapped with submission metadata:
{
"approvalDecision": "approved",
"approvedAmount": 400.00,
"comments": "Approved with reduced amount - policy limit",
"attachmentId": "attach-xyz",
"reviewedAt": "2026-05-25T14:30:00Z",
"_submittedAt": "2026-05-25T14:30:05Z",
"_submittedBy": "user-manager-bob",
"_action": "submit"
}
Downstream Access
// Node id = "expenseReview"
$output.expenseReview.approvalDecision // → "approved"
$output.expenseReview.approvedAmount // → 400.00
$output.expenseReview.comments // → "Approved with..."
$output.expenseReview._submittedBy // → "user-manager-bob"
File Attachments
File upload fields in Atlas Forms return an attachment reference ID, not the file bytes. To access the file content downstream, use the Entity capability to fetch the attachment record:
// In a downstream node config:
{
"serviceId": "attachment-service",
"operationId": "getAttachment",
"inputMap": {
"attachmentId": "$output.expenseReview.attachmentId"
}
}
Field naming: Form field keys in the output match the field key set in the Atlas Forms form builder — not the display label. Review the form's field configuration to know which keys to reference in downstream expressions.