Send form data to any URL. Perfect for developers. Connect your native Framer forms to Custom Webhook in 30 seconds with zero client-side API key leaks.
Framer forms can send their data to a webhook: in the form's Send to settings you add a Webhook and paste a URL. That is how you connect a Framer form to anything without a built-in integration, from a serverless function or an internal API to a self-hosted n8n or a Google Apps Script. The Custom Webhook connector lets FramerSend sit in that slot and forward each submission to your endpoint as a plain JSON POST.
Putting FramerSend in between gives the endpoint things it would otherwise have to build: every delivery is logged with the HTTP status your server returned, a failed delivery triggers an alert email and can be retried with one click, uploaded files arrive as links, and an Authorization header or an HMAC signature is added from FramerSend's server so the secret never appears in your site. The body is the form fields under the names your form uses, without extra wrapping.
What gets created: One HTTP POST per submission to your URL, with Content-Type: application/json, the form fields as the JSON body, an Authorization header when you set a Secret Header, and X-FramerSend-Signature plus X-FramerSend-Timestamp headers when you set a Signing Secret.
| Framer form field | Custom Webhook |
|---|---|
| Every form field | Top-level JSON key with the same nameNo normalisation on this connector: no email cleanup, no name splitting, no added keys. |
| Name, Email, Message (forms created in the plugin or setup wizard) | name, email, messageThose forms start with a mapping that lowercases these three fields. Edit it in Field Mapping. |
| File uploads | URL string under the field's keyFiles are stored first (in your connected storage or FramerSend's managed storage) and the link replaces them. |
| Secret Header on the connection | Authorization headerSent exactly as typed, for example Bearer 9f3c…. Leave it empty to send no header. |
| Signing Secret on the connection (optional) | X-FramerSend-Signature, X-FramerSend-TimestampThe signature is sha256= followed by the hex HMAC-SHA256 of the raw request body, keyed with your secret. The timestamp is the send time in Unix seconds. |
| Form ID, IP | Not addedThe body contains form fields only. |
Prepare an endpoint
Any URL that accepts a POST with a JSON body and answers with a 2xx status works: a Vercel or Netlify function, a Cloudflare Worker, an Apps Script web app or your own API route. Answer quickly and do slow work afterwards, because FramerSend waits for your reply before telling Framer the submission went through.
Choose how to verify requests
Simplest: enter Bearer <long random string> in Secret Header and compare the Authorization header in your endpoint. Stronger: enter a Signing Secret, then compute the HMAC-SHA256 of the raw request body with it and compare it with X-FramerSend-Signature using a constant-time comparison. Return 401 when either check fails.
Connect the webhook in the plugin or dashboard
Custom Webhook is a quick pick in the FramerSend plugin inside Framer, and it is also in Dashboard → 2. Connect CRM. Paste the URL and the optional secrets. Test checks that the URL uses https:// and points to a public address; it sends nothing to your endpoint.
Paste the FramerSend 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 real submission
Submit the live form, then look at Dashboard → 4. Logs. A success row means your endpoint answered 2xx; a failed row shows the status it returned.
Webhook: the URL must start with https://
Cause: Shown by Test when the URL is empty, not a URL, or uses http://. Connections saved earlier with http:// keep working, but new ones should use https://.
Fix: Paste the full address including https://.
Webhook: private or internal addresses are not allowed (…).
Cause: The URL, or a redirect it answered with, points to localhost, a private network range or a cloud metadata address. FramerSend only delivers to public addresses.
Fix: Expose the endpoint on a public https:// URL, for example through your hosting provider or a tunnel.
Webhook returned HTTP …: …
Cause: Your endpoint answered with a status outside 2xx; the number and the start of your response body follow. 401 or 403 usually means the secret check failed, 404 a wrong path, 405 a route that does not accept POST, 500 an error in your code.
Fix: Check your endpoint's own logs for that request, fix it, then click Retry on the failed row in Dashboard → 4. Logs.
Request to … timed out after 10s
Cause: Your endpoint did not answer within 10 seconds.
Fix: Return 2xx straight away and do slow work in the background, then click Retry.
The same submission reached my endpoint twice
Cause: A Retry from Logs sends the stored submission again.
Fix: Make the endpoint idempotent, for example by ignoring an email it has already processed within a short window.
Framer's form spinner takes long
Cause: FramerSend waits for your endpoint's reply before answering Framer.
Fix: Return 2xx straight away and move slow work such as emails or API calls to a queue or background job.
Versus a Zapier Catch Hook. A Catch Hook is a webhook URL that starts a Zap, and each run counts as a task. With your own endpoint you control the code and FramerSend has no submission limit.
Versus pasting your endpoint into Framer. You can paste your own URL into Framer directly. Going through FramerSend adds a delivery log with status codes, alert emails, Retry, hosted file uploads and a server-side Authorization header.
Versus Make or n8n. If you need branching, several destinations or no code at all, FramerSend also has Make, n8n and Pabbly connectors. The Custom Webhook is for when you write the receiving code yourself.
One destination per form. Each FramerSend form sends to one connection. To fan out to several URLs, point the webhook at an endpoint or workflow that forwards it.
Full comparison: FramerSend vs Zapier
Zero code or third-party plugins required
Authenticate Custom Webhook credentials in the FramerSend dashboard. We encrypt and store them securely.
Map your Framer form fields to Custom Webhook 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 Custom Webhook 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.
Select the form in Framer, open Form → Send to → Add… → Webhook and paste a URL. With FramerSend, paste your FramerSend form URL there and enter your own endpoint on the Custom Webhook connection.
A flat JSON object of field names and values, for example {"name": "Ada", "email": "ada@example.com", "message": "Hi"}. Uploaded files appear as URLs.
Set a Signing Secret and check X-FramerSend-Signature: it is sha256= plus the hex HMAC-SHA256 of the raw body with your secret. You can also, or instead, set a Secret Header and compare the Authorization header.
The submission is logged as failed with the status, you get an alert email (at most one per form every 15 minutes) and you can retry it from Logs. FramerSend does not queue automatic retries.
No for new connections: Test requires https:// so form data and your secrets are encrypted in transit. Older connections saved with http:// still deliver. Private and internal addresses are never allowed, and redirects are followed at most three times, each to a public address only.
Sign up for a FramerSend account (or log in). Go to Connections → Add Connection → Custom Webhook 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.