Get instant Slack messages when forms are submitted. Connect your native Framer forms to Slack Notifications in 30 seconds with zero client-side API key leaks.
Speed matters with inbound leads, and most teams already sit in Slack. FramerSend posts a message to the channel of your choice for every Framer form submission, so sales, support or the founder sees a demo request seconds after it is sent. The message has a heading with the form's name and then one line per field, with the field name in bold and the answer next to it.
It uses a Slack incoming webhook, which can only post to the channel it was created for: no bot token, no access to your workspace's messages. Slack is a notification here, not a store of record. Each FramerSend form sends to one connection, so if the same submission must also reach a CRM, use the Make or Zapier connector to fan it out, or keep Slack for forms that only need an alert.
What gets created: One Slack message per submission, posted to your incoming webhook URL: a mailbox emoji with the bold heading New submission: followed by the form name, then one "*field:* value" line per form field.
| Framer form field | Slack |
|---|---|
| Every form field | One line: bold field name, then the valueIn the order the fields arrive, each field once. Field Mapping renames the labels but does not hide fields. |
| Field names such as your_email or q3 | Shown as they areRename them in Field Mapping, for example to Email or Budget, so the message reads well. |
| Multi-choice answers | Values separated by commasStructured values are shown as JSON. |
| File uploads | A link to the stored file |
| Channel on the connection (optional) | channel value in the requestSent when filled in, but Slack decides whether to use it; an incoming webhook normally posts to the channel it was created for. Use one webhook per channel. |
| Form name | In the headingSlack shows the post time. |
Create an incoming webhook
In Slack, create an app for your workspace (or open an existing one), turn on incoming webhooks, add a webhook and choose the channel. Copy the URL, which starts with https://hooks.slack.com/services/.
Connect Slack in the plugin or dashboard
Search for Slack in the FramerSend plugin inside Framer, or use Dashboard → 2. Connect CRM. Paste the webhook URL and leave Channel empty. Test checks that the URL uses https:// and points to a public address; it does not post anything.
Give fields readable names
After the first submission, open Dashboard → 3. Field Mapping, click Auto-load fields and rename inputs to the labels you want in Slack.
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 message
Submit the live form once and check the channel. If nothing appears, the reason is on the row in Dashboard → 4. Logs.
Webhook URL: the URL must start with https://
Cause: Shown by Test when the field is empty, not a URL, or not https.
Fix: Paste the full hooks.slack.com address.
Slack (HTTP …): …
Cause: Slack refused the post and its short reason follows. The usual causes are a webhook that was removed or whose app was uninstalled, or an archived channel.
Fix: Create a new incoming webhook, update the connection and click Retry on the failed row.
Parts of a message look bold or struck through
Cause: Slack applies its own formatting to characters such as *, _ and ~ in answers. Angle brackets and & are escaped, so visitors cannot add links or mentions such as @channel.
Fix: Nothing is lost; the original text is on the submission in Dashboard → 4. Logs.
Fixed format, zero setup. FramerSend posts a fixed layout with the form name and every field, which needs no design work. If you need a custom message layout, build it in an automation platform instead.
No task per alert. Each Zap run counts as a task. FramerSend has no submission limit, so a busy form does not cost more.
Minimal access. An incoming webhook can only post to its channel. FramerSend never sees your workspace's messages or members.
Email instead of Slack. If you would rather get submissions by email, FramerSend's email notification connector sends each one to your inbox.
Full comparison: FramerSend vs Zapier
Zero code or third-party plugins required
Authenticate Slack Notifications credentials in the FramerSend dashboard. We encrypt and store them securely.
Map your Framer form fields to Slack Notifications 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 Slack Notifications 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. Every field is included. You can rename fields in Field Mapping so the labels read well.
Not directly. A connection holds one webhook, and each form sends to one connection. Use a channel everyone follows, or route through Make or Zapier.
Not from one FramerSend form alone, since a form sends to one connection. Use the Make or Zapier connector to do both, or rely on your CRM's own Slack notifications.
No. It only calls the incoming webhook URL you paste.
Only as the posted message. The full submission, with every field, is also kept in FramerSend's Logs.
Test only checks that the URL is a public https:// address; it never posts to Slack. Submit the live form once and read the result in Dashboard → 4. Logs, where Slack's reason is shown if the post failed.
No. FramerSend adds no mentions, and it escapes visitor text so an answer cannot trigger @channel, @here, user mentions or links. Use the channel's notification settings in Slack so the right people are alerted.
Sign up for a FramerSend account (or log in). Go to Connections → Add Connection → Slack Notifications 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.