Feature Requests

Sometimes I am using an icon or I have the same photo I want to use in more than one spot or in a future piece, it would be nice to have a library of all the images or docs we have uploaded to choose from instead of having to always upload from our computer.

Ability to edit the content of an email before resending to unopens

I would love to easily add an invitation to just click a button to forward the email to a friend they think would like the email or our organization :) I know they can forward it anyway, but a button with a specific invitation always makes people more apt to do so.

Not sure if this exists, but if it does can't find it. It would be useful data to understand the 1st action any subscriber took to join the list originally so I can know what attracted them in the first place if they become clients later.

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

It would be great to have the ability to add more than 2 columns, and to customise them with buttons, links, etc. It helps breaking the text up especially when it's large text dumps.

Please allow us to program or select STANDARD FONT so we dont have to RESET it OVER nad OVEr and OVER again from Helvetica we are BRANDING our content with SPECIFIC fonts SO PLEASE let us set ONE FONT choice and save us SO MUCH time and energy from having to reset the font over and over and over again thank u

Introduce 2FA/MFA as security measure for Flodesk accounts

Instead of course integrations such as Teachable etc.. Create a platform for your own in house course hosting. Then you have emails, automations, carts, and courses all speaking with each other. Getting closer and closer to a one stop shop, hopefully!

I would love to see more countries added to the checkout feature, Switzerland is jot yet on the list

I’d love to see a feature in Flodesk that allows for global blocks or synced content blocks—so that when you update a block (like your email signature or a list of key links), it automatically updates across all emails and workflows where that block is used. This would be especially helpful for managing consistent elements across multiple automations or campaigns without needing to manually update each one.

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.