Marketing sites don’t need a database
A contact form is not an app. Wiring full backend infrastructure for it adds cost and surface area; a form endpoint keeps the project as simple as the prompt that made it.
AI site builders · works with Furrow Forms
Contact forms for Lovable apps
A promptable form backend for prompt-built sites.
paste this into your agent
Fetch furrowforms.com/ai and set up a contact form backend for my Lovable site.agent-readable recipe: /forms-for/lovable.md
prefer clicking? start in the dashboard
Connect the contact form to my form backend:
- submit the form as a POST (FormData) to https://api.furrowforms.com/s/fp_k7m2
- include a hidden text input named "_gotcha", left empty (honeypot)
- include a hidden input named "_ft" set to Date.now() on page load (timing check)
- show the success state when the response JSON has ok: true
- do not add a database or server route for thisThe gap
Why Lovable sites need a form backend
Lovable turns a description into a deployed site — which makes it exactly the audience Furrow Forms was built for: people who ship by prompting, not by wiring infrastructure. When your Lovable site needs a contact or lead form, the heavyweight route is provisioning a database and an email pipeline; the lightweight route is one POST endpoint that already knows how to filter spam, store submissions, notify you, and webhook your tools. Tell Lovable to point the form at Furrow — or let a coding agent provision the backend end to end, account included.
Spam arrives the day you launch
Prompt-built sites go live fast — and bots don’t care who wrote the code. Honeypot, optional Turnstile, domain allowlisting, and rate limits are Furrow defaults.
Keep the workflow conversational
You built the site by describing it. Furrow’s control plane speaks the same language: an agent can create the account, the forms, and the webhook wiring from a single instruction.
Two ways in
Set it up yourself, or don’t
Hand it to your agent
[ recommended ]Furrow’s whole control plane is an API and MCP server. Paste this prompt into Claude Code, Cursor, or any agent — it does the rest:
paste this into your agent
Fetch furrowforms.com/ai and set up a contact form backend for my Lovable site.- 1.Registers the account over POST /api/register — you read one 6-digit email code
- 2.Provisions the site: client, project, and forms in one idempotent bootstrap_site call
- 3.Pastes the generated snippet into your codebase
- 4.Fires test_webhook and verifies the signed delivery
Or do it by hand
- 01Create a free Furrow account and form (or have an agent cold-start it from the prompt above).
- 02Paste the integration prompt into Lovable so the form POSTs to your endpoint.
- 03Add your published domain to the project’s allowlist and set notify emails.
- 04Submissions now land in your inbox and dashboard — and anywhere you point the signed webhook.
free tier: 100 subs/mo · unlimited forms · full API + MCP · pricing →
FAQ
Lovable + Furrow Forms, answered
How do I make the contact form on my Lovable site actually send?
Tell Lovable to POST the form to a Furrow Forms endpoint (one prompt — copy it from this page). Furrow stores the submission, filters spam, and emails you; no database or server route in your Lovable project.
When would I use a database instead?
When submissions are application data your app reads back — user profiles, orders, saved state. For contact, lead, and feedback forms, a form backend is simpler, safer, and comes with delivery guarantees: signed webhooks, retries, and a log.
Can I move the data into my CRM or other tools?
Point the project webhook at your integration endpoint: payloads are HMAC-signed with timestamps, retried with backoff up to 8 attempts, and logged. Email notifications with template tokens run in parallel on every tier.
The form backend your agent can run.
paste this into your agent
Fetch furrowforms.com/ai and set up forms for this site.