Feature Requests

Share your product ideas with the Flodesk team. Comment on an idea to follow its progress.

Trending
  1. Quizzes for Flodesk forms

    Introduce the ability to collect quiz responses from Flodesk forms.

    Meagan Entoft

    17

  2. Media library of uploads

    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.

    Petra M

    41

  3. Schedule resend to unopens

    Ability to schedule resend to unopens, instead of having to manually complete the action after 24 hours

    Meagan Entoft

    34

  4. See How Any Subscriber Originally Joined List (via What Form or Integration)

    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.

    Annie F

    16

  5. Claude/Flodesk integration

    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.

    Mary J

    1

  6. Support for Meta Pixel Conversion Tracking on Checkout Success Pages

    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.

    Chantal R

    0

  7. Allow multiple products to be sold

    Meagan Entoft

    36

  8. Accept payments with PayPal

    Accept Checkout payments via PayPal

    Meagan Entoft

    20

  9. Send email based on subscriber timezone

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

    josh l

    10

  10. Add birthdays & address fields to forms

    Youโ€™re able to use Flodesk like an address book AND send clients/subscribers special gifts on an automated basis for their birthday!

    Melanie

    17

  11. Flodesk mobile app

    Creating newsletters in app.

    Antoinette F

    16

  12. Ability to add short videos to emails

    Cameron L

    19

  13. Affiliates for Checkout

    I currently use Thrivecart as my checkout for the option to run my own affiliate program, which is a big source of revenue for me. I know a lot of creators use ThriveCart for the same reason. I'd love to switch to FloDesk as the checkout is more visually appealing, and it would integrate seamlessly with my emails, but I can't go without the affiliates feature. I'm hoping this is something FloDesk can add that would bring a ton of value to creators!

    Hannah

    8

  14. Full customization of email and form builders

    Cameron L

    7

  15. Duplicate Emails in a Workflow

    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!

    Ashley M

    6