Checklist — Xano Reusable Function

Standard: Xano Standards

1. Decision — Should This Be a Reusable Function?

EXTRACT TO A REUSABLE FUNCTION WHEN:
[ ] The same logic is used (or will be used) in 2 or more endpoints
[ ] The logic is complex enough to be worth isolating and testing independently
[ ] The logic represents a coherent unit: "check workspace permission", "format user object"

DO NOT EXTRACT WHEN:
[ ] It is only used once and is simple
[ ] It is one or two steps that read clearly inline
[ ] Extracting would require too many inputs, making it harder to understand

2. Naming

Function name describes exactly what it does using a verb_noun pattern
No vague names like helper, utility, or process_data
Name matches what it returns or does — not what calls it

3. Inputs, Logic, and Outputs

All inputs explicitly named and typed
No implicit global access — required data is passed as an input
Function does one thing only — single responsibility
No auth token validation inside the reusable function
Errors raised with the correct error format
Output is typed, documented, and consistent across code paths
On error, the function raises an exception — it does not return null or an empty object

4. Testing and Documentation

Function tested directly in Xano with success and failure cases
All calling endpoints re-tested after extraction
Function purpose, inputs, output, errors, and calling endpoints documented

Done When

Function extracted and named correctly
All inputs explicitly typed
Single responsibility — does one thing
Error handling is consistent with the rest of the codebase
All calling endpoints work after extraction
Function documented

Practice Task: Reusable Function Task