Why We Built an n8n Credential Setup Coach (And Secretly Use It Ourselves)

Here’s an uncomfortable truth about selling n8n workflows: the workflow is rarely the hard part.

The hard part is the moment after import — the moment the canvas lights up with red credential warnings and your client messages you:

“It says connect Google Sheets. I clicked Sign in with Google. Now it’s angry.”

That message is the start of a support saga. We know, because we lived it. A lot.

The client credential walkthrough from hell

We’d ship a clean automation — Gmail trigger, Sheets log, Slack alert, the works. Setup guide attached. Screenshots included. Coffee still warm.

Then the call would go like this:

• “Which Google account am I supposed to use?”
• “It opened the wrong Google account.”
• “I don’t see the button in your screenshot.”
• “What’s a redirect URI?”
• “It worked yesterday. Today it says redirect_uri_mismatch.”

None of those are workflow bugs. They’re credential bugs. And credential bugs do not respect your calendar.

So we’d hop on Zoom. Share screen. Squint at Google Cloud Console together. Celebrate when OAuth finally worked. Then discover Slack needed a bot token, not the OAuth app we just spent 40 minutes building. Then Postgres. Then OpenAI billing wasn’t enabled so the “AI” node failed with a mysterious 429 that looked like a personality disorder.

We were not selling automations. We were running unpaid credential concierge service.

Documentation didn’t save us

We tried longer setup guides. Better screenshots. “Common errors” sections that grew like kudzu.

People still got stuck — because OAuth UIs change, provider portals rearrange themselves overnight, and a 12-step article is somehow both too long and missing the one sentence you need when you’re on the wrong screen.

What clients actually needed was not another PDF. They needed someone (or something) to say:

Do this one tiny thing. Then say next.

So we built that.

Enter Credential Setup Coach

The n8n Credential Setup Coach is a chat workflow — a searchable catalog of 60+ credential tracks across Google, Microsoft, Slack, AI providers, databases, AWS, CRM, commerce, and more.

You type what you want:

• google sheets
• postgres
• I want to set up mysql
• search sms

It asks where you’re starting from. Shows one small action. Waits for next. Continues. No novel. No jargon dump. No “see appendix C.”

Stuck? Type stuck or this screen looks different. Optional AI help gets the actual instructions you were looking at — not a vague “you’re on step 3” hallucination.

And when you’re done connecting, you don’t guess. You test.

The glorious test sheets moment

This is our favorite part — and honestly the reason we trust the coach more than our own memory.

After you create a Google Sheets credential, you type something like:

test sheets YOUR_SHEET_ID

The workflow doesn’t shrug and say “looks fine.” It runs a live smoke test against Sheets. Same idea for Gmail, Drive, Calendar, Slack, Postgres, OpenAI, and other services with dedicated test nodes.

When that test passes, something magical happens in your brain:

Oh. We’re actually good.

Not “probably good.” Not “the OAuth screen smiled at me.” Actually good — as in the credential can read the sheet, right now, in this n8n instance.

For services without a live test node, test <service> still marks the track verified after you’ve created the credential, so your status checklist stays honest.

That confirmation loop is what we were missing in every Zoom walkthrough. Screenshots prove you clicked something. A smoke test proves it works.

The secret we didn’t plan to admit

We built Credential Setup Coach for clients.

Then we… started using it ourselves.

Quietly at first. Like people who invent a meal-prep system and pretend they still cook from scratch.

New client needs Sheets + Slack + OpenAI? Open the coach. Type the services. Follow the steps. Hit test sheets. Hit test slack. Move on with our lives.

Self-hosted OAuth redirect fighting us again? Type selfhost and stop reinventing the WEBHOOK_URL speech from memory.

It turns out the people who most needed a credential coach were also the people who were supposed to be “experts.” Expertise doesn’t mean you enjoy Google Cloud Console on a Friday afternoon. It means you know better than to wing it twice.

What this changed for us

• Support got shorter. “Open the coach and type google sheets” beats a 45-minute screen share.
• Onboarding got calmer. Clients move one step at a time instead of drowning in a setup novel.
• Our own setups got faster. Reusable credentials, verified once, used across every workflow we ship.
• Confidence went up. A green smoke test is a better goodbye than “try it and let us know.”

If you’ve ever been stuck at “Connect your credentials”

You’re not bad at n8n. You’re hitting the part of automation nobody puts on the marketing page.

We built the coach because we got tired of living there.

If you want the same escape hatch:

Type the service. Do one small thing. Say next. Then type test sheets — and enjoy the rarest feeling in automation: certainty.