Feature Requests

When we export email analytics data, would love to see a column with the subject line of that email too. Super helpful for comparing open rates and identifying subject lines that get the most opens rather than having to manually match them up

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.

The templates in the Abandoned Cart Workflow are not truly customizable. You cannot remove or add any blocks, nor can you choose to use your own created email as in other workflows. If an email cannot be designed to fit your product's or customer's needs, this makes the entire workflow useless.

Introduce the ability to collect quiz responses from Flodesk forms.

Ability to have multiple brands/logos within a single Flodesk account

Improve organization of segments

Me and my team love Flodesk! One thing we believe needs improvement is the workflow capabilities. I find that if I could duplicate my email within a workflow and drag it around that would be much easier than completely starting from scratch. I also don't want to make an email outside of that workflow to then copy, it just needs to be able to be duplicated within the workflow. Thanks!

I understand Flodesk doesn't allow Embed Codes to preserve the integrity of it's visual appeal and functionality to the email receiver -- though it would be nice if we could assume this risk on our own. Allowing codes like HTML, DIV, or Script would be very beneficial. Even if this feature had to be turned on in settings to prevent the novice user from breaking their email designs, it would allow more advanced users to still utilize and empower their emails to help accomplish their end goals.

Similar to how we can now save email blocks as favorites, I’d love to be able to do the same with Checkout blocks! Sometimes I play around with a few different templates before I find one I like. After I’ve customized it, it would be nice to save the blocks I like so I can just bring them into another template.

It would be great if Flodesk automatically generated UTM links for the purpose of tracking traffic from our Flodesk emails in Google Analytics.

I would like to be able to easily add an "add to calendar" button for google calendar events in order for my subscribers to easily add reminders for themselves for upcoming events.

In most other email programs, people are asked WHY they are leaving. This data allows the writer to better tailor the content of emails when we can understand why someone is leaving.

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.