Debugging 400 INVALID_ARGUMENT for YouTube Playlist Creation in n8n

What's likely causing the discrepancy

When a node behaves differently in manual versus automated runs, the root causes are usually one of: expression evaluation differences (runtime values missing in automated triggers), OAuth token renewal/permission issues, or payload/encoding differences introduced by intermediate nodes. The 400 INVALID_ARGUMENT suggests the YouTube API received a malformed or incomplete request body or headers in production runs.

Business implications

If media or marketing automation depends on this workflow, broken production executions can delay content publishing, harm campaign timelines, or create manual workload for teams. It also undermines confidence in automation unless you can reliably reproduce and fix the root cause.

Practical diagnostics and fixes

- Capture request payloads: add a logging step before the YouTube node (save the JSON payload to a file or webhook) to compare manual vs automated outputs.
- Check expression resolution: ensure the expressions used for Title or other fields are available at production trigger time; add defaults for missing values.
- Auth and quotas: verify OAuth tokens refresh automatically for production credentials and that required scopes are granted.
- Retry and backoff: implement retry logic for transient errors and validate string encoding/length limits for fields like title/description.

Recommended actions for leaders

Prioritize observability around automation: enforce request logging, include synthetic end-to-end tests during deployment, and allocate a small engineering task to harden the workflow (graceful defaults, validation steps). If platform limitations persist, escalate to vendor support or consider a lightweight custom integration that provides full control over request construction.