Hey Reinis! That error almost always means domain-wide delegation isn’t fully set up (or the scopes/user you’re impersonating aren’t allowed). Quick checklist that usually fixes it: 1) Workspace vs personal Gmail - Service Accounts with impersonation only work on Google Workspace (not @gmail.com). Make sure the user you’re impersonating is a Workspace user with Gmail enabled. 2) Turn on Domain-Wide Delegation for the SA - In Google Cloud Console → IAM & Admin → Service Accounts → [your SA] → Show advanced settings, tick “Enable Google Workspace Domain-wide Delegation.” - Note the Client ID shown there. 3) Authorize the SA in Admin Console - In Admin Console → Security → API Controls → Domain-wide delegation → Add new, paste the Client ID from step 2 and add the scopes you need. For sending mail, at minimum: https://www.googleapis.com/auth/gmail.send - If you also read/label threads, add: https://www.googleapis.com/auth/gmail.modify - Save. (Common gotcha: scopes must be comma-separated with no spaces.) 4) n8n credential fields - In the Gmail node credentials choose Service Account. - Client Email = the SA email (…@…iam.gserviceaccount.com) - Private Key = from the JSON key. Make sure line breaks are preserved (if it’s in an env var, replace \n with actual newlines). - Toggle Impersonate a User ON and set the Workspace user’s email you want to send as (must exist and have Gmail license). 5) Usual culprits - Wrong Client ID authorized in Admin Console (it must match the SA’s Client ID, not the numeric project ID). - Scopes typo/missing (especially gmail.send). - Time skew on the n8n server (JWTs are time-sensitive). Ensure the server clock is correct (NTP). - Trying to impersonate a user in a different domain or an alias that isn’t the primary mailbox. 6) Quick sanity test (outside n8n)

@Reinis Varavs Totally get it, Reinis [if you’ve ticked all those boxes and it’s still 401’ing, here are the next things I’d check (these are the ones that usually catch even seasoned folks)]: 1) Verify the exact client ID + scopes actually landed in Admin Console Security → API Controls → Domain-wide delegation → click your entry → confirm: - Client ID matches the SA’s unique numeric client ID (not project number). - Scopes are comma-separated, no spaces. - It shows a recent “Last authorized” timestamp (if not, re-save). 2) Gmail API is enabled on the SA’s project Cloud Console → APIs & Services → Library → Gmail API = Enabled. 3) The impersonated user is a real primary mailbox - Same Workspace domain, has a Gmail license, and you’re using the primary address (not an alias/group). - Org policy isn’t restricting the Gmail API for that OU. 4) Private key formatting - In n8n credentials, the private_key must keep real newlines. If you pasted an env var with \n, replace with actual line breaks. 5) Server time skew - JWTs are time-sensitive. Make sure your n8n host clock is correct (NTP). A few minutes off can trigger 401. 6) n8n credential type alignment - Gmail node → “Service Account” (not Google OAuth2). - Impersonate a user = ON, and Subject = that user’s email. 60-second proof inside n8n (bypasses the Gmail node to isolate auth): 1. Create Credentials → Google (Service Account) using the same SA JSON. 2. Add an HTTP Request node: Method: POST URL: https://oauth2.googleapis.com/token Body (x-www-form-urlencoded): grant_type: urn:ietf:params:oauth:grant-type:jwt-bearer assertion: <JWT> If your credential supports SA JWT automatically (newer n8n), you can instead select the SA credential and set OAuth2 → Google SA (JWT) with Impersonated Email. If this returns a token (200 with access_token), auth is fine → the issue is node config; if this still 401s, it’s a DWD/scopes mismatch.

Great question, Aaron! You’re definitely not alone (almost everyone starts out feeling like their prompts are “average”). A few good places to dig in: A. Communities like this one [people are constantly sharing tested prompts (especially for AI automation use cases)]. B. Prompt marketplaces & libraries (sites like FlowGPT, PromptHero, and PromptBase have tons of examples you can adapt). C. Reverse-engineering [when you see someone share a cool result (like an agent workflow or content output), ask “what prompt got you that?”]. You’ll be surprised how generous folks are when you ask. D. Iterating your own (honestly, the best prompts usually come from you testing, refining, and adjusting based on your exact workflow or niche). So think of it as half “find inspiration,” half “tweak until it fits your use case.” That’s where the magic happen.

ようこそ、五郎さん ! コンサルティング事業とスクールの両方を立ち上げられたことに大きな敬意を表します（とても強力な組み合わせですね）。おっしゃる通り、日本がAI導入において「遅れている」というのは、実は先行者にとって素晴らしいチャンスだと思います。企業は信頼できるガイドを探しているはずで、五郎さんはまさに完璧なポジションに立たれています。また、翻訳ツールを使って言語の壁をすでに乗り越えているところも素晴らしいです。もしよければお伺いしたいのですが、日本の企業はまずコスト削減のための業務自動化に関心が強いのでしょうか？それとも成長や顧客体験向上のためのAI活用により関心を持たれているのでしょうか? 日本市場をどのように形づくられるのか、とても楽しみにしていま Welcome, Goro! Huge respect for launching both a consulting business and a school (that’s a powerful combo). You’re absolutely right: Japan being “behind” in AI adoption is actually an incredible opportunity for first movers. Businesses there will be looking for trusted guides, and you’re positioning yourself perfectly. Like that you’re already bridging the language gap with translation tools. If you’re open, do you see Japanese companies more interested in process automation to cut costs first, or are they leaning toward AI for growth and customer experience? Excited to see how you shape the market in Japan.

Welcome, Mike! Like that you’ve got a coding background (that’s such a superpower in this space). The cool part about the AAA model is it blends your technical creativity with solving very real business problems (and people pay well for that). Are you leaning more toward building custom automations from scratch with your coding skills, or are you planning to package solutions using no-code/low-code tools first to get traction?

@Bill Wilkey Appreciate that, Bill! Makes sense (almost like discovery-first rather than pitching a menu). Instead of saying “here are 3 agents,” you let the client reveal where the biggest pain actually is, then map the right agent to that. When you run that consultative approach, do you ever find clients think their main problem is one thing (say, lead gen), but it actually turns out to be something else (like revenue leaks or poor CX)?

@Charles Jackson Charles (appreciate that, brother!). Have you found CX pain (missed calls, support gaps) to be the biggest door-opener in your convos too, or do prospects in your niche respond stronger to revenue-focused angles?