Can my app's backend take a form, keep a status history and send emails?
Yes, on your own Supabase. Describe it in Developer → Backend, for example: "visitors send the onboarding form; keep a history of each request's status; email the sales team about each new request". Furge writes it into your database and tests it as each kind of person before you apply it. An endpoint is a checked way to add a row: it checks every value and how often each person sends (5 an hour, say), and the table can be made to take rows only through it. A history keeps every change of a column, with who made it and when; whoever can read the record reads its history, and nobody can write it. An email goes to the holders of a role, the record's owner or you, when a row is added or a column changes. Your database queues it, and Furge sends it from Furge's address, up to 300 a day. Text messages, WhatsApp and push notifications can't be sent yet.
Steps
- Turn on Developer at the top of the studio (or press Shift+D) and open Backend.
- Describe the form, the history or the email, and press Change with Furge AI.
- Check it: the Tests tab tries each one as a visitor, a signed-in person and each role; the API tab shows how your app calls the endpoint.
- Apply it. In History, Emails says how many are waiting and sent; Send now sends what's waiting.
Also asked as
- send emails from my backend
- email my team when
- email sales when
- notify staff
- notification email
- email when status changes
- status history
- keep a history
- audit trail
- who changed the status
- track changes
- endpoint
- api endpoint
- form endpoint
- rate limit my form
- stop spam on my form
- validate my form
- supabase function
- rpc
- onboarding form
- contact form backend
Related
Still stuck? Ask Furge Help, the round chat button at the bottom right, or contact the Furge team.