Trigger Make scenarios from form submissions. Connect your native Framer forms to Make (Integromat) in 30 seconds with zero client-side API key leaks.
Make is the right tool when one form submission should start a chain: enrich the lead, route it with a filter, write it to two apps and post a summary to Slack. The FramerSend Make connector forwards each Framer submission as JSON to the URL of a Make Custom webhook, so your scenario starts with the same field names your form uses.
If all you need is one destination, a scenario is extra work and every run uses part of your Make plan. In that case connect the tool directly instead: FramerSend has native connectors for Klaviyo, HubSpot, Notion, Salesforce, Google Sheets and many more. You could also paste a Make webhook straight into Framer; going through FramerSend adds a log of every submission, a retry button, failure alerts and hosting for uploaded files.
What gets created: One HTTP POST to your Make webhook URL per submission, with Content-Type application/json and the form fields as the body.
| Framer form field | Make (Integromat) |
|---|---|
| Every form field | Top-level JSON key with the same nameField names are not normalised for Make, so Email stays Email. Rename fields in Field Mapping if your scenario expects other keys. |
| File upload fields | URL stringThe file is stored first and the field holds its link, so a Make HTTP module can download it. |
| Multi-choice answers | Same value Framer sent |
| Metadata (time, IP, page) | Not addedOnly the form fields are sent. Make's webhook bundle has its own receive time. |
Create the webhook in Make
Create a scenario, add Webhooks → Custom webhook as the trigger, click Add, name it and copy the address (https://hook.us1.make.com/… or your region's host).
Connect Make in FramerSend
In the FramerSend plugin inside Framer or Dashboard → 2. Connect CRM, choose Make (Integromat), paste the webhook URL and click Test. Test only checks that the URL is a valid https address; it does not send data to Make.
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.
Let Make learn the data structure
With the Make webhook module waiting to determine the data structure, submit your live Framer form once. Make then knows the field names and offers them in later modules.
Build and switch on the scenario
Add your modules, then turn the scenario on and set it to run immediately as data arrives.
Invalid Webhook URL. Must start with https://
Cause: Shown by Test when the field is empty or not a URL.
Fix: Copy the full address from the Make webhook module, including https://.
Make: …
Cause: Make answered with a non-2xx status. Make's own message follows the colon. Common reasons are a webhook that was deleted or replaced, or a scenario that is not switched on.
Fix: Open the scenario in Make, check the webhook module still shows the same address and turn the scenario on. Update the URL on the FramerSend connection if it changed, then retry the failed rows in Dashboard → 4. Logs.
FramerSend shows success, but the scenario did not finish
Cause: FramerSend marks a delivery successful as soon as Make's webhook answers with a 2xx status. What later modules do is not reported back.
Fix: Check the scenario's run history in Make for the module that failed.
Fields missing in Make's mapping panel
Cause: Make learned the data structure from an older version of the form.
Fix: Re-run the data structure step on the webhook module and submit the form again.
Use Make for multi-step logic. Routers, filters, iterators, lookups and writing to several apps from one submission are what Make is built for. FramerSend sends a form to one connection, so the Make connector is how you reach that power.
Use a direct connector for one destination. Framer → Make → Klaviyo is three systems to keep in sync. A direct FramerSend connector is one URL and one log, with no scenario to keep switched on.
Operations are counted by Make. Every module that runs uses part of your Make plan's monthly allowance. FramerSend itself does not meter submissions.
Keys sit in different places. With the Make connector your app credentials live in Make's connections. With direct connectors they are stored in FramerSend. Neither puts a key in your Framer site.
Full comparison: FramerSend vs Make.com
Zero code or third-party plugins required
Authenticate Make (Integromat) credentials in the FramerSend dashboard. We encrypt and store them securely.
Map your Framer form fields to Make (Integromat) 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 Make (Integromat) 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.
When one submission must do several things: branch on answers, write to more than one app, look up data or wait for an approval. For a single destination such as a newsletter list or CRM, a direct connector is simpler and does not use Make operations.
Yes, that works. Routing through FramerSend adds a log of every submission with its payload, one-click retry after an error, a failure alert email and hosted links for file uploads.
A flat object of your form's fields, e.g. {"name":"Ada","email":"ada@example.com","message":"Hi"}, using your Framer field names or the names you set in Field Mapping.
A failed delivery is logged with Make's response and you are emailed (at most once per form every 15 minutes). You retry it from Dashboard → 4. Logs.
Yes. The Zapier connector works the same way with a Catch Hook URL.
Sign up for a FramerSend account (or log in). Go to Connections → Add Connection → Make (Integromat) 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.