Publishing a listing

Publishing a listing

Organization admins can build a Loop or a tool and publish it to the Marketplace, from the Developers page. It runs on Harmony, not your servers: each installer gets their own copy, running as them on their own connections. You see installs, runs and outcomes, never their records.

Developers → Marketplace listings: your publisher profile, your listings with their status, and their installs and runs

Listings are built in five steps: Start, Build, Test, Listing and Submit.

Before you start: your publisher profile

Open Developers from the organization menu and choose Marketplace listings. Your organization needs a publisher profile before it can build listings; it shows at the top with its support email and website. Harmony checks publishers before they appear as Verified publisher; an organization's policy can limit installs to Harmony and verified publishers.

1. Start

  1. On Marketplace listings, under Start something new, choose Loop or Tool.
    • Loop: recurring work on a schedule, or started by hand. Installs as a Loop of the installer's own.
    • Tool: know-how for one job that people and Loops can call. Installs as a custom tool.
  2. Enter a Name and choose a Category.
  3. Under Describe it, write what it should do, and choose Draft with Harmony. Harmony drafts the instructions, the steps and what each one touches; you review every line next. Or choose Start blank instead.
  4. Or start from a Loop you already run: its instructions, schedule and connectors are copied into a draft. Its runs, data and connections stay behind; installers bring their own.

Starting a new listing: Loop or tool, a name, and a description for Harmony to draft from

2. Build

Write what the installed Loop is asked to do, when it runs, and every step it takes.

  1. Instructions: what the installed Loop is asked to do, written to Harmony.
  2. Runs: How often (when someone runs it, every few hours, daily, weekly or monthly) and when. Installers can change the schedule when they install it.
  3. Steps: add each step with Read, Write or Model:
    • Reads from a connector: choose the connector, What it reads, and Only these fields.
    • Writes to a connector: choose what it writes and whether it Reaches people inside or outside the installer's company. Each write is sent once per run, even if the run is retried.
    • Works it out with Harmony's model: reasoning with no connector.
  4. Set the Version number and What changed. Installers see this with the update.

Each step declares exactly what it touches. Those declared reads and writes become what installers approve.

The Build step: instructions, schedule, and steps that each declare what they read or write

3. Test

Run the same checks every listing passes before review, then try it for real.

Check What it confirms
Lint The steps are valid and each one declares what it touches.
Binding The connectors it names exist in the catalog.
Write declarations What it writes is declared.
Policy scan It asks for no credentials, and its access is only what the steps declare.
Live run A test of this version ran in your own organization.

Choose Run checks, then Test run to run the version as a private test Loop of yours, with your connections. The listing shows what a run typically uses, measured from your test runs.

The Test step: five checks, declared reads and writes, and test runs

4. Listing

Write the page installers read before they install.

  1. Choose an Icon, and check the Name and Category.
  2. Write a Tagline (one line on its card) and a Description: what it does, what lands where, and what it needs.
  3. Optionally estimate Hours saved per run. Installers see it labelled as yours; Harmony counts it only for runs they accept, unless they set their own.
  4. Price: installers pay Free; each run counts on the installer's usage limit.
  5. Choose who can install it:
    • Only your organization can install it
    • Anyone with the link (not in the Marketplace list)
    • Public Marketplace (listed for every organization)

The Card preview shows it as installers will, with what they'll be asked to approve.

The Listing step: icon, name, category, tagline and description, with a live card preview

5. Submit

The checklist shows Every check passes and The listing page has a tagline and a description. Choose Submit.

  • Nothing it writes leaves the installer's company: it's published as soon as the checks pass.
  • It writes to people outside the installer's company: after the checks, a person at Harmony reviews it. They check that what it sends outside reads like something the recipient should get, that it reads no more than its steps need, that each write is sent once even when a run is retried, that the listing page matches what it does, and that nothing in it tries to widen its access at install.

While it's being reviewed it shows In review. If the reviewer asks for changes, you see Changes requested with their note; edit and submit again. Once published, Copy link to send it to people who should try it.

The Submit step: review stages, what the reviewer checks, and sharing the link

Release a new version

Open the listing and choose New version. Make your changes, test them, and submit. Installers see What changed with the update. If the new version reads or writes more than the last one, each organization's stewards approve it before their copies move to it.

FAQs

Does my listing run on my servers? No. It runs on Harmony in each installer's organization, as the installer, on their connections.

Can I see installers' data? No. You see installs, runs, completion and reviews, never their records, results or connections. See Listing numbers.

Can I charge for a listing? Listings are free. Each run counts against the installer's usage limit.