If you're clicking around a UI, hand it to Claude
Here's a pattern we hit again today, and it keeps repeating across systems. We're sharing it because we wish we'd internalized it sooner.
If you find yourself clicking around in a SaaS console more than twice, stop. Spend five minutes giving Claude API access instead.
The setup is almost always cheaper than the second round of clicking. And from that point on, the system is something Claude can operate, audit, and integrate — not something you have to babysit.
What happened today
We wanted to check on Google Search Console. The marketing site, the creator portal, and the storefront all live under merchsage.com, and we'd just shipped a sitemap index that unifies them. Was it being picked up? Were the right URLs indexed? What were people actually searching for?
The instinct was to open the Search Console UI and start clicking. Pick a property, click into Performance, click Sitemaps, click Coverage, switch property, repeat.
Instead — five minutes:
- In GCP, enable
searchconsole.googleapis.comon the project. - In Search Console, grant our existing service account
Fulluser access on the Domain property.
That's it. Two web operations. From that point on, Claude could:
- List every sitemap registered against the property, with submission dates, error counts, and warning counts.
- Pull the last 28 days of search analytics — top pages, top queries, clicks, impressions, CTR, position.
- Inspect any URL to see its indexing state and last crawl time.
- Delete the stale sitemap that was registered against a domain we don't even own anymore.
- Find a real bug: the portal's static
index.htmlwas a copy of the marketing site's<head>, so its canonical pointed to the wrong domain — which is exactly why the portal had been quietly "Discovered, not indexed" for days. Five-minute fix.
None of that was in our heads when we started. None of it would have come out of clicking around the UI.
Why this works
The UI is optimized for one human, one screen, one task at a time. The API is optimized for programs — and Claude is a program that can read your code, your docs, your DB, and your prior work, and synthesize across all of it.
When Claude has both the API and the context, the kind of thing it produces is qualitatively different. It doesn't just answer "are the sitemaps OK?" — it also notices that one of them points to a dead domain and offers to delete it, then notices that a property isn't being indexed and traces it back to a <link rel="canonical"> mistake in an HTML file that was scaffolded from another app.
A human clicking around might catch one of those things. Not both. Definitely not in five minutes of investigation.
The pattern
Every external system MerchSage depends on — Kestra, PostgreSQL, S3, Stripe, Google Cloud, Search Console, the Printful API, even our own internal services — Claude can drive directly. The cost of getting there is always similar:
- Enable the API in whatever provider console controls it.
- Create or reuse a service account / API token.
- Grant that identity scoped access to the thing you care about.
- Store the credential somewhere Claude can read.
It's usually less work than the first manual workflow it replaces. After the second workflow, it's free money. By the tenth, it's the only sane way to operate.
The signal
The signal is the clicking itself. The moment you notice that you are the bottleneck moving the mouse around — verifying things, copying values between tabs, checking the same dashboard for the third time today — that's the system telling you it should be wired up to Claude, not to you.
Five minutes. Do it now. Future-you, debugging something gnarly at 11pm, will be grateful.