Write form submissions to your Firebase Realtime Database. Connect your native Framer forms to Firebase in 30 seconds with zero client-side API key leaks.
If your product already runs on Firebase, the natural home for Framer form data is the same project. FramerSend writes each submission into your Realtime Database through its REST API: one new node under /submissions with a key generated by Firebase, holding the form fields exactly as they are named in Framer plus an ISO 8601 timestamp. There is no Cloud Function to deploy, no endpoint to host and no Firebase SDK in your Framer site.
Two things are worth knowing before you start. This connector works with the Realtime Database only, not Cloud Firestore. And it sends no credentials, only the database URL, so your security rules must allow writes to the /submissions path. Keep those rules as narrow as you can: writes allowed under /submissions only, reads closed.
What gets created: A new child under /submissions in your Realtime Database, written with POST {database URL}/submissions.json. Firebase generates the child's key (a push ID), so two submissions arriving at the same moment never overwrite each other. The value holds every form field plus a timestamp.
| Framer form field | Firebase |
|---|---|
| Every form field | Key with the same nameKept exactly as received, with no renaming, email cleanup or name splitting. |
| Name, Email, Message (forms created in the plugin or setup wizard) | name, email, messageThose forms start with a mapping that lowercases these three fields. Change it in Field Mapping if your app expects other keys. |
| (added by FramerSend) | timestampSubmission time as an ISO 8601 string in UTC, for example 2026-10-31T09:15:00.000Z. |
| (node key) | Firebase push IDGenerated by Firebase for every write, unique and roughly ordered by time. |
| File uploads | Link stringThe file is stored first and its URL replaces it in the record. |
| Field names with special characters | May be rejected by FirebaseRealtime Database keys cannot contain some punctuation. If a write is refused for that reason, rename the field in Field Mapping. |
Create a Realtime Database
In the Firebase console, add a Realtime Database to your project if it has none. Copy its URL, which looks like https://your-project-default-rtdb.firebaseio.com or, for other regions, ends in firebasedatabase.app.
Allow writes to /submissions only
FramerSend authenticates with nothing but the URL, so your Realtime Database rules must let unauthenticated requests create new children under /submissions. Keep reads closed and limit the write rule to that path (ideally to new children only), then test the rules in the Firebase console's rules playground. Read the data from your backend with the Admin SDK.
Connect Firebase in the plugin or dashboard
Search for Firebase in the FramerSend plugin inside Framer, or use Dashboard → 2. Connect CRM, and paste the Database URL. Test makes a read-only request to confirm a Realtime Database answers at that URL. It cannot confirm that writes are allowed without writing, so it reminds you to check the rules.
Paste the webhook URL into Framer
In Framer, select the form, open Form → Send to → Add… → Webhook, paste the FramerSend webhook URL (https://www.framersend.com/api/submit/ followed by your form ID) and publish the site.
Send a test submission
Submit the live form once, then open the Data tab of your Realtime Database. A new node appears under submissions. If it does not, the reason is on the row in Dashboard → 4. Logs.
Firebase: permission denied. Your Realtime Database rules must allow writes to /submissions (FramerSend writes without signing in).
Cause: The rules refused the write.
Fix: Update the rules as in step 2, then click Retry on the failed row in Dashboard → 4. Logs.
Firebase: database not found. Check the Database URL (Realtime Database → Data → the URL at the top).
Cause: The URL is not a Realtime Database, for example a Firestore or console address.
Fix: Copy the URL from the Realtime Database page and click Retry.
Firebase (HTTP …): …
Cause: The database refused the write for another reason, for example a field name with a character that keys cannot contain.
Fix: Rename the field in Field Mapping, then click Retry.
Test passes but nothing arrives
Cause: Test only reads, so it cannot see whether the rules allow writes.
Fix: Send one real submission and look at Dashboard → 4. Logs for the result.
Submissions are stored but my app cannot read them
Cause: The recommended rules block reads on purpose.
Fix: Read submissions from a trusted server with the Admin SDK, or add a read rule limited to signed-in admins.
No function to maintain. The usual alternative is a Cloud Function that receives the form and writes to the database. FramerSend does the write for you; a function is still the better choice if you need custom validation or authenticated writes.
Firestore needs another route. This connector writes to the Realtime Database only. If your data lives in Cloud Firestore, use an automation platform, a Cloud Function, or FramerSend's Custom Webhook pointed at your own endpoint.
Logs and retry included. Every write is logged with Firebase's reply, you get an alert email when one fails, and failed rows can be retried after a rules fix.
No per-run pricing. Zapier and Make count each run against your plan. FramerSend has no submission limit.
Full comparison: FramerSend vs Zapier
Zero code or third-party plugins required
Authenticate Firebase credentials in the FramerSend dashboard. We encrypt and store them securely.
Map your Framer form fields to Firebase properties using our visual dropdown UI.
Paste your webhook URL into your Framer form under Send to → Webhook and publish. Submissions flow automatically.
Every plan includes Firebase and 100+ other connectors. Pay monthly, yearly, or once. Try it free for 14 days, no card needed.
For one Framer site
For freelancers and small studios
For agencies with many client sites
14-day free trial of every connector, no card needed. Form fields and FramerSend file uploads stay free forever with a free account.
Start freeEncrypted API vault, real-time delivery, and unlimited submissions
Automatically capture and route leads from your Framer forms.
Trigger automated workflows when form submissions arrive.
Keep all your form data in one place, synced in real-time.
No. It writes to the Realtime Database through its REST API. For Firestore, point FramerSend's Custom Webhook at a Cloud Function or your own endpoint.
FramerSend sends no token or secret with the write, only the database URL, so the rules decide alone. Limit the rule to new nodes under /submissions and keep reads closed.
A node under submissions with a Firebase push ID as its key, containing {"name": "Ada", "email": "ada@example.com", "message": "Hi", "timestamp": "2026-10-31T09:15:00.000Z"}, with keys named after your form fields.
No. The path is fixed. Use separate Firebase projects or databases if different forms must stay apart.
FramerSend writes it again as a new node with a new push ID.
Yes. Search for Firebase in the FramerSend plugin, paste the Database URL and save. The plugin creates the form and shows the webhook URL to paste into the form's Send to settings.
No. It only reads, to confirm a Realtime Database answers at the URL. It cannot prove that your rules allow writes, so send one real submission after setup.
Sign up for a FramerSend account (or log in). Go to Connections → Add Connection → Firebase and add your credentials. They are stored server-side and never exposed in your Framer site, which only gets a public form URL.
Yes, all API credentials are encrypted at rest. The client-side code in Framer only exposes a public Form ID, keeping your private keys entirely secure.
No. FramerSend provides unlimited form submissions across all license tiers so your live website forms never get blocked during high-traffic spikes.