Order JSON
textareaRequired input
Noderan MarketplaceCustomer Support
Demo ReadyLive E2E verifiedDeterministic~10s
Refund Policy Decision Helper
Validates request shape and returns review warnings.
Check refund request JSON against pasted policy context.
Before you run
Workflow summary
Check refund request JSON against pasted policy context.
What is Refund Policy Decision Helper?
Refund Policy Decision Helper is a ready-to-run Noderan marketplace workflow for customer support teams. It helps users move from a manual process to a repeatable automation with visible credit cost and app-based execution.
- Who is it for?
- Support and billing operators
- What problem does it solve?
- Check refund request JSON against pasted policy context.
- How does it work?
- Check refund request JSON against pasted policy context.
- How does pricing work?
- 1 credit per run.
- What is the next action?
- Open the app marketplace to activate this workflow, or review credit pricing.
Refund Policy Decision Helper FAQ
Short answers for activation, pricing, inputs, and execution review.
Validates request shape and returns review warnings.
Expected inputs
Policy text
textareaRequired input
Demo input
Order Json
{"orderId":"ord_123","daysSincePurchase":12,"reason":"duplicate"}Policy Text
Refund duplicates within 30 days after verification.View raw JSON
{
"orderJson": "{\"orderId\":\"ord_123\",\"daysSincePurchase\":12,\"reason\":\"duplicate\"}",
"policyText": "Refund duplicates within 30 days after verification."
}Output highlights
- valid
- topLevelKeys
- normalized
- warnings
Example result
Valid
EnabledTop Level Keys
namestatus
Normalized
NameAlpha
Statusready
Warnings
Refund request is structurally valid and needs duplicate verification.
View raw JSON
{
"valid": true,
"topLevelKeys": [
"name",
"status"
],
"normalized": {
"name": "Alpha",
"status": "ready"
},
"warnings": [
"Refund request is structurally valid and needs duplicate verification."
]
}Use cases
- Structure refund review before a human decision.
Step 1
Review the workflow and expected credit cost.
Step 2
Connect the tools or inputs required for execution.
Step 3
Run the workflow and inspect outputs in the app history.