Cleint credentials setup

Feedback General
1

Describe the problem/error/question

Do clients usually struggle with reconnecting credentials, APIs, or accounts after workflow delivery?

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

@ASHIM_DOLEY , it depends. Are your clients conversant with workflow automation?

3

Most of my target clients are non-technical business owners. In that case, do you find reconnecting credentials, APIs, or accounts becomes a common onboarding challenge after workflow delivery?

4

For non-technical clients, credential reconnection is consistently the #1 handoff problem. A few things that reduce friction:

  • Document exactly which credentials need to be re-authorized and in what order, before you hand over. A short numbered checklist per integration works better than a general readme.
  • For Google services, make sure the client’s account is used during the OAuth flow, not yours - if you set it up with your account, they’ll need to reconnect it anyway.
  • For API key-based credentials, pre-create them in n8n with placeholder values and name them clearly (e.g. “[CLIENT] OpenAI Key - update before use”).
  • For very non-technical clients, a 15-minute screen share for the handoff where they authorize each credential themselves while you guide them prevents most follow-up tickets.
2 Likes
5

Yes, non-technical clients usually struggle with credentials after delivery unless the process is designed for it.

The best setup I have seen is to make credentials client-owned, but not client-unsupported. I would avoid asking for raw passwords or keeping personal access after handoff. Instead, use OAuth/service accounts where possible, document which account owns each credential, and keep a short reconnect runbook for every external system.

For handoff, I would include:

  1. Which credentials exist and what they connect to.
  2. Who owns each account on the client side.
  3. What happens when a token expires or an API scope changes.
  4. A test workflow or health check that proves the credential still works.
  5. A support boundary: what is included in maintenance versus a new change request.

The common mistake is treating credential setup as a one-time onboarding task. In practice it is a maintenance risk, especially with Google, CRMs, ad platforms, and anything with changing scopes. So I would make credential checks part of the ongoing support package.