Dashboard → Backend Functions

Backend Functions are small pieces of your app that run on Buildy's servers instead of in a visitor's browser. That is the right place for anything secret or heavy, like talking to an outside service, processing a payment callback, or sending a private notification. You will find this section under Advanced in the Dashboard sidebar.

The Backend Functions screen

Preview image unavailable

The screenshot couldn't load right now, but you can still follow the steps below.

What is inside

Your app's backend functions

This screen lists every backend function Buildy has created for your app. Each one is a named helper that runs on the server when something needs to happen behind the scenes.

Most of the time you will not write these yourself. You describe the outcome you want in chat, and Buildy creates the function and keeps this list up to date.

A web address for each function

Every function gets its own URL (web address). Other services can call that address when something happens on their side.

That pattern is called a webhook. For example, a payment provider can hit your function's URL after a successful charge so your app can update an order or send a confirmation.

Logs and errors

Each function keeps logs: a running record of what it did when it ran, and whether it hit an error.

When an integration feels broken, logs are often the fastest way to see what actually failed. You can open them here, or ask Buildy in chat to read them for you.

How it works with chat

Ask for the outcome you want, not the technical setup. Buildy writes the function, deploys it, and stores any secret keys securely so they never sit in your site's visible code.

Try asking:

Notify me on Slack when someone places an order
Connect my app to Stripe so payments update my orders
When a form is submitted, send the data to my CRM webhook
Show me the logs for the function that handles new bookings

Good to know

Deploys happen automatically

When Buildy creates or changes a backend function, it deploys right away. There is no separate deploy button or manual publish step for functions.

Secrets stay on the server

API keys and other secrets belong in backend functions, not in page code visitors can view. Buildy stores them securely when it sets up the connection for you.

Most users only visit when something breaks

Day to day, you build by talking to Buildy. Open Backend Functions when you want to confirm a function exists, copy its webhook URL for an outside service, or check logs after an error.

Pro tip: let Buildy read the logs

If an integration seems broken, tell Buildy in chat what you expected and what happened instead. It can open the function's logs, find the real error, and fix the code without you digging through technical messages by hand.

Relevant Keywords: backend functions, server, webhooks, API, logs, secrets.