Feature Requests

I often schedule multiple emails at the same time, with each email going to a different country-language combination (e.g. email 1 English - Canada & US, email 2 English - South Africa, email 3 German - Germany, Austria & Switzerland). It's hard to double check that I selected the right segments for each email, because it involves: unscheduling each emailgoing through the different screens for each email (edit email, edit sender, edit subject line etc.)finally getting to the screen with recipients and included/excluded segmentsrescheduling the email and ensuring the correct time is selected again It would be amazing if there was an option "View recipients" on a scheduled email (in the menu in the top right hand corner of the email tile). When clicking on "view recipients" you see the total number of recipients that will receive the email, the included segments and the excluded segments (more or less the same view that you get when scheduling the email). I'm very worried I accidentally send the same email to the same person multiple times because our segmentation is country/region and language specific and therefore slightly complex.

Introduce the ability to collect quiz responses from Flodesk forms.

I don't need to explain why this is useful, can this be implemented this week

Hello Flodesk Team, A growing number of Flodesk users rely on AI tools like ChatGPT and Claude to draft newsletters, subject lines, and automated email content. Right now, we have to copy and paste between platforms, which interrupts workflow and slows campaign creation. A direct integration would enable: Generating subject lines, email copy, or A/B test variants directly inside Flodesk Quickly personalising automations with AI-powered suggestions Streamlined editing and publishing without switching platforms This would make Flodesk a true one-stop shop for content creation and delivery, and it would put you ahead of other email platforms that are only just starting to explore AI features. Thanks for considering—this integration would save users huge amounts of time while keeping their campaigns sharp and consistent. Thank you.

Good Morning, The Flodesk/Claude integration is the missing piece in my monthly sales funnel analysis for my TPT store. Claude was able to integrate an email analysis with my Pinterest/Blog/Sales data to render comprehensive funnel analysis. While the information from the current Flodesk/Claude integration was quite robust, Claude has recommended some additional features which I have copied and pasted below. Thanks very much. Mary Jenkins Hi Flodesk team, I'm using the Flodesk–Claude integration (the MCP connector) for monthly analysis of my email funnel, and your support team suggested I submit a ticket with feature requests for upcoming phases. I rely on the connector heavily, and the additions below would make it considerably more useful. In rough priority order: Email content and template/layout data. The connector currently returns metrics and subject lines, but not the email body, the template used, or the layout. Exposing this — even just a template identifier per campaign — would let me analyze which templates and layouts actually drive clicks. Right now that analysis is impossible because the design never reaches the connector.Link-level / click-destination data per email. The campaign tools return total clicks, but not which links were clicked or their destination URLs. Per-link click data (or a UTM/destination breakdown) would let me attribute clicks to specific products and pages, which is the core of funnel measurement.Subscriber- and segment-level member access. The connector returns aggregate segment sizes and engagement rates, but not the members of a segment (names/emails). Being able to pull a segment's members would let me match subscribers against my own sales records and measure conversion by segment.A/B test results. Access to split-test setup and outcomes (open and click by variant) so I can read test results directly rather than reconstructing them by hand.Longer or configurable date ranges. The send-time insights are capped at 90 days, which is short for senders who mail only a few times a month. A longer or custom lookback window — ideally for the subscriber and email trend tools as well — would help a lot. A note on setup and data discovery Beyond the data gaps above, getting to these insights took more trial and error than it should have, and a few changes would smooth the path for the next user: • The campaign search filter didn't return results. When I searched campaigns by a keyword I knew existed, the search came back empty, so I had to page through the entire campaign list twenty at a time to find specific emails. A working keyword search — plus the ability to look up a campaign directly by name or ID, and to filter by tag or date — would replace a lot of manual paging. • Pagination and date-range limits forced many repeated calls. Results cap at twenty per page, and the send-time insights only look back ninety days. For anyone with more than a handful of campaigns, or a low send frequency, that means stitching together many calls or simply not seeing the full history. Higher page limits (or an option to return all results) and longer, configurable date windows would help. • The data model was hard to discover. The tool descriptions are brief, so I often had to call a tool just to learn what fields it returns. A short schema or field reference for each tool would let the analysis go straight to the data instead of exploring first. • The connection and approval flow was confusing at first. Each tool had to be approved individually, and my first attempts returned a "no approval received" error with no obvious prompt, which looked like a failure rather than a pending permission. Clearer setup documentation about what to expect — and, if possible, a single authorization for the full tool set at connect time rather than tool-by-tool — would prevent that early friction. Individually these are small, but together they turned a one-hour analysis into a much longer one. Smoothing them would make the integration feel finished.

Reiterating from the partner call our request for more excuses to yap about flodesk. Specifically the purple sweatshirt that Megan wore and a big water cup and also a mug… “sexy people write emails” or similar, please ask social team for their threads and screenshots for ideas. 🫶🏼

As a Flodesk user running Meta Ads, I need the ability to track 'Purchases' and 'Complete Registrations' directly within my Meta Ads Manager. Currently, there is no way to fire a Meta Pixel event when a customer completes a transaction on a Flodesk Checkout page. Custom Conversion on the thank-you page is not working either (using a key word search like "thank-you" within the url). I am requesting one of the following features be added to Flodesk Checkouts: Custom Header/Footer Code for Success Pages: The ability to paste a Meta Pixel 'Purchase' event script that only fires after a successful transaction. Native Meta Pixel Integration: A simple field to enter a Meta Pixel ID that automatically tracks standard e-commerce events (ViewContent, AddToCart, Purchase). Custom Redirect URL: The option to automatically redirect customers to a specific URL (on my own domain) immediately after a successful checkout so I can track conversions there. Without this, I cannot accurately measure my return on ad spend (ROAS) or optimise my ads for actual sales.

This reeeealllly needs to happen. When working within a team, it's really hard to see which segments have had emails delivered to them - these should appear at a glance when you view the sent email details. The only workaround is to duplicate the email and then go to send it to see which segments were in there - proper tedious.

I'm hosting my store on Salla (which is an e-commerce platform in KSA), and I'd like to be able to integrate a post-purchase for my products. (as the platform has an abandoned cart workflow).

It would save a lot of time if we could set up an automatic resend of the opt-in email to unconfirmed subscribers, and also auto-delete them after a certain amount of time has elapsed. For example, I would set up the opt-in to resend if 14 days has passed since the initial sign-up, and then if 30 days passes after re-sending opt-in, that unconfirmed subscriber would automatically be deleted. Currently, doing all this manually is a lot of trouble to keep track of (like, which subs have I resent the opt-in to already? and how much time am I giving them before deleting?). Due to this, I usually just don't resend at all, and delete all the oldest unconfirmed subs (the ones who've been sitting there 3 months or more).

I’m reaching out with a feature idea that came to me during the call. As a web designer, I use Flodesk with clients constantly. I’m often signing into their accounts to set up lead magnet pop-ups or embed newsletter sign-up forms on their sites, and I almost always run into 2FA. It’s manageable, but it slows things down every time I need to jump in and help them. My idea: a developer or collaborator account for partners like me. I could request access to a client’s account without being added as a member of their team, similar to how Shopify handles access for its development partners. Since I’m usually only in an account for a short (but crucial!) window, this would make the whole process smoother for me and for my clients.

I’m not sure there is a huge benefit in translating forms if the emails I then send aren’t in the language my subscriber speaks. As Spanish is so widely spoken I think this would be a good first translation option to allow the English and Spanish speaking communities to reach each other. I have had Spanish speakers ask for a translated version of my flodesk emails. Either an automatic translation, a plug-in perhaps, or a drop down menu the reader can choose would be ideal!