Backend

Tables and schema changes, edge functions, scheduled jobs, access rules, secrets and member login.

Get started

• Get started with your backend: Every Willo business has its own backend for data, member logins, files and server code. What it does, when it appears, and how you work with it.

Concept

• Tables and access rules: How your backend decides what visitors and members can read and write, why a new table starts locked, and how Willo proves the rules work.
• Change your database safely: Why Willo adds before it removes, what a draft does to a database change, and when deleting a table or column needs your explicit say-so.
• Backend functions: What backend functions are for, who can call them, how Willo deploys and checks them, and why a function with admin powers needs a caller check.
• Secrets and API keys: How to give Willo an API key without pasting it into chat, where keys are stored, test keys for drafts, and the credentials Willo never asks for.
• Scheduled backend jobs: Run one of your backend functions on a timer, such as a nightly digest or an hourly sync. How often each plan allows, the limits, and how usage is counted.
• Member login and login email: How member accounts on your site work, why login emails stop after a couple of sends, and how connecting your own Resend account lifts the limit.

Guide

• Add a table and show it on the site: Store something new in your backend, such as events or a team list, and show it on a page, with the right access rules, tested before it goes live.
• Run a job on a schedule: Set up a backend job that runs on its own every day or hour, such as a morning summary email, then check that it ran and change or stop it.
• Connect an outside service: Wire your site to a service you already use, such as an email, SMS or AI provider, by giving Willo its API key safely and letting it build the function.