Feature Requests

Tell us how we could make Heartbeat better for you.

Video Library Folders & Renaming

As course creators managing multiple courses and large video libraries, having all uploaded videos in a single list on the video library makes it difficult to organise and locate content efficiently. I know you can search, but when you can’t remember what you labelled something as, it’s tricky lol! It would be extremely helpful to be able to organise videos into folders or categories within the video library, allowing for easier navigation, faster content management, and better scalability for growing course libraries. Also, once uploaded, you can’t rename files! So files that I’ve misspelt or mislabelled, granted that’s my fault, but it’d be fab to be able to rename video files too! :)

Laura Morris 22 days ago

Need subscription payment failure/cancelled endpoints for API (MCP)

I'm building an automated financial and member-management dashboard using the Heartbeat API (v0) alongside Stripe and Kit. I'd love to see additional API endpoints that would help community builders like me manage churn and member lifecycle without needing to check the admin UI manually. Specifically: Cancellation feedback / exit survey data — The "View Feedback" section under Offers in the admin panel collects valuable cancellation reasons, but there's no API endpoint to retrieve this data. Being able to pull feedback programmatically would let me track churn reasons over time and respond faster. Subscription status per user — The current /v0/users endpoint doesn't include subscription status (active, cancelled, past due, etc.) or cancellation dates. Adding subscription fields to the user object would make it possible to build member dashboards without cross-referencing Stripe separately. Offer purchases / subscriber list per offer — An endpoint to list which users have purchased a specific offer (and their current payment status) would be extremely useful for membership management and reporting.

Sue Brown-Moore about 15 hours ago

Option to make event location visible for ticketed events.

Right now, the location is protected apparently for community privacy, so external guests won’t see the location until they RSVP. Before signing up, they see under location: “RSVP to see”. If I want the location visible before anyone signs up, the only way to do this is to make the event not ticketed. Which defeats the purpose of paid public events. There should be an option to choose whether or not you want the location visible, not a default to hidden. I get that you're going for privacy, but I'd like to request that you offer an option or on/off toggle to let folks outside of the community see the location before signing up as this may inform a potential participant's decision in signing up (if they can see the location is close by, they would be more likely to sign up – or if they sign up and see the event is very far away and not possible for them, I have to do extra admin work and offer a refund). Currently, I share the location in the event description, but I would prefer also to be able to show the event location in the ‘Location’ panel.

Alex Williams about 18 hours ago

Closed

Copy workflows when creating new cohorts

Cohort-based courses generate new lesson IDs per cohort, which means all lesson-attached workflows (popups, automations, etc.) are lost and must be manually recreated each time. This is especially painful when workflows contain rich content like GIF/video embeds that can't be easily duplicated. Expected behavior: When a new cohort is created, workflows attached to lessons in the previous cohort should automatically carry over to the corresponding lessons in the new cohort. Customer impact: Creators running recurring cohort programs have to manually rebuild every workflow for every new cohort — error-prone and time-consuming. Missed workflows mean students don't receive key moments (e.g., graduation gift popups).

Serena Hawtin about 1 month ago

2

Request to Reconsider DM Rules for Starter Plan

Please consider making DM rules available on the Starter plan. As I've been building my educational community on Heartbeat, I've found that DM management is truly a foundational feature for creating a structured, professional learning environment - not just something needed at scale. Currently, this feature being limited to higher plans feels like it treats DM control as a "nice-to-have" scaling feature, when it's actually fundamental to how many communities need to operate from the start. Small educational communities, coaching programs, and professional development groups all need this level of structure regardless of their member count. Would the team consider moving DM rules to the Starter plan? This would make Heartbeat much more accessible for educators and community builders who need professional-grade moderation tools but are just starting out. Thank you for considering this feedback.

Ms. Dora May about 1 month ago