Install a marketplace connector
A marketplace connector (item kind node) is a WebAssembly component that
adds a reusable node type to the workflow builder. Once installed, it appears in
the node palette and can be wired into any workflow in your workspace — with
network egress limited to the resource credentials you map at install time.


Browse the catalog
Section titled “Browse the catalog”Open the Marketplace page in the sidebar. Use the filter bar to narrow by:
- Kind — select Connector to see
nodeitems only. - Search — substring search across an item’s name and summary.
- Verified — tick to show only items that passed the automated review gate.
Each listing shows its current price (free or one-time purchase), publisher, install count, and average buyer rating.
Install a connector
Section titled “Install a connector”-
Open the item page. Click a connector in the catalog to see its detail page: port schema, declared resource requirements, capabilities, and changelog.
-
Open the install wizard. Click Install on the item. The first step is the Install Preview, where SupaCloud resolves transitive dependencies (other marketplace items the connector relies on) and lists every resource kind it needs (for example,
seafile_webdav). -
Map resources. For each required resource kind, select an existing workspace resource of that kind from the dropdown. (Create the resource beforehand under Resources if you do not yet have one.) The connector can only reach the hosts declared by the resources you map here — no ambient network access is granted.
-
Accept the capability surface. Read the connector’s declared capabilities and confirm. This step is mandatory; the install does not proceed until you confirm.
-
Complete the install. Click Install on the final confirm step. (For paid items you must complete the Stripe checkout earlier, on the preview step, before you can continue.) SupaCloud registers the connector in your workspace’s node-type registry.
Install a package that ships a database schema
Section titled “Install a package that ships a database schema”Some marketplace items — a workflow or script that needs its own tables, not only a connector — ship a shared database schema (ADR 0057). When an item declares one, the install applies that schema’s migrations onto a PostgreSQL resource you map, so the item’s flows have their tables on first run.
- The install requires a
postgresqlresource mapping. The Install Preview listspostgresqlamong the required resources; map an existing PostgreSQL resource (or create one under Resources first). Without it the install is refused — the schema is never skipped silently. - The preview discloses the database footprint: the schema name, its tenant isolation, and each migration’s name with a SHA-256 fingerprint of its SQL, so you can review exactly what runs before you confirm.
- The apply is all-or-nothing: if the schema cannot be applied, the install is rejected and nothing is left behind. Re-installing resumes cleanly.
Use the connector in a workflow
Section titled “Use the connector in a workflow”After installation the connector node type is available in the workflow builder:
- Open or create a workflow in Workflows.
- Click the + button on the canvas to open the node palette.
- Find the connector under its category or search by name.
- Drag it onto the canvas and wire its input and output ports to other nodes.
- In the node’s settings panel, the resource bindings you mapped at install are pre-filled — you can change the binding per-node if your workspace has multiple resources of the same kind.
Ratings and updates
Section titled “Ratings and updates”Leaving a rating. Once you have installed the connector, the rating form on the item detail page lets you leave a star rating (1–5) and a short comment. Ratings are install-gated — only a workspace that has installed the item can rate it.
Update-available signal. When the publisher releases a new version, an Update available badge appears on the item’s catalog card and an update banner on its detail page. Click Update now to apply the latest version in one step; your existing resource mappings are kept.