Automate Helium 10

What I mean by automating Helium 10

Automating Helium 10 means a bot logs in, navigates to the tool you'd use (Cerebro, Magnet, Profits, Black Box, whichever), runs the query, and either downloads the export or scrapes the on-screen table. You point it at the ASINs or keywords from a sheet, and it works through them one at a time, on a schedule if you want.

The login is the hard part. Helium 10 sometimes adds a "verify it's you" check or a 2FA step, and a bot has to be prepared for that. axiom handles it by storing the session cookies after a one-time human sign-in, so subsequent runs walk straight past the login screen.

Reading and writing data is already solved

Helium 10 has an API on its highest-tier plans, but most sellers don't subscribe to that tier. The browser is the only path. The right pattern is: log in once (a real human), capture the session, then have axiom drive Chrome with that session loaded. The downloaded CSVs go into a Google Sheet or land in a webhook.

Who this is for

This is for Amazon sellers and agencies that hit Helium 10 every day or every hour. Pulling Cerebro on a list of competitor ASINs. Tracking Magnet results for a set of seed keywords. Checking Black Box for new product ideas on a schedule. Downloading the Profits export for the weekly P&L. If you keep refreshing the same tool with slightly different inputs, a bot can do that for you.

It's also for the developer who wants Helium 10 data wired into a real pipeline. The browser is the only stable surface, and our cloud Chromium runs the same Playwright or Puppeteer scripts you'd write locally.

How I'd approach it

Don't try to log in with a username and password from a bot. Helium 10 will block it, and even when it doesn't, the experience is fragile. Instead, sign in once by hand, capture the session cookies in axiom, and load those on every run. From there, the click work is the same as any other web app.

For the report itself, decide up front whether you're downloading the CSV or scraping the on-screen table. Downloading is more reliable but adds a "wait for file" step; scraping is faster but breaks when Helium 10 changes the table layout.

Automate Helium 10 from a description

Describe the report in plain words in the Chrome extension and it builds the steps for you. Tell it the tool to open, the input list, and where the result should land. Explore no-code.

Automate Helium 10 in code

Build with code. If you would rather script it yourself, this is the path. Explore code

import { chromium } from "playwright";

const browser = await chromium.connectOverCDP(
  `wss://cdp-lb.axiom.ai/?token=${process.env.AXIOM_API_KEY}`
);

const CEREBRO = "https://members.helium10.com/cerebro";

try {
  const context = browser.contexts()[0];
  const page = context.pages()[0] ?? await context.newPage();

  // Cookies for the signed-in Helium 10 session are loaded into the run
  await page.goto(CEREBRO);
  await page.waitForLoadState("networkidle");

  // Each ASIN would come from your Google Sheet
  const asins = ["B08N5WRWNW", "B0BSHF7WHW", "B09B8V1LZ3"];

  for (const asin of asins) {
    await page.locator('input[placeholder*="ASIN"]').fill(asin);
    await page.getByRole("button", { name: "Get Keywords" }).click();
    await page.getByRole("button", { name: /Export CSV/i }).waitFor({ state: "visible", timeout: 60000 });
    const download = await Promise.all([
      page.waitForEvent("download"),
      page.getByRole("button", { name: /Export CSV/i }).click(),
    ]).then(([d]) => d);
    console.log(asin, await download.path());
  }
} finally {
  await browser.close();
}

+

Build with a Claude skill

Build no-code or code bots with a skill.

Add the Claude skill and describe the Helium 10 report you want. It builds the bot for you, no-code or code, handling the login, the query, and dropping the result into a sheet.

Install the skillLearn more

What can you automate in Helium 10?

Most of the click work in the seller tools. A couple of cases worth knowing first.

What I'd watch out for

Helium 10 is a friendly site for a bot once you're past the login. A few quirks bite if you don't plan for them.

Capture the session cookies once

Don't script the username/password. Sign in once in a normal Chrome with axiom's extension, save the cookies for the helium10.com and members.helium10.com domains, and load those into every run.

Reports take time to generate

Cerebro and Magnet can take 30-60 seconds to produce a result on a busy account. Wait for a specific element (the Export button, a row count, a results header) rather than a fixed timeout.

Watch the daily limits

Every Helium 10 plan has per-tool daily limits. A bot will burn through them fast if you don't pace the runs. Add a delay between iterations, or chunk the work across the day.

Test one input first

Pick one ASIN or keyword and run it end-to-end. Confirm the result lands where you expect, then loop the rest.