New to skills? Start with the AI Skills Library for how to add one.
Builds a segment in Userflow from a plain-language description of who should be in it, showing you the conditions before anything is created.
What it does
You say whether you're building a user segment or a company segment, describe the audience in your own words, and the skill turns that into real conditions. It looks up your account's actual attributes and events rather than guessing at names, shows you the result in plain English, and asks you to confirm before creating anything.
Once created, the segment is live in your segment list and keeps itself up to date—membership is worked out from the conditions, so people move in and out as their data changes. There's no list to maintain.
What you'll need
The Userflow MCP connected
How to use it
"Create a segment of users who haven't finished onboarding."
"Build me an audience of companies on an active subscription in the EU."
"Make a segment of users last seen more than 30 days ago."
If your description could mean more than one thing—"active" might mean subscribed or recently seen—you'll get one short question rather than a guess.
User segments and company segments
The choice matters, because it decides which attributes are available. A company segment can only use company attributes. A user segment can use user attributes, company attributes, and company membership attributes, so it's the more flexible of the two.
Things worth knowing
This builds condition-based segments only. If you want a fixed list of specific people uploaded from a file, that's a manual segment, and it has to be imported from the Userflow dashboard. The skill will tell you rather than trying to fake it with a long list of conditions.
Segments can't be built from other segments. "Everyone in segment X plus these others" isn't something the conditions support. The underlying rules have to be written out instead.
Check the conditions before you confirm. This is the step worth slowing down for. A condition with a subtly wrong value matches the wrong people, or nobody at all, and it isn't obvious afterwards—the segment just quietly comes back smaller than you expected.
Editing a segment takes effect immediately. Unlike a flow, a segment isn't versioned, so changes apply to anything already using it. See Creating and publishing with MCP write tools.