Share automations (the automation marketplace)
The Automations tab of the Marketplace — sharing a recipe as a copy-paste code with the private parts stripped out, publishing it to the curated cloud catalog, importing someone else's automation as a paused recipe, and the publisher gate that guards it.
On this page
What it is
The Automations tab in the Marketplace lets you share your recipes (multi-step automations — e.g. a daily comic-scraper or digest) with other people, and install ones they've shared. It's a second content type alongside the plugin marketplace.
There are two ways to share, and every path is built to be safe — a shared automation is an executable recipe that runs on someone else's machine:
- Copy a code (offline). On any recipe, click Share → Omniscio packages it into a copy-paste code, stripping out anything private first (secrets, API keys, file paths, and anything tied to your account or projects) and flagging anything key-shaped so you can double-check. Send the code to anyone; they paste it into Import and get the automation.
- Publish to the public catalog. The same Share dialog can Publish the automation to the browsable marketplace (sign in with GitHub the first time). It lands as a pending submission that an admin reviews before it's listed.
However you get one, an imported automation always arrives paused — it can't run until you review its steps and approve it in the inbox. Recipes that depend on something local (another recipe, a local script, a file on disk) can't be shared and Share tells you why.
The public browse grid appears once the cloud catalog is live. If a fetch fails (you are offline, or the catalog service is unreachable) the tab shows the last catalog it loaded, with a line saying it may be out of date, rather than an empty grid. That copy is for reading only: installing from it re-reads the listing first. The code-based import path works with no internet at all.
Where to find it
How to use it
- Share one of your recipes. In the Recipes view, hover a recipe and click the Share icon. The dialog shows the copy-paste code (with what was removed and any secret warnings), plus a Publish to the marketplace option (pick a category → Publish).
- Import from a code. Marketplace → Automations → Import automation → paste the code. You'll see a preview (name, step count, and a reminder it stays paused) before you import.
- Browse & install. The Automations tab lists shared automations once the catalog is live. Search them and click Install to add one as a paused recipe. Installing one you already have does not add a second copy: the install answers with the recipe you already have. If a refresh fails, the grid keeps the last catalog it loaded and says it may be out of date.
- Approve before it runs. Every imported/installed automation is paused. Open it in the inbox, review the steps, and approve it — only then can it run.
- Review submissions (admins). If you're a marketplace admin, a Review queue appears at the top of the Automations tab: Approve (publishes it) or Reject each pending submission.
- Take down your own listing. A card you published shows Unpublish. If it does not, read the account line above the search box — it says which marketplace account the tab is using, or why Unpublish is hidden and what to run to sign in.
How it behaves
Good to know
Publishing needs an approved publisher account, not just a sign-in. Publish is refused with a 403 unless your account is an approved marketplace publisher (admins always pass). The first refusal records your request so an admin can approve you, and nothing about the automation is stored. It is the same gate that covers plugin uploads — see plugin-marketplace.md and the publisher-gate contract. Sharing by code is unaffected — it never touches the cloud.
Nothing private ever leaves your machine — sharing builds the public copy from an allow-list of safe fields, so a secret hiding in an odd field simply never travels.
"Requires: Jira · Supermail" tells you what to connect BEFORE you install. An automation that works across your apps only runs if those apps are set up on your machine — the person who wrote it had their own Jira connected, you might not. Every listing now declares what it needs, and the browse card shows it while you are still deciding. If you install one anyway, its first step checks your actual setup and stops with a plain sentence telling you what to turn on, instead of failing halfway through and leaving things half-done.
Publishers do not have to get this right by hand: publishing reads which apps an automation actually uses and flags any it forgot to declare. A cross-app automation is not blocked from being published just because it needs Jira — needing an app you can go and connect is a normal thing for an automation to do, unlike depending on a file that only exists on the author's computer, which still blocks sharing.
Curated: published automations are reviewed by an admin before they're publicly listed.
The catalog lives in the marketplace's own cloud project (separate from your app data); see automation-marketplace-contract.md.
Who sees Unpublish, and which account the tab uses
- Unpublish follows the marketplace's own answer, never the author's name. The tab asks the marketplace which listings the signed-in account published and offers Unpublish only on those. A byline is just a display name, so two developers with the same name never see each other's button. If that answer cannot be read, nobody sees Unpublish.
- A line above the search box names the account. It reads "Managing your listings as @handle", and adds "Signed in with amc-plugin on your computer" when the sign-in came from the command-line tool. On a phone it describes the computer the app runs on.
- Signed out, it says so and gives the two commands. Installed builds have no sign-in button
of their own; they use the sign-in of the
amc-plugincommand-line tool on your computer. Runnpm install -g @agent-mc/plugin-cli, thenamc-plugin status— the first run opens GitHub sign-in in your browser and publishes nothing — then reopen the tab. The tool has nologinsubcommand. - Expired, it says it could not be renewed. Run
amc-plugin statusagain (or, in a developer build that signed in on My Plugins, sign in there again), then reopen the tab. - "Couldn't check which automations are yours" means you are signed in but the marketplace did not answer the ownership question just now, so Unpublish stays hidden. Reopen the tab to try again.
- Someone else seeing Unpublish on your listing means their computer is signed in to the
marketplace as the account that published it — their own account line shows which one.
Running
amc-plugin logouton that computer signs the app out too. Company (workspace) listings are covered by Org marketplace.
Ratings, ranking and what a block does
Two things about the catalogue are worth knowing because they change what you see:
- Only an established account moves the ranking. A download counts, and a new rating counts toward the published average, only when the account doing it is at least a day old. The ranking drives the default "popular" order and the Featured row, and a free sign-up was otherwise enough to buy either — or to 1-star a competitor. Editing a rating you already left is never gated.
- Blocking a publisher delists their work. When a publisher is blocked for abuse, everything they had already published is taken offline with them (and restored if the block is lifted). Only the listings that block itself took down come back — anything suspended separately stays down.
Related
The plugin half of the same marketplace is covered in Plugin marketplace, and both share the publisher gate described above. What an installed automation's steps behave like is set out in Automation Rules, and the secrets an automation asks you to connect are stored the way Automation credentials describes.
Last verified 2026-11-05