# Allow workflows to create new segments/lists

**URL:** <https://community.hubspot.com/t/allow-workflows-to-create-new-segments-lists/146737>\
**Category:** HubSpot Ideas\
**Tags:** segments, workflows\
**Created:** [February 26, 2026, 9:14pm UTC](https://community.hubspot.com/t/allow-workflows-to-create-new-segments-lists/146737 "2026-02-26T21:14:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![katjmars](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/katjmars/32/203478_2.png) [@katjmars](https://community.hubspot.com/u/katjmars)\
**Post date:** [February 26, 2026, 9:14pm UTC](https://community.hubspot.com/t/allow-workflows-to-create-new-segments-lists/146737/1 "2026-02-26T21:14:52Z")

</div>

We use Marketing Events synced from Zoom, and are building out an “event afterglow” process to include follow-up emails to participants. Currently, we have to create or clone a segment/list for every single marketing event/webinar that we have in order to pull participating contacts. We’d like workflows to be able to automatically create segments/lists when a new Marketing Event is created, e.g., an active segment named _Webinar – {{Event name}} – Registered_. We don’t necessarily need the workflow to set filters, although it would be best case scenario to have it dynamically filter the associated event; at the very least, we just need it to create the empty segment/list, so we can then configure filters manually.

---

<div class="post-metadata">

**Author:** ![jweberswtb](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jweberswtb/32/227138_2.png) [@jweberswtb](https://community.hubspot.com/u/jweberswtb)\
**Post date:** [August 19, 2026, 12:25pm UTC](https://community.hubspot.com/t/allow-workflows-to-create-new-segments-lists/146737/2 "2026-08-19T12:25:45Z")

</div>

Fabulous idea! We would also use this as we participate in many events and the limitations on dynamic creation of other objects (like Segments as you say) in work flows based on a marketing event ID, results in proliferation of “one time use” workflows. In our case it’s adding a contact to a marketing event as attending during a workflow that is processing lead capture forms or imports. One step because you can’t currently do this forces the unique workflow.