Publish frozen project, element, node-group, or package bundles; manage metadata and snapshots; and, after creator approval, configure a product page, free or one-time offer, gated delivery, and versions in Creator Studio.
Where: Project menu or selection menu → Publish to Marketplace; Account → Creator Studio
Before you start
- Use an account eligible to publish; paid products require the applicable creator/payment setup.
Key ideas
- Frozen listing bundle: Marketplace publishing snapshots the current project or selection. Later source edits are private until the creator explicitly refreshes or replaces the listing bundle.
- Community publishing: Creator attribution exists for every listing; any member can use a community profile, while approved sellers receive a seller identity and Creator Studio.
- Merchandising and sale: Approved creators can add landing-page media/body, choose free or one-time pricing, gate the bundle behind entitlement, and respect the configured minimum price.
- Versioned updates: Bumping a listing version makes Update available to entitled users; a changelog explains the new snapshot.
- Agent-assisted node-group listing preparation: The Flowgen Agent can prepare a selected graph, connected flow, or existing Group and open the native Publish dialog with a title, description, supported category, tags, and a thumbnail chosen from a completed image output. Preparation is not publication; the human reviews the snapshot and presses Publish.
Steps
- From a project or supported selection, choose Publish to Marketplace and confirm the intended kind: project, element, Flowgen node group, or package.
- Add a clear title, description, kind-specific category, lowercase tags, thumbnail, and optional live demo URL.
- Publish the snapshot. Full projects can be shared through the public listing; elements, node groups, and packages remain discoverable only inside compatible projects.
- For a project listing, use Update listing and enable Refresh snapshot when source changes should reach buyers. For a node group, choose the current selection, connected flow, or group to replace its blueprint.
- From Flowgen, the Agent can prepare a node-group listing after you specify the intended graph, purpose, category, tags, and a completed image output for the thumbnail. If any of that is unclear, it should ask before opening the dialog.
- Review the exact snapshot and metadata in the native Publish dialog, replace or upload the thumbnail if needed, and press Publish yourself. A prepared dialog is not a live listing.
- If approved as a creator, open Account → Creator Studio and add the landing page, choose Free or One-time, set price/currency, and enable gated delivery for entitlement-protected files.
- When shipping a meaningful update, bump the version, write the changelog, and save so current installers see Update available.
- Use My listings/Creator Studio to edit metadata, refresh the bundle, or remove a listing; verify its public or in-project discovery surface afterward.
Where listing kinds appear
- Project: public Marketplace and share link.
- Element: in-project f0 Marketplace/Insert.
- Node group: in-project Flowgen Marketplace.
- Package: in-project installation surface for organization resources.
Flowgen Agent preparation boundary
- Tool: prepare_marketplace_node_group. It accepts selection, connected_flow, or group; a group target needs the exact existing group_id.
- Required listing details include title, accurate description, supported node-group category, relevant tags, and thumbnail_node_id from a completed image output.
- The thumbnail must depict the actual reusable flow. If the output cannot be fetched, choose or upload a replacement in the dialog.
- The tool snapshots the intended graph and opens the native dialog; only a human press on Publish completes public listing. Do not claim publication from preparation success.
Update semantics
- Updating metadata alone does not silently resnapshot the source.
- A project refresh rebuilds the frozen project bundle.
- A node-group refresh swaps the blueprint while keeping the listing id, link, and use count.
- Version defaults to 1 for legacy listings; version bump and changelog are explicit Creator Studio actions.
Seller boundary
Paid-offer controls are not part of the first Publish dialog. They are managed in Creator Studio after seller approval. Checkout validates the listing’s server-side offer, and gated files are delivered only through entitlement-checked signed URLs.
Marketplace web address
Public listing and marketplace navigation now use market.flowmo.ai as the canonical marketplace origin. Newly copied public links should use that domain.
Tips
- Show the result and setup requirements in the thumbnail, demo, and description.
- Use a changelog that tells existing installers whether an update changes structure, dependencies, or organization resources.
Limitations and important notes
- Creator Studio and paid offers require an approved seller status.
- Marketplace publishing does not publish the source project’s domains or give buyers access to its organization.
- Removing a listing stops new discovery; prior acquisition history can remain visible as unavailable.
Troubleshooting
Creator Studio is missing
Open Account and check creator application status. The tab appears for approved or paused creator accounts; community publishing remains separate.
Buyers still receive the old content
Edit the listing and explicitly refresh/replace the frozen bundle. Bump the version if existing installers should see Update available.
The Agent asks questions or only opens a dialog
Answer missing target/purpose/category/tag/thumbnail questions, inspect the exact graph snapshot and listing details, then press Publish in the native dialog. The Agent cannot treat preparation as successful publication.