APIs and automations

Real apps do more than show pages. Vorx can add server-side logic so your app reacts to what happens and talks to the world outside it.

Call external services

Ask your app to reach out to an API — "look up the address from a postcode," "pull the latest exchange rate." Vorx wires the call and handles the response. Pointing it at the provider's docs URL usually saves a round of clarification.

React to events

Describe what should happen when something occurs:

When an order is placed, email the customer a receipt and post a message to our Slack.

Vorx builds the trigger and the action as a backend function.

Run work on a schedule

Some things should happen on their own. "Every morning, send me a summary of yesterday's sign-ups" or "archive expired sessions nightly" — Vorx sets up the scheduled job.

Receive webhooks

Automations run in both directions. Vorx can expose an endpoint for another service to call — a Stripe event, a form provider, an internal tool — and act on what arrives.

Keep keys safe

Automations that talk to other services need credentials. Store them under Settings → Cloud → Secrets so they're never written into your app's code or exposed to users. See Secrets.

Watch them run

A scheduled automation's runs are recorded under Settings → Cloud → Jobs with their timing and status. Automations triggered another way have no run log yet (logs and monitoring). When an automation "didn't work", the logs almost always say whether it fired at all — which is the first thing worth knowing.

Calling Vorx itself

This page is about your app calling out. If you want to script Vorx from outside — backups, internal tooling — see Using the Vorx API.

Next steps

• Backend functions — where this logic lives
• Scheduled jobs — recurring work
• Integrations — the services wired up for you