Add subscribers to Flodesk segments, with names and custom fields. Connect your native Framer forms to Flodesk in 30 seconds with zero client-side API key leaks.
FramerSend creates or updates a Flodesk subscriber for every Framer form submission, with first and last name and any other answers as custom fields, and then adds the subscriber to the segments you choose, which can start your Flodesk workflows.
What gets created: A Flodesk subscriber, created or updated with POST /v1/subscribers, then added to your segments with POST /v1/subscribers/{email}/segments (existing segments are kept).
| Framer form field | Flodesk |
|---|---|
| emailRequired. | |
| first_name / firstName, or name | first_nameA full name is split: the first word is first_name, the rest last_name. |
| last_name / lastName | last_name |
| segment_ids | SegmentsOptional, comma-separated; added to the segments set on the connection. |
| Any other field, e.g. favorite_color | Custom field favorite_colorCreate the custom field in Flodesk first. If Flodesk rejects the custom fields, the subscriber is saved without them. |
Create an API key
In Flodesk, open Integrations → API keys and create a key.
Find your Segment IDs
Open Audience → Segments and click a segment; its ID is the last part of the URL. Separate several IDs with commas.
Connect and test
In FramerSend, open Connections, add this connector, paste the values and click Test. Save it, then attach it to your form. The Test button lists your segments with the key and checks that each Segment ID exists. It creates no subscriber.
Send from Framer
In Framer, select the form, open Form → Send to → Add… → Webhook, paste your FramerSend webhook URL, and publish the site.
Flodesk: Email is required
Add an email input to the Framer form.
Flodesk (HTTP 401): …
Cause: The API key was deleted or mistyped.
Fix: Create a new key in Flodesk → Integrations → API keys.
Flodesk: subscriber saved, but adding to segments failed (HTTP 404)
Cause: A Segment ID does not exist.
Fix: Copy the IDs again from the segments' URLs and click Test.
Flodesk (HTTP 429): …
Cause: More than 100 API requests a minute.
Fix: Retry the submission from Dashboard → Logs.
Zero code or third-party plugins required
Authenticate Flodesk credentials in the FramerSend dashboard. We encrypt and store them securely.
Map your Framer form fields to Flodesk 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 Flodesk 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, no card needed. Unlimited submissions while you test.
Start freeEncrypted API vault, real-time delivery, and unlimited submissions
Capture leads from your Framer site and auto-add them to targeted email campaigns.
Convert visitors into subscribers with a seamless form-to-list flow.
Automatically enroll new customers into welcome sequences.
Yes. Set Double opt-in to Yes on the connection and Flodesk sends its confirmation email to new subscribers.
No. Segments are added with Flodesk's add-to-segments endpoint, which keeps existing memberships.
Add the subscriber to a segment that triggers the workflow in Flodesk.
Sign up for a FramerSend account (or log in). Go to Connections → Add Connection → Flodesk 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.