Auto-sync your shop: push new products to your link in bio

You can sync products to your link in bio automatically by pointing a small script or an AI agent at the isall.me API or CLI, so every new drop lands at the top of your page without you touching the dashboard. There is no magic auto-poster button; you wire your own store data to the isall.me tools, and it runs whenever you tell it to.

This is a builder guide, written by the person who makes isall.me. I will be straight about what is built in and what you assemble yourself.

The problem this solves

You add a new product to your shop. Then you go update your link in bio so it points at the new thing. Then you do it again next week. It is small, but it is the kind of small that never stops.

The fix is to let the update happen on its own. When a product goes live, something notices and pushes it to your page. You keep making things; the page keeps itself current.

What "auto-sync" really means here

Let me set expectations before you build anything.

isall.me does not have a built-in one-click auto-poster that watches your store for you. What it has is a full set of developer tools: a REST API, a CLI, and an MCP server. You point your own script or agent at those tools, and that is what does the syncing.

So "auto-sync" is a pattern you set up, not a switch you flip. The good news is the pattern is short, and you only build it once.

The pieces:

• A source of truth. Wherever your products live: a store, a spreadsheet, a JSON file, a webhook.
• A trigger. Something that runs on a schedule or when a product changes.
• The isall.me tools. The API or CLI that actually writes the update to your page.

Get your token first

Everything below needs a token. Mint one in your dashboard under the Developer tab. It starts with isam_ and it is a Pro feature.

For a shop sync you want a full-access token, not the read-only option, since the whole point is writing new products to your page. Keep it secret. Store it as an environment variable, not pasted into your code.

Full reference for every endpoint and command is at the hub: https://isall.me/developers.

Option 1: a scheduled script (the reliable way)

This is the most predictable approach. A script runs on a timer, checks your products, and updates your page.

The isall.me CLI is on npm as isallme. You run it with npx isallme. In a script you would read your latest products from wherever they live, then call the CLI to add or reorder links on your page.

The rough shape of the job:

1. Read your current products from your store or data file.
2. Compare against what is already on your page.
3. For anything new, call the isall.me CLI or API to add it as a link at the top.
4. Optionally remove sold-out items.

To make it automatic, put that script on a schedule. A cron job on a server, or a GitHub Action on a timer, both work well. A GitHub Action is nice because it needs no server of your own; you store the isam_ token as an encrypted secret and let the Action run every hour or every morning.

The result: a shop that auto-adds new products to the top of the page, running on its own, built by you in an afternoon.

If you want the CLI specifics, /blog/link-in-bio-cli walks through the commands. For the raw endpoints, /blog/link-in-bio-api covers the REST layer.

Option 2: an AI agent (the flexible way)

If you would rather describe the behavior than code every step, use an agent.

The isall.me MCP server (isallme-mcp on npm, run with npx -y isallme-mcp) exposes tools that let an AI assistant read and update your page. You connect it to an assistant like Claude, hand it your token, and then you can hand it a task like "here is my latest product list, put anything new at the top of my page and match the styling of the others."

An agent is more forgiving when your product data is messy or when the rules are fuzzy. A plain script is better when the rules are strict and you want the exact same behavior every time. Plenty of people use both: a script for the routine sync, an agent for the one-off cleanups.

The deeper walkthrough for standing up an agent that manages your page lives at /blog/ai-agent-link-in-bio.

A concrete example

Say you sell prints and you keep them in a Google Sheet: title, price, image, buy link, and a "live" column.

Your GitHub Action runs every morning. It reads the sheet, filters to rows marked live, and for each new one it calls the isall.me API to add a link at the top of your page with the title and buy link. Sold-out rows get pulled.

You never open the isall.me dashboard. You just keep the sheet honest, and your page follows.

That is the whole game: your data stays where you already manage it, and a small job keeps your link in bio in sync with it.

Keeping it honest and safe

A few things worth saying plainly.

Test with a read-only token or a throwaway link first, so a bug does not scramble your real page. Once you trust the job, switch to the full-access token.

Rotate your token if it ever leaks, from the same Developer tab where you made it. And log what your job does, so when a product shows up wrong you can see why.

Automation is great until it quietly breaks. A job that emails you when it fails is worth the extra ten minutes.

FAQ

Does isall.me automatically post my new products for me?

Not on its own. There is no built-in auto-poster that watches your store. isall.me gives you the API, CLI, and MCP tools, and you point your own script or agent at them. Once you set that up, it runs automatically, but the wiring is yours.

Do I need to know how to code to sync products to my link in bio?

For a scheduled script, some coding helps. For the agent route, much less: you connect the MCP server and describe what you want in plain language. Either way you need a Pro token from the Developer tab, since developer access is a Pro feature.

What should trigger the sync?

Two common choices. A schedule, using cron or a GitHub Action that runs on a timer, is simplest and needs no live connection to your store. A webhook from your store, if it offers one, updates the page the moment a product changes. Schedules are easier to start with.

Is it safe to store my token in a GitHub Action?

Yes, if you use encrypted repository secrets rather than hard-coding the token in the workflow file. Never commit an isam_ token to your repo. If one leaks, revoke it in the Developer tab and mint a new one.

Try it

Claim your link, upgrade to Pro for developer access, then open the Developer tab and mint a token for your sync job. Pro is 24 dollars a year with a 0 percent fee on sales, which matters when you are actually selling.

Create yours at https://isall.me/signup and read the full developer docs at https://isall.me/developers.

Everything you are. One little link.