Data & backend
Backend functions
Run server-side logic — webhooks, third-party calls, and secure operations — without standing up a backend.
When something has to happen on the server — not in the browser — Vorx generates a backend function for it. You describe the behaviour; Vorx writes the function, wires the route, and connects it to your UI.
When you need one
- Calling a third-party API with a secret key.
- Handling an incoming webhook (for example, a Stripe event).
- Work that must be trusted — anything a user shouldn't be able to tamper with.
- Anything heavy enough that you don't want it running in someone's browser.
The rule of thumb: if faking the request from a browser console would be a problem, it belongs on the server.
Describe the behaviour
When an order is marked shipped, call the shipping provider's API to buy a label and email it to the customer.
Vorx generates the function, decides when it runs, and hooks it up.
Secrets stay server-side
Functions read credentials from Settings → Cloud → Secrets, so API keys never ship to the client. See Secrets.
Run them on a schedule
A function can run on a timer instead of on demand — see Scheduled jobs, managed under Settings → Cloud → Jobs.
Watch and debug
There is no per-function run log yet (logs and monitoring). A function called on a schedule is the exception: its runs appear under Settings → Cloud → Jobs. Pasting a failed run's error straight into a prompt is usually the fastest way to a fix.
Next steps
- Secrets — credentials for third-party calls
- Scheduled jobs — running on a timer
- Logs and monitoring — watching runs in production