Integrations

Vorx wires up common services so you don't have to read three sets of API docs. You name the tool and what you want it to do; Vorx builds the flow and the backend behind it.

Add an integration

Describe the outcome, not the API:

Take payments with Stripe for a monthly subscription, and email a receipt after each successful charge.

Vorx sets up the calls, the webhooks, and the UI, reading any credentials from secrets.

Bring your own keys

For a service tied to your account, add its API key under Settings → Cloud → Secrets and tell Vorx to use it. Keys stay server-side and never reach the browser.

Use the provider's test key while you're building, and swap it for the live key before you go live — a secret holds one value for the project, so whatever is set is what the published app uses too. See Environments.

What's built in

• Payments — Stripe checkout and subscriptions, under Settings → Cloud → Payments. See Payments.
• Email — transactional email from your own domain, under Settings → Cloud → Email. See Custom emails.
• Social sign-in — Google and Microsoft, under Settings → Cloud → Social login. See Social login.
• Storage — file uploads, under Settings → Cloud → Storage. See Files and storage.
• Analytics — built in on every published app, under Settings → Analytics. See Analytics.
• AI — chat, summaries and image generation with no keys. See AI features.

Custom APIs

Calling a service Vorx doesn't know about? Point it at the API — the docs URL is often enough — and Vorx generates a backend function to talk to it securely.

When an integration misbehaves

Most integration problems are credentials rather than code. Check the key is set, that it's the right key for the environment you're testing, and then paste the error your app shows into chat — there is no call log to read yet (logs and monitoring).

Next steps

• Secrets — storing credentials safely
• Backend functions — where third-party calls run
• APIs and automations — reacting to events