Webflow Designer API: Combo Class Parent Relationship Missing

**Hi Webflow Team,

Problem**: The Designer API lacks methods to retrieve parent-child relationships for combo classes, making cross-project element copying unreliable.

What we have:

  • isComboClass() - check if style is combo class

  • createStyle(name, {parent}) - create combo with known parent

What’s missing:

  • getParent() - get parent of existing combo class

  • No way to determine if primary belongs to c-button.primary vs c-card.primary

Impact: When copying elements between projects, combo classes lose their scoping context. A primary combo class might exist in the target project but be scoped to the wrong base class, resulting in incorrect styling or complete style loss.

Current workaround: Using xattr to preserve combo class names, but this fails silently when classes don’t exist or have different scoping in the target project.

Request: Add API methods to inspect combo class hierarchy relationships for reliable cross-project element copying.

Can you give me any more information on this topic? I would be very happy for some insights.

Greetings

Jan Brombach

3 Likes

Yes, absolutely
we definitely need that capability to track the parent of combo classes. I’m actually surprised this wasn’t included in the API from the start, considering how critical it is.

I’ve added this request to the Webflow Wishlist so the team can get more visibility on it. Upvoting it will help highlight just how important this functionality is for developers.

Cheers,
Srinadh.

1 Like

Hey there @schmandarine welcome to the community and thanks for posting. Vic from the DevRel team here.

This is a great point and something we’re thinking about how to make easier for devs. (Great workaround BTW, but you’re right it’s not bulletproof.) I’ll circle back and make sure we share a solution for you as we have updates.

All the best,

Vic