# Sharing

> Turn an automation into a link anyone can open and copy, with every account, proxy and secret left behind.


Sharing hands one of your automations to somebody else as a link. They see the whole flow, read what each step does, and copy it into their own account. Nothing about your accounts, groups, proxies or connections travels with it.

## Creating a share link

**Share** sits on every row of the **Automations** list and in the header of the builder. It opens one modal that both creates the link and manages it afterwards.

The automation has to be finished first. If the builder still flags a missing trigger or a half-filled step, sharing refuses and tells you to finish it: a share is a recommendation, so it has to be something the reader can actually run.

| Field | What it does |
| --- | --- |
| **Shared name** | The title at the top of the share page. Your own automation keeps its own name |
| **Description and usage notes** | Optional, up to 2,000 characters. Shown under the title as **About this automation** |
| **Include canvas notes** | On by default, and only offered when the canvas has notes. Turn it off if yours are private reminders |
| **Show my name** | Off by default. When on, the page reads "Shared by" and your chat name. When off, it reads "Shared by a SteamLabs user" |

**Create share link** publishes it and hands you the link straight away, with a copy button, so there is nothing to go back and look up. The automation also picks up a share icon in the list, so you can see at a glance which of your flows are out in the world.

An automation has one share link. After you share, the builder header and the row menu say **Update share**. Opening that modal shows when you first shared, when you last updated the snapshot, and how many times it has been imported. **Update share** writes a new snapshot over the same link, so anything already pasted into a chat keeps working.

New visitors to the link see the updated snapshot. People who already imported keep their own copy.

> [!IMPORTANT]
> The link is the key. Anyone holding it can open the page and take a copy, so treat it like any other unlisted URL. There is no public gallery, and the page asks search engines not to index it.

## What the link carries

The share is a snapshot taken the moment you press the button, not a live mirror of your canvas. Edits you make afterwards stay yours until you press **Update share**.

Everything in that snapshot is stripped of tenant detail first. What survives is the shape of the flow and the settings that mean the same thing in anybody's account.

| Part of the automation | What the link carries |
| --- | --- |
| Steps, branches, and the order they run in | All of it |
| Schedules, waits, gate counts, filter conditions, notification text | All of it, minus your timezone |
| Task steps | The task type and its settings, minus every account, profile and trade link inside |
| Tags | The tag names, recreated as the reader's own tags on import |
| Canvas notes | Included by default, or left behind on the share form |
| Hand-picked accounts | Nothing. A **Select accounts** step that pointed at a list arrives set to all accounts |
| Account groups | Nothing. A group filter, a **Set account group** target, and a filter condition on a group are all removed. Ungrouped is the one exception, since it means the same thing everywhere |
| Proxies and proxy groups | Nothing. A **Test proxies** step narrowed to a group or a hand-picked set arrives widened to all proxies |
| Inline webhook details | Nothing. A Discord, Telegram or custom destination configured on the step is removed, credentials and all |
| Trade URLs, wallet codes, API keys, tokens, passwords | Nothing, wherever in the automation they sit |
| Your numbers | Nothing. The page describes rules instead of counting them, so a step reads "Accounts matching 3 filters", never how many accounts you own |

Tags are the one thing that travels by name, because a name is cheap and a tag is easy to recreate. A step that adds `Prime` still says `Prime` on the share page, and the reader gets their own tag of that name on import.

Nothing is taken out silently. Whatever could not travel is recorded on the share, counted in the notice the importer gets, and badged on the steps themselves once the copy opens in their builder, which is where they can actually do something about it.

## What a reader sees

The share page opens at a short link and shows, in order:

- The title, the byline, the step count, and what the automation runs on.
- A miniature of the canvas, so the shape of the flow reads at a glance.
- **About this automation**, your description, when you wrote one.
- **How it works**: every step in order with a one-line summary, the trigger badged **Runs on**.
- A **Needs a linked FarmLabs** notice, when a step only fires through the FarmLabs integration.

Canvas notes are not listed here. They travel with the automation and appear pinned to the steps they belong to once the copy is open in the builder, which is the only place they mean anything.

A signed-out reader gets one call to action, **Sign in to add it**, and signing in brings them straight back to the page. A signed-in reader gets **Add to my automations**. A reader whose plan does not cover automations still reads the whole page and meets a **See plans** button instead of a wall.

Opening your own link shows you exactly what everybody else sees, with a note saying so.

## Importing

**Add to my automations** asks for a name and copies the automation into the reader's account. It always arrives as a **Draft** and opens in the builder, so nothing a stranger wrote can run before its new owner has looked at it.

What the copy sorts out on its own:

- Tags are matched to tags of the same name, or created. One import can create up to 25 new tags.
- Schedule times are re-stamped in the importer's timezone, so 09:00 keeps meaning nine in the morning where the automation now lives.
- Webhook steps point at the importer's own saved integration of the same kind, so connecting Discord or Telegram on the **Notifications** page is all that step needs.

What is left to finish, badged on the canvas and counted in the notice:

- **Select accounts** steps start from all accounts. Narrow them.
- **Set account group** steps and group conditions need one of your own groups.
- Tag steps whose tags could not travel need tags choosing.
- A task step whose type is not available to create right now needs a new one.

The notification after an import says how many steps still need setting up, and the builder badges them on the canvas. Fix those, then activate.

Importing the same link twice makes a second, separate copy. Imports are capped at 10 a minute per account.

## Sharing into chat

Paste a share link into community chat and it renders as a card instead of a bare URL: the name, the description, what it runs on, the step count, the byline, and a row of step icons. **View and import** opens the share page inside the dashboard rather than in a new tab.

The card is read from the share every time the message renders, not stored in the message. So a card always shows the current name and description, and a share that has been stopped leaves the message in place with the card gone.

## Stopping a share

Open **Share** on the automation and use **Stop sharing** at the bottom of the modal.

- The link stops working immediately. Anyone opening it lands on "This link is not available".
- Cards already posted in chat go quiet, and the messages stay.
- Copies people already imported are theirs and are not affected.
- Sharing again later mints a new link. The old one never comes back.

Deleting the automation takes its share down with it.

> [!NOTE]
> Sharing, like the rest of the automation builder, is dashboard only. There is no user API for publishing or importing a share.