Live links are hosted in your own Cloudflare account, so the URL, the files and the comments all belong to you. Before the first share you run Set Up once: you paste one Cloudflare API token and the app creates everything itself.
There is no wrangler CLI, no config file and nothing to deploy by hand. Live Link needs a PRO licence in the desktop app.
Create the API token
- Create a free account at cloudflare.com if you do not have one.
- Open My Profile → API Tokens and click Create Token → Custom token.
- Give it three Account permissions:
- Workers Scripts: Edit
- Workers R2 Storage: Edit
- D1: Edit
- Create the token and copy it.
This is the same token collaboration asks for. The app remembers it on this machine only, and whichever wizard you run first fills it in for the other.
Run Set Up
- Open any board and click Share board in the top bar.
- On the Live Link card, click Set Up.
- The first screen, Share boards with a live link, explains what you get. Click Set Up (or Not now to go back).
- Under Connect your Cloudflare account, paste the token into the Cloudflare API token field and click Continue.
- If the token can reach several Cloudflare accounts, the wizard asks “This token can access several Cloudflare accounts — which one?” Click the account to use.
The rail on the left, What gets created, ticks off each step as the app works through it. It usually takes under a minute.
| Step | What the app does |
|---|---|
| Verify API token | Checks that Cloudflare accepts the token. |
| Find Cloudflare account | Picks the account the token belongs to, or asks you to choose. |
| Create storage bucket | Creates the R2 bucket moodboard-shares for pages and media, or reuses it. |
| Create comments database | Creates the D1 database moodboard-comments, or reuses it. |
| Prepare database tables | Adds the tables for shares and comments. Existing data is kept. |
| Deploy share worker | Uploads the moodboard-share worker that serves your links. |
| Set upload token | Creates the secret that lets this app publish to the worker. An existing one is kept. |
| Enable public URL | Turns on the worker’s workers.dev address. |
| Check custom domain | Looks for a domain attached to the worker and uses it instead of workers.dev when there is one. |
When it finishes, the wizard shows Sharing is ready with the address new links will use. Click Back to sharing and press Share. No restart is needed.
If setup stops
The rail marks the failed step with ✕ and the wizard reads Setup hit a snag. Nothing is left half-done: fix the cause and click Try again. The usual causes:
- Verify API token fails — the token was mistyped, expired or deleted. Paste it again or create a new one.
- Find Cloudflare account says “The token has no account access” — the permissions were not given as Account permissions. Create a new token as described above.
- A later step fails with a Cloudflare permission error — the token is missing one of the three permissions.
- Enable public URL says the account has no workers.dev subdomain — open the Workers dashboard in Cloudflare once so it creates one, then try again.
Sanity check
Open a board, click Share board, then Share under Live Link. A link appears within a few seconds on your own workers.dev subdomain (or your domain). Open it in a browser: the board appears with comments enabled.
Custom domain (optional)
To serve links from share.your-brand.com instead of workers.dev:
- In the Cloudflare dashboard, attach the domain to the
moodboard-shareworker (Workers & Pages → Settings → Domains & Routes). - Run Set Up again. The Check custom domain step shows the domain it found, and new links use it.
- For a board that is already shared, press Update: the link moves to the new domain.
Keep the workers.dev route enabled — links you already handed out point at it.
A second computer
Sharing is set up per machine. On another computer, run Set Up with the same Cloudflare token. The storage and worker already exist, so the wizard reuses them and keeps the worker’s upload token — replacing it would cut your first computer off.
Because this machine has no copy of that upload token yet, the wizard then shows This worker already has an upload token:
- Use this token — on the computer that already shares, open Settings ▸ Sharing (the API Keys button in the header) and copy the value of the Cloudflare API Token field. That field holds the worker’s upload token, not the token you created in Cloudflare. Paste it here; the app checks it against the worker before saving it.
- Reset token — issues a new upload token instead. Every other computer then loses access until it runs Set Up again.
Running Set Up again
Running the wizard again is safe. On a machine that is already set up it skips the introduction and says where sharing is set up now. The bucket and database are reused, the worker is redeployed, and its upload token is kept, so every link you shared keeps working. Run it again after attaching a custom domain, or when the Share window suggests it with Re-run setup.
Boards with an older link
If a board already has a link but this machine has no sharing storage set up, the Live Link card shows the link with the note “Updating this link needs sharing storage of your own — it is not set up on this machine yet” and a Set Up button in place of Update. After setup, Update republishes the board through your own worker under a new URL.
Editing the connection by hand
Settings ▸ Sharing shows the two values the wizard saved: Cloudflare Worker URL (the address links are published to) and Cloudflare API Token (the upload token). You can edit them there, for example to point this machine at a share worker you deployed yourself; the app treats them exactly like the values the wizard writes.
Where to go next
- Generating a Share Link — publish your first board.
- Updating a Shared Board — push changes and stop sharing.
- Pro Tier Sharing — what the licence covers.
- Setting Up a Shared Board — the collaboration wizard that uses the same token.
Leave a Reply
You must be logged in to post a comment.