Version Updates

Marketplace listings support versioning. Sellers can push updates, and buyers can pull them into their cloned workflows.

For sellers: publishing an update

1. Make changes to your source workflow in the editor
2. Save the workflow
3. Go to your listing and click Publish Update
4. Write a changelog describing the changes (required, max 2000 characters)
5. The version number increments and the snapshot is updated

The changelog is visible to buyers in the version history.

For buyers: pulling an update

When a seller publishes a new version, your purchased workflow shows an "Update available" indicator.

1. Open the purchased workflow or check the marketplace listing
2. Click Pull Update
3. Your workflow's nodes and edges are overwritten with the seller's latest version

Warning: Pulling an update replaces your current nodes and edges. If you've made local modifications, they will be lost. There is no rollback.

Owner preview clones can also show update status, but they are for testing what buyers receive. They do not count as sales.

Version history

Both sellers and buyers can view the version history for a listing, showing:

• Version number
• Publish date
• Changelog text

What updates include

• Node additions, removals, and configuration changes
• Edge connection changes
• Layout/viewport changes
• Sticky Notes and Arrows

What updates don't include

Seller credentials and destination config are never included in updates. Pulling an update replaces your cloned workflow's nodes and edges, so you may need to re-enter your own credentials and destination settings (chat IDs, webhook URLs) afterward.

Next steps

• Purchasing - initial purchase flow
• Listing a Workflow - managing your listings