Share a module through the marketplace
- Step 1 · Open your development environment
- Step 2 · Choose Marketplace on the module
- Step 3 · What: the name, what it does and this version
- Step 4 · For whom: your own organisation
- Step 5 · The check, then publish
- Step 6 · Find it in the marketplace
- Step 7 · Read what it does and what it asks
- Step 8 · Allow and install
- Step 9 · Installed, with updates
What you built well once, you do not want to build again in every environment or branch. You publish a module as a package in your organisation's own catalogue, with a version and a release note. Colleagues find it in the portal's marketplace, see what it asks and install it into Development; it then travels with the normal releases. Only the design goes along: no rows, no secrets, no conversations.
What: the name, what it does and this version
At the top is what it is called in the marketplace and what it does: that is what your colleagues read when they find it. Flow fills in the module's name and description; if the module has none, you write one here. An English text may be added, otherwise the Dutch one applies. Below is this version: three numbers (1.0.0), each next one higher, and in one sentence what is new.
The check, then publish
Flow makes the package and the marketplace checks it: fully described, signed by this environment, no secrets in the content, a Flow version that exists, newer than the previous one. If a key or password is in it somewhere, the marketplace refuses it and says where.
This guide was carried out step by step on 28 Oct 2026 by an automated test on Flow (version 96971699).




















