Skip to main content
Automations are custom server logic Bilt builds for your app — handling payments, sending emails, validating orders, reacting to events. They run on Bilt Cloud, not on the user’s phone, so secrets and sensitive logic never ship inside your app. There’s no deploy button: ask Bilt in chat and it writes, deploys, and wires up the automation. You monitor everything on the Automations tab under Settings → Database.

​
What you see

Each automation shows its name, who may call it, when it was last deployed, and its status. Open one to see:
  • Source — the actual deployed code, so you can read exactly what runs
  • Invocations — every run with status, duration, timestamps, log lines, and full error details when something fails

​
Who can call it

Each automation is either:
  • Sign-in required — only signed-in users of your app can call it (the default to keep)
  • Open to anyone — anyone with the URL can call it. Use this only for webhooks (Stripe, GitHub) and public APIs. Open automations are rate-limited to 60 calls per minute per caller, versus 600 for signed-in users
You can flip this per automation with Make public / Require JWT — Bilt warns you about the trade-offs before switching.

​
Deleting

Deleting an automation stops it immediately, but it stays restorable for 1 hour — ask Bilt to redeploy it under the same name to bring it back. After the hour, it and its logs are gone for good.

​
Good to know

  • Secrets (API keys and the like) live on the server and are available to your automations — they’re never bundled into the app. Bilt manages them for you when you ask for a feature that needs one
  • An automation can span multiple files, up to 1 MB of code
  • There’s no built-in scheduler yet — for a recurring job, use an external scheduler that calls a public automation’s URL on your cadence

​
Ask for it in chat

Questions? We're happy to help

Email support@bilt.me, or ask in the Discord community.